From: Hans Rosenfeld <hans.rosenfeld@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Richter, Robert" <robert.richter@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC 0/3] Basic support for LWP
Date: Tue, 5 Oct 2010 20:27:39 +0200 [thread overview]
Message-ID: <20101005182739.GE173@escobedo.osrc.amd.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010051730060.2556@localhost6.localdomain6>
On Tue, Oct 05, 2010 at 11:34:11AM -0400, Thomas Gleixner wrote:
> So it's the end result. Ok, then explain the following sentence:
>
> > > > This code adds basic support for LWP to the context switch code, which
> > > > is the minimum needed to use LWP. Support for other LWP features like
> > > > interrupts will be added later.
>
> If your patch _IS_ the end result then there are no other LWP
> features, right ?
Ok, you got me there. I should have checked again before I wrote this.
There is at one other optional feature. Thats the support for a
thresholding interrupt, which the OS should relay to the user process
in one way or another.
But thats not required to use LWP instructions. Maybe Robert will add
it to perf some day, or maybe not. It is completely optional, and how
it is implemented at some point in the future is completely irrelevant
to the basic support of LWP.
> If there are, then your patch is _NOT_ the end result and we really
> want to know what is coming.
As far as I am concerned, it _is_ the end result. It implements the
necessary changes to make LWP usable, and that's it.
Whatever support for optional features Robert or anybody else may be
going to implement or not affects in no way the necessity of managing
the LWP state for user processes. Those are two completely unrelated
issues.
Now, since this was obviously not made clear enough before:
Don't merge this code anywhere yet. This is an RFC and nothing else.
It implements a basic change necessary to support a new instruction
set, which just so happens to be a profiling mechanism, too. Please
review the code and flame me for anything that you don't like in it.
Hans
PS: The patches were not delivered to LKML previously, so I'll resend
them.
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
next prev parent reply other threads:[~2010-10-05 18:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1286212172-654419-1-git-send-email-hans.rosenfeld@amd.com>
2010-10-04 22:13 ` Thomas Gleixner
2010-10-05 14:51 ` Hans Rosenfeld
2010-10-05 15:34 ` Thomas Gleixner
2010-10-05 18:27 ` Hans Rosenfeld [this message]
2010-10-05 18:30 ` Hans Rosenfeld
2010-10-05 18:30 ` [RFC 1/3] Cleanup xsave/xrstor support Hans Rosenfeld
2010-10-05 18:30 ` [RFC 2/3] Allow saving of individual states in fpu_xsave() Hans Rosenfeld
2010-10-05 18:30 ` [RFC 3/3] Save/restore LWP state in context switches Hans Rosenfeld
2010-10-06 11:12 ` Brian Gerst
2010-10-07 14:58 ` Hans Rosenfeld
2010-11-23 20:41 ` [RFC 0/2] FPU/xsave rework in preparation for LWP Hans Rosenfeld
2010-11-23 20:41 ` [RFC 1/2] x86, xsave: cleanup xsave/xrstor support Hans Rosenfeld
2010-11-23 20:41 ` [RFC 2/2] x86, xsave: rework xsave support Hans Rosenfeld
2010-11-25 0:36 ` Brian Gerst
2010-10-05 19:05 ` [RFC 0/3] Basic support for LWP Ingo Molnar
2010-10-06 7:35 ` Robert Richter
[not found] ` <AANLkTi=T0QmcKeZcgcR+GKk-9OwQUB_x8XdHiNuU7tE_@mail.gmail.com>
2010-10-07 10:46 ` Stephane Eranian
2010-10-07 13:59 ` H. Peter Anvin
2010-10-07 14:11 ` Stephane Eranian
2010-10-07 14:20 ` Hans Rosenfeld
2010-10-07 14:20 ` H. Peter Anvin
2010-10-07 14:25 ` Stephane Eranian
2010-10-07 14:47 ` H. Peter Anvin
2010-10-07 15:12 ` Stephane Eranian
2010-10-05 18:43 ` Davidlohr Bueso
2010-10-06 10:26 ` 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=20101005182739.GE173@escobedo.osrc.amd.com \
--to=hans.rosenfeld@amd.com \
--cc=Andreas.Herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome