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