From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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>
Subject: Re: re-enable Nehalem raw Offcore-Events support
Date: Sat, 30 Apr 2011 22:09:16 +0100 [thread overview]
Message-ID: <20110430220916.1c184d4d@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1104301653310.7288@cl320.eecs.utk.edu>
> See the problem here? Going general event first makes it seriously
> inconvenient to test and so noone is going to do it for you because it's
> such a pain. RAW first is the way to go.
Or you build your patch back in each time.
Lots of us don't run a Linus kernel. Mine gets several patches each
update which mean the disk performance is typically a few percent faster
than the upstream one etc.
Alan
next prev parent reply other threads:[~2011-04-30 21:08 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
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 [this message]
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=20110430220916.1c184d4d@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@linux.intel.com \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®