From: Hans Rosenfeld <hans.rosenfeld@amd.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86 <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [RFC] syscall calling convention, stts/clts, and xstate latency
Date: Mon, 25 Jul 2011 13:04:46 +0200 [thread overview]
Message-ID: <20110725110446.GD353@escobedo.osrc.amd.com> (raw)
In-Reply-To: <CAObL_7G-afftZD7ULhbyTqBsuZCs03H-HS-n8tqRC=-Q3Bs9Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Mon, Jul 25, 2011 at 05:44:32AM -0400, Andrew Lutomirski wrote:
> On Mon, Jul 25, 2011 at 2:38 AM, Ingo Molnar <mingo@elte.hu> wrote:
> > I should have mentioned it earlier, but there's a certain amount of
> > delazying patches in the tip:x86/xsave branch:
> >
> > $ gll linus..x86/xsave
> > 300c6120b465: x86, xsave: fix non-lazy allocation of the xsave area
> > f79018f2daa9: Merge branch 'x86/urgent' into x86/xsave
> > 66beba27e8b5: x86, xsave: remove lazy allocation of xstate area
> > 1039b306b1c6: x86, xsave: add kernel support for AMDs Lightweight Profiling (LWP)
> > 4182a4d68bac: x86, xsave: add support for non-lazy xstates
> > 324cbb83e215: x86, xsave: more cleanups
> > 2efd67935eb7: x86, xsave: remove unused code
> > 0c11e6f1aed1: x86, xsave: cleanup fpu/xsave signal frame setup
> > 7f4f0a56a7d3: x86, xsave: rework fpu/xsave support
> > 26bce4e4c56f: x86, xsave: cleanup fpu/xsave support
> >
> > it's not in tip:master because the LWP bits need (much) more work to
> > be palatable - but we could spin them off and complete them as per
> > your suggestions if they are an independent speedup on modern CPUs.
>
> Hans, what's the status of these? I want to do some other cleanups
> (now or in a couple of weeks) that will probably conflict with your
> xsave work.
I know of one bug in there that occasionally causes panics at boot, see
the attached patch for a fix.
Hans
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
[-- Attachment #2: 0001-x86-xsave-clear-pre-allocated-xsave-area.patch --]
[-- Type: text/plain, Size: 1056 bytes --]
>From 599d3ee9a9e743377739480a8a893582f1409a8d Mon Sep 17 00:00:00 2001
From: Hans Rosenfeld <hans.rosenfeld@amd.com>
Date: Wed, 6 Jul 2011 16:31:19 +0200
Subject: [PATCH 1/1] x86, xsave: clear pre-allocated xsave area
Bogus data in the xsave area can cause xrstor to panic, so make sure
that the pre-allocated xsave area is all nice and clean before being
used.
Signed-off-by: Hans Rosenfeld <hans.rosenfeld@amd.com>
---
arch/x86/kernel/process.c | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index c5ae256..03c5ded 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -28,8 +28,15 @@ EXPORT_SYMBOL_GPL(task_xstate_cachep);
int arch_prealloc_fpu(struct task_struct *tsk)
{
- if (!fpu_allocated(&tsk->thread.fpu))
- return fpu_alloc(&tsk->thread.fpu);
+ if (!fpu_allocated(&tsk->thread.fpu)) {
+ int err = fpu_alloc(&tsk->thread.fpu);
+
+ if (err)
+ return err;
+
+ fpu_clear(&tsk->thread.fpu);
+ }
+
return 0;
}
--
1.5.6.5
next prev parent reply other threads:[~2011-07-25 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 21:07 [RFC] syscall calling convention, stts/clts, and xstate latency Andrew Lutomirski
2011-07-24 21:15 ` Ingo Molnar
2011-07-24 22:34 ` Andrew Lutomirski
2011-07-25 3:21 ` Andrew Lutomirski
2011-07-25 6:42 ` Ingo Molnar
2011-07-25 10:05 ` [PATCH 3.1?] x86: Remove useless stts/clts pair in __switch_to Andy Lutomirski
2011-07-25 11:12 ` Ingo Molnar
2011-07-25 13:04 ` Andrew Lutomirski
2011-07-25 14:13 ` Ingo Molnar
2011-07-25 6:38 ` [RFC] syscall calling convention, stts/clts, and xstate latency Ingo Molnar
2011-07-25 9:44 ` Andrew Lutomirski
2011-07-25 9:51 ` Ingo Molnar
2011-07-25 11:04 ` Hans Rosenfeld [this message]
2011-07-25 7:42 ` Avi Kivity
2011-07-25 7:54 ` Ingo Molnar
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=20110725110446.GD353@escobedo.osrc.amd.com \
--to=hans.rosenfeld@amd.com \
--cc=arjan@infradead.org \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=x86@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