From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: perf: Clean up perf_event cpu code
Date: Fri, 02 Sep 2011 15:32:06 +0200 [thread overview]
Message-ID: <1314970326.1301.16.camel@twins> (raw)
In-Reply-To: <1314747665-2090-1-git-send-email-kjwinchester@gmail.com>
On Tue, 2011-08-30 at 20:41 -0300, Kevin Winchester wrote:
> The CPU support for perf events on x86 was implemented via included C files
> with #ifdefs. Clean this up by creating a new header file and compiling
> the vendor-specific files as needed.
>
> Signed-off-by: Kevin Winchester <kjwinchester@gmail.com>
> ---
>
> This is now against the tip tree. I left it all as one big commit for now,
> although I can break it up if necessary. I'm just not sure it would gain much.
>
> Again, this is by far the largest out of the handful of patches I have ever
> submitted, so please let me know if I am doing anything wrong.
>
I've stuck it in the queue,. seems to work so far.
If Ingo doesn't complain, it ought to show up for the next release
someplace ;-)
next prev parent reply other threads:[~2011-09-02 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 23:40 warning: ‘x86_get_event_constraints’ defined but not used Kevin Winchester
2011-08-23 13:23 ` Peter Zijlstra
2011-08-23 13:31 ` Kevin Winchester
2011-08-30 11:21 ` [RFC PATCH] x86: perf: Clean up perf_event cpu code Kevin Winchester
2011-08-30 11:35 ` Peter Zijlstra
2011-08-30 23:41 ` [PATCH] " Kevin Winchester
2011-09-02 13:32 ` Peter Zijlstra [this message]
2011-09-19 10:27 ` Peter Zijlstra
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=1314970326.1301.16.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=hpa@zytor.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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