From: David Miller <davem@davemloft.net>
To: heiko.carstens@de.ibm.com
Cc: rostedt@goodmis.org, vapier@gentoo.org,
linux-kernel@vger.kernel.org, fweisbec@gmail.com,
mingo@redhat.com, brueckner@linux.vnet.ibm.com,
lethal@linux-sh.org
Subject: Re: [PATCH] ftrace: unify arch_syscall_addr() implementations
Date: Fri, 22 Jan 2010 17:38:38 -0800 (PST) [thread overview]
Message-ID: <20100122.173838.159363288.davem@davemloft.net> (raw)
In-Reply-To: <20100122163700.GD6412@osiris.boeblingen.de.ibm.com>
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Date: Fri, 22 Jan 2010 17:37:00 +0100
> On Fri, Jan 22, 2010 at 09:36:17AM -0500, Steven Rostedt wrote:
>> I would not be too sure. s390 is very strange, and I would definitely
>> want to get an Ack from the arch maintainers first.
>
> It's not a typo. The syscall table on s390 contains always 32 bit pointers
> since we know that the address of the function to be called is (way) below
> 4GB. So this saves us a few bytes.
> In addition this makes syscall patching done by some security modules a
> bit more difficult, since they would need to store a 64 bit pointer.
> That's because we make sure that module addresses are always above 4GB.
Sparc64 is the same way.
next prev parent reply other threads:[~2010-01-23 1:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 13:43 Mike Frysinger
2010-01-22 14:36 ` Steven Rostedt
2010-01-22 16:37 ` Heiko Carstens
2010-01-22 19:32 ` Mike Frysinger
2010-01-23 1:38 ` David Miller [this message]
2010-01-23 1:36 ` David Miller
2010-01-26 3:03 ` Paul Mundt
2010-01-27 4:50 ` Mike Frysinger
2010-01-23 7:10 ` [PATCH v2] " Mike Frysinger
2010-01-23 8:28 ` David Miller
2010-01-23 19:13 ` Mike Frysinger
2010-01-26 9:40 ` [PATCH v3] " Mike Frysinger
2010-01-26 11:29 ` Heiko Carstens
2010-02-03 22:48 ` Frederic Weisbecker
2010-02-27 12:51 ` [tip:tracing/core] tracing: Unify " tip-bot for Mike Frysinger
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=20100122.173838.159363288.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brueckner@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vapier@gentoo.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®