Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
Kernel
提交
420b61f4
K
Kernel
项目概览
openeuler
/
Kernel
大约 1 年 前同步成功
通知
5
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
K
Kernel
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
420b61f4
编写于
6月 13, 2009
作者:
M
Mike Frysinger
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Blackfin: convert user/elf to asm-generic
Signed-off-by:
N
Mike Frysinger
<
vapier@gentoo.org
>
上级
71b844f1
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
2 addition
and
90 deletion
+2
-90
arch/blackfin/include/asm/elf.h
arch/blackfin/include/asm/elf.h
+1
-1
arch/blackfin/include/asm/user.h
arch/blackfin/include/asm/user.h
+1
-89
未找到文件。
arch/blackfin/include/asm/elf.h
浏览文件 @
420b61f4
...
...
@@ -20,7 +20,7 @@
typedef
unsigned
long
elf_greg_t
;
#define ELF_NGREG
(sizeof(struct user_regs_struct) / sizeof(elf_greg_t))
#define ELF_NGREG
40
/* (sizeof(struct user_regs_struct) / sizeof(elf_greg_t)) */
typedef
elf_greg_t
elf_gregset_t
[
ELF_NGREG
];
typedef
struct
user_bfinfp_struct
elf_fpregset_t
;
...
...
arch/blackfin/include/asm/user.h
浏览文件 @
420b61f4
#ifndef _BFIN_USER_H
#define _BFIN_USER_H
/* Changes by Tony Kou Lineo, Inc. July, 2001
*
* Based include/asm-m68knommu/user.h
*
*/
/* Core file format: The core file is written in such a way that gdb
can understand it and provide useful information to the user (under
linux we use the 'trad-core' bfd). There are quite a number of
obstacles to being able to view the contents of the floating point
registers, and until these are solved you will not be able to view the
contents of them. Actually, you can read in the core file and look at
the contents of the user struct to find out what the floating point
registers contain.
The actual file contents are as follows:
UPAGE: 1 page consisting of a user struct that tells gdb what is present
in the file. Directly after this is a copy of the task_struct, which
is currently not used by gdb, but it may come in useful at some point.
All of the registers are stored as part of the upage. The upage should
always be only one page.
DATA: The data area is stored. We use current->end_text to
current->brk to pick up all of the user variables, plus any memory
that may have been malloced. No attempt is made to determine if a page
is demand-zero or if a page is totally unused, we just cover the entire
range. All of the addresses are rounded in such a way that an integral
number of pages is written.
STACK: We need the stack information in order to get a meaningful
backtrace. We need to write the data from (esp) to
current->start_stack, so we round each of these off in order to be able
to write an integer number of pages.
The minimum core file size is 3 pages, or 12288 bytes.
*/
struct
user_bfinfp_struct
{
};
/* This is the old layout of "struct pt_regs" as of Linux 1.x, and
is still the layout used by user (the new pt_regs doesn't have
all registers). */
struct
user_regs_struct
{
long
r0
,
r1
,
r2
,
r3
,
r4
,
r5
,
r6
,
r7
;
long
p0
,
p1
,
p2
,
p3
,
p4
,
p5
,
usp
,
fp
;
long
i0
,
i1
,
i2
,
i3
;
long
l0
,
l1
,
l2
,
l3
;
long
b0
,
b1
,
b2
,
b3
;
long
m0
,
m1
,
m2
,
m3
;
long
a0w
,
a1w
;
long
a0x
,
a1x
;
unsigned
long
rets
;
unsigned
long
astat
;
unsigned
long
pc
;
unsigned
long
orig_p0
;
};
/* When the kernel dumps core, it starts by dumping the user struct -
this will be used by gdb to figure out where the data and stack segments
are within the file, and what virtual addresses to use. */
struct
user
{
/* We start with the registers, to mimic the way that "memory" is returned
from the ptrace(3,...) function. */
struct
user_regs_struct
regs
;
/* Where the registers are actually stored */
/* The rest of this junk is to help gdb figure out what goes where */
unsigned
long
int
u_tsize
;
/* Text segment size (pages). */
unsigned
long
int
u_dsize
;
/* Data segment size (pages). */
unsigned
long
int
u_ssize
;
/* Stack segment size (pages). */
unsigned
long
start_code
;
/* Starting virtual address of text. */
unsigned
long
start_stack
;
/* Starting virtual address of stack area.
This is actually the bottom of the stack,
the top of the stack is always found in the
esp register. */
long
int
signal
;
/* Signal that caused the core dump. */
int
reserved
;
/* No longer used */
unsigned
long
u_ar0
;
/* Used by gdb to help find the values for */
/* the registers. */
unsigned
long
magic
;
/* To uniquely identify a core file */
char
u_comm
[
32
];
/* User command that was responsible */
};
#define NBPG PAGE_SIZE
#define UPAGES 1
#define HOST_TEXT_START_ADDR (u.start_code)
#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
#endif
#include <asm-generic/user.h>
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录