From: Jakub Jelinek <jakub@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 13:14:01 -0400 [thread overview]
Message-ID: <20030714131400.N15481@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030715031123.5c8e0c96.sfr@canb.auug.org.au>; from sfr@canb.auug.org.au on Tue, Jul 15, 2003 at 03:11:23AM +1000
On Tue, Jul 15, 2003 at 03:11:23AM +1000, Stephen Rothwell wrote:
> > This is not correct for the merged header.
> > It needs to be:
> > #ifdef __s390x__
> > #define __ARCH_SI_PREAMBLE_SIZE (4 * sizeof(int))
> > #endif
>
> OK, I can see that (although is __s390x__ defined when building a
> 32 (31?) bit kernel on a 64bit s390?).
__s390x__ is defined when doing 64-bit compile targetted to s390.
Ie. gcc -m64 defines it, gcc -m31 does not.
> > Furthermore, there needs to be a pad inserted fo arch/s390x/kernel/signal.c
> ^^^^^
> s390? (there is no arch/s390x in 2.6.0-test1)
Then that pad needs to be #ifdef __s390x__ as well.
>
> > (rt_sigframe right after info member) to keep binary compatibility.
Jakub
next prev parent reply other threads:[~2003-07-14 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 12:40 sizeof (siginfo_t) problem Jakub Jelinek
2003-07-14 13:55 ` Jamie Lokier
2003-07-14 15:02 ` Andreas Schwab
2003-07-14 15:48 ` David Mosberger
2003-07-14 15:57 ` Jakub Jelinek
2003-07-14 16:52 ` Stephen Rothwell
2003-07-14 17:00 ` Jakub Jelinek
2003-07-14 17:11 ` Stephen Rothwell
2003-07-14 17:14 ` Jakub Jelinek [this message]
2003-07-14 17:25 ` Stephen Rothwell
2003-07-14 17:45 ` Jakub Jelinek
2003-07-19 18:32 ` Anton Blanchard
2003-07-21 0:08 ` Stephen Rothwell
2003-07-22 13:42 ` Russell King
2003-07-22 13:57 ` Stephen Rothwell
2003-07-14 18:31 Ulrich Weigand
2003-07-14 18:35 ` Jakub Jelinek
2003-07-14 18:52 Ulrich Weigand
2003-07-15 11:58 Martin Schwidefsky
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=20030714131400.N15481@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).