From: Jason Wessel <jason.wessel@windriver.com>
To: linux-kernel@vger.kernel.org
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
Jason Wessel <jason.wessel@windriver.com>
Subject: [PATCH 3/3] kgdb, mips: pad pt_regs on MIPS64 for function arguments in an exception
Date: Fri, 18 Jul 2008 12:08:48 -0500 [thread overview]
Message-ID: <1216400928-29097-4-git-send-email-jason.wessel@windriver.com> (raw)
In-Reply-To: <1216400928-29097-3-git-send-email-jason.wessel@windriver.com>
When using KGDB the pt_regs structure has the function arguments saved
to the stack. 48 bytes are required for MIPS 64 for this purpose.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
include/asm-mips/ptrace.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-mips/ptrace.h b/include/asm-mips/ptrace.h
index 786f7e3..c3f535f 100644
--- a/include/asm-mips/ptrace.h
+++ b/include/asm-mips/ptrace.h
@@ -28,7 +28,7 @@
* system call/exception. As usual the registers k0/k1 aren't being saved.
*/
struct pt_regs {
-#ifdef CONFIG_32BIT
+#if defined(CONFIG_32BIT) || defined(CONFIG_KGDB)
/* Pad bytes for argument save space on the stack. */
unsigned long pad0[6];
#endif
--
1.5.5.1
next prev parent reply other threads:[~2008-07-18 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 17:08 [PATCH 0/3] kgdb 2.6.27 mips Jason Wessel
2008-07-18 17:08 ` [PATCH 1/3] kgdb, mips: Remove existing kgdb implementation Jason Wessel
2008-07-18 17:08 ` [PATCH 2/3] kgdb, mips: add arch support for the kernel's kgdb core Jason Wessel
2008-07-18 17:08 ` Jason Wessel [this message]
2008-07-18 17:31 ` Atsushi Nemoto
2008-07-18 17:50 ` Jason Wessel
2008-07-24 16:27 ` Atsushi Nemoto
2008-07-25 3:00 ` Jason Wessel
2008-07-25 14:52 ` Atsushi Nemoto
2008-07-28 14:05 ` Atsushi Nemoto
2008-07-28 18:50 ` Jason Wessel
2008-07-29 1:24 ` Atsushi Nemoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1216400928-29097-4-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®