1 files changed, 84 insertions, 0 deletions
diff --git a/arch/arm/include/asm/user.h b/arch/arm/include/asm/user.h
new file mode 100644
index 000000000000..825c1e7c582d
--- /dev/null
+++ b/arch/arm/include/asm/user.h
@@ -0,0 +1,84 @@
+#ifndef _ARM_USER_H
+#define _ARM_USER_H
+#include <asm/page.h>
+#include <asm/ptrace.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_fp {
+        struct fp_reg {
+                unsigned int sign1:1;
+                unsigned int unused:15;
+                unsigned int sign2:1;
+                unsigned int exponent:14;
+                unsigned int j:1;
+                unsigned int mantissa1:31;
+                unsigned int mantissa0:32;
+        } fpregs[8];
+        unsigned int fpsr:32;
+        unsigned int fpcr:32;
+        unsigned char ftype[8];
+        unsigned int init_flag;
+};
+/* 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 pt_regs regs;          /* Where the registers are actually stored */
+/* ptrace does not yet supply these.  Someday.... */
+  int u_fpvalid;                /* True if math co-processor being used. */
+                                /* for this mess. Not yet used. */
+/* 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 */
+  int u_debugreg[8];
+  struct user_fp u_fp;          /* FP state */
+  struct user_fp_struct * u_fp0;/* Used by gdb to help find the values for */
+                                /* the FP registers. */
+};
+#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 /* _ARM_USER_H */

diff --git a/arch/arm/include/asm/user.h b/arch/arm/include/asm/user.h new file mode 100644 index 000000000000..825c1e7c582d --- /dev/null +++ b/arch/arm/include/asm/user.h
@@ -0,0 +1,84 @@
	1	#ifndef _ARM_USER_H
	2	#define _ARM_USER_H
	3
	4	#include <asm/page.h>
	5	#include <asm/ptrace.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 (under
	8	linux we use the 'trad-core' bfd). There are quite a number of
	9	obstacles to being able to view the contents of the floating point
	10	registers, and until these are solved you will not be able to view the
	11	contents of them. Actually, you can read in the core file and look at
	12	the contents of the user struct to find out what the floating point
	13	registers contain.
	14	The actual file contents are as follows:
	15	UPAGE: 1 page consisting of a user struct that tells gdb what is present
	16	in the file. Directly after this is a copy of the task_struct, which
	17	is currently not used by gdb, but it may come in useful at some point.
	18	All of the registers are stored as part of the upage. The upage should
	19	always be only one page.
	20	DATA: The data area is stored. We use current->end_text to
	21	current->brk to pick up all of the user variables, plus any memory
	22	that may have been malloced. No attempt is made to determine if a page
	23	is demand-zero or if a page is totally unused, we just cover the entire
	24	range. All of the addresses are rounded in such a way that an integral
	25	number of pages is written.
	26	STACK: We need the stack information in order to get a meaningful
	27	backtrace. We need to write the data from (esp) to
	28	current->start_stack, so we round each of these off in order to be able
	29	to write an integer number of pages.
	30	The minimum core file size is 3 pages, or 12288 bytes.
	31	*/
	32
	33	struct user_fp {
	34	struct fp_reg {
	35	unsigned int sign1:1;
	36	unsigned int unused:15;
	37	unsigned int sign2:1;
	38	unsigned int exponent:14;
	39	unsigned int j:1;
	40	unsigned int mantissa1:31;
	41	unsigned int mantissa0:32;
	42	} fpregs[8];
	43	unsigned int fpsr:32;
	44	unsigned int fpcr:32;
	45	unsigned char ftype[8];
	46	unsigned int init_flag;
	47	};
	48
	49	/* When the kernel dumps core, it starts by dumping the user struct -
	50	this will be used by gdb to figure out where the data and stack segments
	51	are within the file, and what virtual addresses to use. */
	52	struct user{
	53	/* We start with the registers, to mimic the way that "memory" is returned
	54	from the ptrace(3,...) function. */
	55	struct pt_regs regs; /* Where the registers are actually stored */
	56	/* ptrace does not yet supply these. Someday.... */
	57	int u_fpvalid; /* True if math co-processor being used. */
	58	/* for this mess. Not yet used. */
	59	/* The rest of this junk is to help gdb figure out what goes where */
	60	unsigned long int u_tsize; /* Text segment size (pages). */
	61	unsigned long int u_dsize; /* Data segment size (pages). */
	62	unsigned long int u_ssize; /* Stack segment size (pages). */
	63	unsigned long start_code; /* Starting virtual address of text. */
	64	unsigned long start_stack; /* Starting virtual address of stack area.
	65	This is actually the bottom of the stack,
	66	the top of the stack is always found in the
	67	esp register. */
	68	long int signal; /* Signal that caused the core dump. */
	69	int reserved; /* No longer used */
	70	unsigned long u_ar0; /* Used by gdb to help find the values for */
	71	/* the registers. */
	72	unsigned long magic; /* To uniquely identify a core file */
	73	char u_comm[32]; /* User command that was responsible */
	74	int u_debugreg[8];
	75	struct user_fp u_fp; /* FP state */
	76	struct user_fp_struct * u_fp0;/* Used by gdb to help find the values for */
	77	/* the FP registers. */
	78	};
	79	#define NBPG PAGE_SIZE
	80	#define UPAGES 1
	81	#define HOST_TEXT_START_ADDR (u.start_code)
	82	#define HOST_STACK_END_ADDR (u.start_stack + u.u_ssize * NBPG)
	83
	84	#endif /* _ARM_USER_H */