Linux-2.6.12-rc2v2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!

1 files changed, 83 insertions, 0 deletions

diff --git a/arch/s390/kernel/compat_ptrace.h b/arch/s390/kernel/compat_ptrace.h
new file mode 100644
index 000000000000..419aef913ee1
--- /dev/null
+++ b/arch/s390/kernel/compat_ptrace.h
@@ -0,0 +1,83 @@
+#ifndef _PTRACE32_H
+#define _PTRACE32_H
+
+#include "compat_linux.h"  /* needed for _psw_t32 */
+
+typedef struct {
+        __u32 cr[3];
+} per_cr_words32;
+
+typedef struct {
+        __u16          perc_atmid;          /* 0x096 */
+        __u32          address;             /* 0x098 */
+        __u8           access_id;           /* 0x0a1 */
+} per_lowcore_words32;
+
+typedef struct {
+        union {
+                per_cr_words32   words;
+        } control_regs;
+        /*
+         * Use these flags instead of setting em_instruction_fetch
+         * directly they are used so that single stepping can be
+         * switched on & off while not affecting other tracing
+         */
+        unsigned  single_step       : 1;
+        unsigned  instruction_fetch : 1;
+        unsigned                    : 30;
+        /*
+         * These addresses are copied into cr10 & cr11 if single
+         * stepping is switched off
+         */
+        __u32     starting_addr;
+        __u32     ending_addr;
+        union {
+                per_lowcore_words32 words;
+        } lowcore; 
+} per_struct32;
+
+struct user_regs_struct32
+{
+        _psw_t32 psw;
+        u32 gprs[NUM_GPRS];
+        u32 acrs[NUM_ACRS];
+        u32 orig_gpr2;
+        s390_fp_regs fp_regs;
+        /*
+         * These per registers are in here so that gdb can modify them
+         * itself as there is no "official" ptrace interface for hardware
+         * watchpoints. This is the way intel does it.
+         */
+        per_struct32 per_info;
+        u32  ieee_instruction_pointer; 
+        /* Used to give failing instruction back to user for ieee exceptions */
+};
+
+struct user32 {
+        /* We start with the registers, to mimic the way that "memory"
+           is returned from the ptrace(3,...) function.  */
+        struct user_regs_struct32 regs; /* Where the registers are actually stored */
+        /* The rest of this junk is to help gdb figure out what goes where */
+        u32 u_tsize;            /* Text segment size (pages). */
+        u32 u_dsize;            /* Data segment size (pages). */
+        u32 u_ssize;            /* Stack segment size (pages). */
+        u32 start_code;         /* Starting virtual address of text. */
+        u32 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.  */
+        s32 signal;              /* Signal that caused the core dump. */
+        u32 u_ar0;               /* Used by gdb to help find the values for */
+                                 /* the registers. */
+        u32 magic;               /* To uniquely identify a core file */
+        char u_comm[32];         /* User command that was responsible */
+};
+
+typedef struct
+{
+        __u32   len;
+        __u32   kernel_addr;
+        __u32   process_addr;
+} ptrace_area_emu31;
+
+#endif /* _PTRACE32_H */