ARM32,phys_to_virt,无法处理虚拟地址上的内核页面调度请求

如何解决ARM32,phys_to_virt,无法处理虚拟地址上的内核页面调度请求

我正在实现https://apenwarr.ca/log/20190216的变体。长话短说,主要的想法是在内存中留出空间,以便在软重启/出现紧急情况后保留信息并检索该信息。

就我而言,我只想保留一些变量,以免重新引导到另一个变量。因此,我已经研究了此机制的一个简单变体来完成这项工作。该代码只是原始补丁的复制粘贴,并进行了一些原始改编。我添加了一个系统调用以进入内核模式以执行此代码(此处未显示)。

    struct logbits {
        int magic; /* needed to verify the memory across reboots */
        int state;
        int nb_reboot;
    };
    
    #define PERSIST_SEARCH_START 0
    #ifdef CONFIG_NO_BOOTMEM
    #define PERSIST_SEARCH_END 0x5e000000
    #else
    #define PERSIST_SEARCH_END 0xfe000000
    #endif
    #define PERSIST_SEARCH_JUMP (4*1024)
    #define PERSIST_MAGIC 0xba5eba11
    
    /*
     * arm uses one memory model,mips uses another
     */
    phys_addr_t physmem_reserve(phys_addr_t size) {
    #ifdef CONFIG_NO_BOOTMEM
        phys_addr_t alloc;
        alloc = memblock_find_in_range_node(size,SMP_CACHE_BYTES,PERSIST_SEARCH_START,PERSIST_SEARCH_END,NUMA_NO_NODE);
        if (!alloc) return alloc;
        if (memblock_reserve(alloc,size)) {
            pr_err("info_keeper: memblock_reserve failed\n");
            return 0;
        }
        return alloc;
    #else
        unsigned long where;
        for (where = PERSIST_SEARCH_END - size;
             where >= PERSIST_SEARCH_START && where <= PERSIST_SEARCH_END - size;
             where -= PERSIST_SEARCH_JUMP) {
            if (reserve_bootmem(where,size,BOOTMEM_EXCLUSIVE))
                continue;
            else
                return where;
        }
        return 0;
    #endif
    }
    
    struct logbits *log_buf_alloc(char **new_logbuf)
    {
        char *buf;
        phys_addr_t alloc;
        unsigned long size = sizeof(struct logbits);
        unsigned long full_size = size;
        struct logbits *new_logbits;
    
        alloc = physmem_reserve(full_size);
        if (alloc) {
            printk(KERN_INFO "info_keeper: memory reserved @ 0x%08x\n",alloc);
            buf = phys_to_virt(alloc);
            if(buf){
                *new_logbuf = buf;
                new_logbits = (void*)buf;
                printk(KERN_INFO "info_keeper: memory virtual @ 0x%08x\n",buf);
                if (new_logbits->magic != PERSIST_MAGIC) {
                    printk(KERN_INFO "info_keeper: header invalid," "cleared.\n");
                    memset(buf,full_size);
                    memset(new_logbits,sizeof(*new_logbits));
                    new_logbits->magic = PERSIST_MAGIC;
                } else {
                    printk(KERN_INFO "info_keeper: header valid; " "state=%d\n" "nb_reboot=%d\n",new_logbits->state,new_logbits->nb_reboot);
                }
                return new_logbits;
            }else{
                printk(KERN_ERR "info_keeper: failed to get phys to virt");
                buf = alloc_bootmem(full_size);
                *new_logbuf = buf;
                new_logbits = (struct logbits*)(buf);
                memset(buf,full_size);
            }
        } else {
            /* replace the buffer */
            printk(KERN_ERR "info_keeper: failed to reserve bootmem " "area. disabled.\n");
            buf = alloc_bootmem(full_size);
            *new_logbuf = buf;
            new_logbits = (struct logbits*)(buf);
            memset(buf,full_size);
        }
        return new_logbits;
    }

执行后,physmem_reserve函数成功并返回一个内存区域。然后,我从phys_to_virt获得了物理到虚拟内存的映射。然后,当我尝试访问内存时,出现此Unable to handle kernel paging request at virtual address错误。

以下是示例输出:

[   42.489639] info_keeper: memory reserved @ 0x5dffffc0
[   42.494781] info_keeper: memory virtual @ 0x0dffffc0
[   42.499778] Unable to handle kernel paging request at virtual address 0dffffc0

有什么想法吗?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-