public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
	akpm@linux-foundation.org
Subject: Re: [patch] x86: fix taking DNA during 64bit sigreturn
Date: Mon, 12 Nov 2007 16:11:34 -0800	[thread overview]
Message-ID: <4738EBB6.7060605@zytor.com> (raw)
In-Reply-To: <200711122216.40663.ak@suse.de>

Andi Kleen wrote:
>> The *real* fix for this is almost certainly to just get rid of the 64-bit 
>> code entirely, and use the 32-bit code as the base for one single unified 
>> setup.
> 
> That would likely break the ABI. x86-64 ABI is completely different here --
> no ibcs, just pure x86 ISA.
> 

Different ABIs clearly have to be handled, but I don't think that is a 
huge deal.  The i387 code overall (not just asm/i387.h) is very 
different, though, and I find it unlikely that a properly unified code 
is going to be ready and working in the 2.6.24 timeframe.  I'm exploring 
if a partial merge with high confidence level is feasible; either way, a 
proper merge for 2.6.25 is probably the right thing.

	-hpa

  reply	other threads:[~2007-11-13  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 19:27 [patch] x86: fix taking DNA during 64bit sigreturn Siddha, Suresh B
2007-11-12 19:08 ` Linus Torvalds
2007-11-12 19:33   ` H. Peter Anvin
2007-11-12 21:16   ` Andi Kleen
2007-11-13  0:11     ` H. Peter Anvin [this message]
2007-11-13  0:43       ` Andi Kleen

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=4738EBB6.7060605@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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