From: "H. Peter Anvin" <hpa@zytor.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hans Rosenfeld <hans.rosenfeld@amd.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
tglx@linutronix.de
Subject: Re: [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels
Date: Thu, 14 Jun 2012 13:48:46 -0700 [thread overview]
Message-ID: <4FDA4E2E.7030503@zytor.com> (raw)
In-Reply-To: <1339545814.28766.148.camel@sbsiddha-desk.sc.intel.com>
On 06/12/2012 05:03 PM, Suresh Siddha wrote:
> I can split the patch if needed. And I need to do little bit more
> validation (already tested on 64-bit IVB and 32-bit NHM) before
> removing the 'RFC' tag.
>
> I tried starting with the old version of Hans patch. But there were lot
> more changes in this area since then and also his patch had few
> user-visible compatibility issues.
>
> Appended is the version that I came up with. Please review.
>
This patch doesn't apply to v3.5-rc2.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-06-14 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 0:03 [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels Suresh Siddha
2012-06-13 0:17 ` H. Peter Anvin
2012-06-14 14:37 ` Hans Rosenfeld
2012-06-14 20:45 ` Suresh Siddha
2012-06-15 0:10 ` Suresh Siddha
2012-06-15 0:16 ` H. Peter Anvin
2012-06-15 1:07 ` Suresh Siddha
2012-06-15 1:13 ` H. Peter Anvin
2012-06-15 1:16 ` Suresh Siddha
2012-06-15 1:17 ` H. Peter Anvin
2012-06-16 3:14 ` [tip:x86/urgent] x86, compat: Use test_thread_flag(TIF_IA32) in compat signal delivery tip-bot for Suresh Siddha
2012-06-14 20:48 ` H. Peter Anvin [this message]
2012-06-14 20:49 ` [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels Suresh Siddha
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=4FDA4E2E.7030503@zytor.com \
--to=hpa@zytor.com \
--cc=hans.rosenfeld@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.