Linux Kernel  3.7.1
 All Data Structures Namespaces Files Functions Variables Typedefs Enumerations Enumerator Macros Groups Pages
user_64.h
Go to the documentation of this file.
1 #ifndef _ASM_X86_USER_64_H
2 #define _ASM_X86_USER_64_H
3 
4 #include <asm/types.h>
5 #include <asm/page.h>
6 /* Core file format: The core file is written in such a way that gdb
7  can understand it and provide useful information to the user.
8  There are quite a number of obstacles to being able to view the
9  contents of the floating point registers, and until these are
10  solved you will not be able to view the contents of them.
11  Actually, you can read in the core file and look at the contents of
12  the user struct to find out what the floating point registers
13  contain.
14 
15  The actual file contents are as follows:
16  UPAGE: 1 page consisting of a user struct that tells gdb what is present
17  in the file. Directly after this is a copy of the task_struct, which
18  is currently not used by gdb, but it may come in useful at some point.
19  All of the registers are stored as part of the upage. The upage should
20  always be only one page.
21  DATA: The data area is stored. We use current->end_text to
22  current->brk to pick up all of the user variables, plus any memory
23  that may have been malloced. No attempt is made to determine if a page
24  is demand-zero or if a page is totally unused, we just cover the entire
25  range. All of the addresses are rounded in such a way that an integral
26  number of pages is written.
27  STACK: We need the stack information in order to get a meaningful
28  backtrace. We need to write the data from (esp) to
29  current->start_stack, so we round each of these off in order to be able
30  to write an integer number of pages.
31  The minimum core file size is 3 pages, or 12288 bytes. */
32 
33 /*
34  * Pentium III FXSR, SSE support
35  * Gareth Hughes <[email protected]>, May 2000
36  *
37  * Provide support for the GDB 5.0+ PTRACE_{GET|SET}FPXREGS requests for
38  * interacting with the FXSR-format floating point environment. Floating
39  * point data can be accessed in the regular format in the usual manner,
40  * and both the standard and SIMD floating point data can be accessed via
41  * the new ptrace requests. In either case, changes to the FPU environment
42  * will be reflected in the task's state as expected.
43  *
44  * x86-64 support by Andi Kleen.
45  */
46 
47 /* This matches the 64bit FXSAVE format as defined by AMD. It is the same
48  as the 32bit format defined by Intel, except that the selector:offset pairs
49  for data and eip are replaced with flat 64bit pointers. */
50 struct user_i387_struct {
51  unsigned short cwd;
52  unsigned short swd;
53  unsigned short twd; /* Note this is not the same as
54  the 32bit/x87/FSAVE twd */
55  unsigned short fop;
56  __u64 rip;
57  __u64 rdp;
58  __u32 mxcsr;
59  __u32 mxcsr_mask;
60  __u32 st_space[32]; /* 8*16 bytes for each FP-reg = 128 bytes */
61  __u32 xmm_space[64]; /* 16*16 bytes for each XMM-reg = 256 bytes */
62  __u32 padding[24];
63 };
64 
65 /*
66  * Segment register layout in coredumps.
67  */
68 struct user_regs_struct {
69  unsigned long r15;
70  unsigned long r14;
71  unsigned long r13;
72  unsigned long r12;
73  unsigned long bp;
74  unsigned long bx;
75  unsigned long r11;
76  unsigned long r10;
77  unsigned long r9;
78  unsigned long r8;
79  unsigned long ax;
80  unsigned long cx;
81  unsigned long dx;
82  unsigned long si;
83  unsigned long di;
84  unsigned long orig_ax;
85  unsigned long ip;
86  unsigned long cs;
87  unsigned long flags;
88  unsigned long sp;
89  unsigned long ss;
90  unsigned long fs_base;
91  unsigned long gs_base;
92  unsigned long ds;
93  unsigned long es;
94  unsigned long fs;
95  unsigned long gs;
96 };
97 
98 /* When the kernel dumps core, it starts by dumping the user struct -
99  this will be used by gdb to figure out where the data and stack segments
100  are within the file, and what virtual addresses to use. */
101 
102 struct user {
103 /* We start with the registers, to mimic the way that "memory" is returned
104  from the ptrace(3,...) function. */
105  struct user_regs_struct regs; /* Where the registers are actually stored */
106 /* ptrace does not yet supply these. Someday.... */
107  int u_fpvalid; /* True if math co-processor being used. */
108  /* for this mess. Not yet used. */
109  int pad0;
110  struct user_i387_struct i387; /* Math Co-processor registers. */
111 /* The rest of this junk is to help gdb figure out what goes where */
112  unsigned long int u_tsize; /* Text segment size (pages). */
113  unsigned long int u_dsize; /* Data segment size (pages). */
114  unsigned long int u_ssize; /* Stack segment size (pages). */
115  unsigned long start_code; /* Starting virtual address of text. */
116  unsigned long start_stack; /* Starting virtual address of stack area.
117  This is actually the bottom of the stack,
118  the top of the stack is always found in the
119  esp register. */
120  long int signal; /* Signal that caused the core dump. */
121  int reserved; /* No longer used */
122  int pad1;
123  unsigned long u_ar0; /* Used by gdb to help find the values for */
124  /* the registers. */
125  struct user_i387_struct *u_fpstate; /* Math Co-processor pointer. */
126  unsigned long magic; /* To uniquely identify a core file */
127  char u_comm[32]; /* User command that was responsible */
128  unsigned long u_debugreg[8];
129  unsigned long error_code; /* CPU error code or 0 */
130  unsigned long fault_address; /* CR3 or 0 */
131 };
132 #define NBPG PAGE_SIZE
133 #define UPAGES 1
134 #define HOST_TEXT_START_ADDR (u.start_code)
135 #define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
136 
137 #endif /* _ASM_X86_USER_64_H */
Generated on Thu Jan 10 2013 13:20:09 for Linux Kernel by   doxygen 1.8.2