From: Ingo Molnar <mingo@elte.hu>
To: Corey Ashford <cjashfor@linux.vnet.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>,
Pekka Enberg <penberg@kernel.org>,
Vince Weaver <vweaver1@eecs.utk.edu>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@gmail.com>,
Carl Love <carll@us.ibm.com>
Subject: Re: re-enable Nehalem raw Offcore-Events support
Date: Sun, 1 May 2011 19:55:05 +0200 [thread overview]
Message-ID: <20110501175505.GA27830@elte.hu> (raw)
In-Reply-To: <4DBC6BC1.5090102@linux.vnet.ibm.com>
* Corey Ashford <cjashfor@linux.vnet.ibm.com> wrote:
> Carl Love and I recently completed some work to add perf_events support for
> the IBM Blue Waters machine's "CPU networking" chip, called the Torrent chip.
> We did all of this work based on a RHEL 6 kernel (2.6.32ish), which doesn't
> have Peter's more recent multi-PMU support.
>
> I would say that most if not all of the events are not generalizable in the
> sense that you are talking about; the events are very specific to the Torrent
> chip. [...]
That's ok and not a problem.
The issue here are events that *are* generalizable.
> So if I'm understanding what you have said correctly, we would not be able to
> get a forward port of this code committed without abstracting these events in
> a away that's acceptable to the kernel community. [...]
If the number of events worth generalizing is the empty set that's ok.
Thanks,
Ingo
next prev parent reply other threads:[~2011-05-01 17:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 15:04 re-enable Nehalem raw Offcore-Events support 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
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 [this message]
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=20110501175505.GA27830@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=carll@us.ibm.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--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