From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
jaswinder@kernel.org, tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perfcounters/core] x86: perf_counter cleanup
Date: Sun, 08 Mar 2009 21:59:08 +0100 [thread overview]
Message-ID: <1236545948.22914.3648.camel@twins> (raw)
In-Reply-To: <tip-e255357764f92afcafafbd4879b222b8c752065a@git.kernel.org>
On Sun, 2009-03-08 at 15:52 +0000, Jaswinder Singh Rajput wrote:
> Commit-ID: e255357764f92afcafafbd4879b222b8c752065a
> Gitweb: http://git.kernel.org/tip/e255357764f92afcafafbd4879b222b8c752065a
> Author: "Jaswinder Singh Rajput" <jaswinder@kernel.org>
> AuthorDate: Sun, 8 Mar 2009 17:09:49 +0530
> Commit: Ingo Molnar <mingo@elte.hu>
> CommitDate: Sun, 8 Mar 2009 16:26:50 +0100
>
> x86: perf_counter cleanup
>
> Remove unused variables and duplicate header file.
Why did you commit this?
Until someone from AMD steps up and either tells us they're going to be
48bits _ALWAYS_ or that it's impossible to detect dynamically, I'd
rather try and get the dynamic thing working.
> Signed-off-by: Jaswinder Singh Rajput <jaswinder@kernel.org>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> ---
> arch/x86/kernel/cpu/perf_counter.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/perf_counter.c b/arch/x86/kernel/cpu/perf_counter.c
> index 1df4210..155bc3c 100644
> --- a/arch/x86/kernel/cpu/perf_counter.c
> +++ b/arch/x86/kernel/cpu/perf_counter.c
> @@ -17,7 +17,6 @@
> #include <linux/kdebug.h>
> #include <linux/sched.h>
>
> -#include <asm/perf_counter.h>
> #include <asm/apic.h>
>
> static bool perf_counters_initialized __read_mostly;
> @@ -954,9 +953,6 @@ static struct pmc_x86_ops *pmc_intel_init(void)
>
> static struct pmc_x86_ops *pmc_amd_init(void)
> {
> - u64 old;
> - int bits;
> -
> nr_counters_generic = 4;
> nr_counters_fixed = 0;
> counter_value_mask = 0x0000FFFFFFFFFFFFULL;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2009-03-08 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-e255357764f92afcafafbd4879b222b8c752065a@git.kernel.org>
2009-03-08 20:59 ` Peter Zijlstra [this message]
2009-03-08 21:03 ` [tip:perfcounters/core] x86: perf_counter cleanup H. Peter Anvin
2009-03-08 21:05 ` Ingo Molnar
2009-03-08 10:34 [git-pull -tip] x86:perf_counter cleanup Peter Zijlstra
2009-03-08 15:52 ` [tip:perfcounters/core] x86: perf_counter cleanup 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=1236545948.22914.3648.camel@twins \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--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