public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hans Rosenfeld <hans.rosenfeld@amd.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Richter, Robert" <robert.richter@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [RFC 0/3] Basic support for LWP
Date: Tue, 5 Oct 2010 21:05:01 +0200	[thread overview]
Message-ID: <20101005190501.GA21916@elte.hu> (raw)
In-Reply-To: <20101005182739.GE173@escobedo.osrc.amd.com>


* Hans Rosenfeld <hans.rosenfeld@amd.com> wrote:

> 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.

It isnt irrelevant. If the concept is implemented in a crappy way, if 
there are random user-space libraries that do not properly expose these 
capabilities and do not allow them to extend existing perf functionality 
in a natural way then we might be better off not adding overhead to the 
scheduler and not enabling it at all.

So thoughts need to be made what the point of it all is and how it 
integrates into perf. If it doesnt integrate, if the whole plan is to 
just get it to user-space where it can be messed up freely in some CPU 
specific way then color me thoroughly uninterested. We have a generic 
instrumentation framework for a reason.

We very much want to know the structure of that area and want to make 
use of it not just on a per task basis. We also want to expose it all in 
a more generalized form.

I cannot believe something like this was committed into silicon without 
at minimum talking to people who have a clue about where it will (and 
should) all go ...

	Ingo

  parent reply	other threads:[~2010-10-05 19:05 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 ` [RFC 0/3] Basic support for LWP Thomas Gleixner
2010-10-05 14:51   ` Hans Rosenfeld
2010-10-05 15:34     ` Thomas Gleixner
2010-10-05 18:27       ` Hans Rosenfeld
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         ` Ingo Molnar [this message]
2010-10-06  7:35           ` [RFC 0/3] Basic support for LWP 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=20101005190501.GA21916@elte.hu \
    --to=mingo@elte.hu \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hans.rosenfeld@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.com \
    --cc=rostedt@goodmis.org \
    --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