mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Vince Weaver <vweaver1@eecs.utk.edu>
Cc: Ingo Molnar <mingo@elte.hu>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@gmail.com>,
	Andi Kleen <ak@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Robert Richter <robert.richter@amd.com>
Subject: Re: re-enable Nehalem raw Offcore-Events support
Date: Sat, 30 Apr 2011 10:11:32 +0200	[thread overview]
Message-ID: <20110430081132.GA3705@liondog.tnic> (raw)
In-Reply-To: <alpine.DEB.2.00.1104292200110.9459@cl320.eecs.utk.edu>

On Fri, Apr 29, 2011 at 10:17:04PM -0400, Vince Weaver wrote:
> > AMD managed to keep a large chunk of their events stable even across very 
> > radical changes of the underlying hardware. I have two AMD systems produced 
> > *10* years apart and they even use the same event encodings for the major 
> > events.
> 
> Well guess what, AMD family 15h changes all of that.

I don't see a big problem here, Robert has a patch that takes care of
counter constraints. It probably needs a bit more work but we'll get
where we need to be.

> And you're not going to like LWP. They got tired of waiting for a
> workable kernel perf counter interface and moved it completely to
> usersapce,

I don't know where you get your information but that's absolutely and
completely not nearly even beginning to smell the truth.

> and there's nothing you can do about it unless you start blocking the
> xsave patches from getting in.

Look at tip/x86/xsave, looks like LWP support will most likely be in
2.6.40.

-- 
Regards/Gruss,
    Boris.

  parent reply	other threads:[~2011-04-30  8:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 15:04 Vince Weaver
2011-04-29 15:27 ` Andi Kleen
2011-04-29 16:49   ` Ingo Molnar
2011-04-29 16:42 ` Ingo Molnar
2011-04-29 18:01   ` Vince Weaver
2011-04-29 18:57     ` Ingo Molnar
2011-04-30  2:17       ` Vince Weaver
2011-04-30  7:14         ` Pekka Enberg
2011-04-30 20:47           ` Vince Weaver
2011-05-01 18:31             ` Ingo Molnar
2011-04-30  8:11         ` Borislav Petkov [this message]
2011-04-30 21:03           ` Vince Weaver
2011-05-09 11:01       ` stephane eranian
2011-05-10  9:35         ` Ingo Molnar
2011-04-29 22:16   ` Borislav Petkov
2011-04-30  1:49     ` Vince Weaver
2011-04-30  1:53   ` Vince Weaver
2011-04-30 20:58     ` Vince Weaver
2011-04-30 21:09       ` Alan Cox
2011-04-29 17:17 ` Pekka Enberg
2011-04-29 17:25   ` Andi Kleen
2011-04-29 17:37     ` Pekka Enberg
2011-04-29 17:46       ` Vince Weaver
2011-04-29 17:59         ` Pekka Enberg
2011-04-29 17:42     ` Thomas Gleixner
2011-04-30 20:06       ` Corey Ashford
2011-05-01  4:45         ` Andi Kleen
2011-05-01 18:00           ` Ingo Molnar
2011-05-01 17:55         ` Ingo Molnar
2011-05-02 18:32           ` Corey Ashford

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=20110430081132.GA3705@liondog.tnic \
    --to=bp@alien8.de \
    --cc=ak@linux.intel.com \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vweaver1@eecs.utk.edu \
    /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

all inboxes | Powered by JetHome®