From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: joe.korty@ccur.com
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: siginfo & 32 bits compat, what is the story ?
Date: Tue, 20 Apr 2004 08:02:06 +1000 [thread overview]
Message-ID: <1082412126.19045.45.camel@gaston> (raw)
In-Reply-To: <20040419175503.GA4383@tsunami.ccur.com>
> I believe the x86_64 method is correct.
>
> It might be worth moving this compatibility code to a
> common place where all architectures could reference it.
Hrm... I just heard the opposite: that is, the x86_64 code allows
some cruft to communicate between 32 and 64 bits, but breaks anything
that uses more than those 3 copied fields, even between 2 32 bits
applications.
I'm lost, I don't know in which way to fix ppc64 at this point...
Ben.
next prev parent reply other threads:[~2004-04-19 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 7:35 siginfo & 32 bits compat, what is the story ? Benjamin Herrenschmidt
2004-04-19 17:55 ` Joe Korty
2004-04-19 22:02 ` Benjamin Herrenschmidt [this message]
[not found] <1MBxZ-6l5-37@gated-at.bofh.it>
[not found] ` <1MLe2-5WC-25@gated-at.bofh.it>
[not found] ` <1MP7P-UD-13@gated-at.bofh.it>
2004-04-19 22:44 ` Andi Kleen
2004-04-20 0:30 ` Benjamin Herrenschmidt
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=1082412126.19045.45.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.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