From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
x86 maintainers <x86@kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [git-pull -tip] x86: Basic AMD Support for performance counters
Date: Sat, 28 Feb 2009 10:40:18 +0100 [thread overview]
Message-ID: <20090228094018.GF12095@elte.hu> (raw)
In-Reply-To: <1235756278.3914.9.camel@localhost.localdomain>
* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> Hello Ingo,
>
> These patches added basic AMD (K7 and later) support for performance counters:
>
> [jaswinder@hpdv5 linux-2.6-tip]$ perfstat -e 0,1,2,3,4,5,-1,-2,-3,-4,-5 ls -lR > /dev/null
>
> Performance counter stats for 'ls':
>
> 2723.203821 task clock ticks (msecs)
>
> 1812527794 CPU cycles (events)
> 1121688997 instructions (events)
> 569836744 cache references (events)
> 15934598 cache misses (events)
> 57313261 branches (events)
> 4243201 branch misses (events)
> 2639.682866 cpu clock ticks (msecs)
> 2723.203821 task clock ticks (msecs)
> 647 pagefaults (events)
> 2401 context switches (events)
> 3 CPU migrations (events)
>
> Wall-clock time elapsed: 6813.030975 msecs
Very nice feature!
The AMD patches look much cleaner than i feared they would be.
It seems you were able to keep pretty generic x86 code in
arch/x86/kernel/cpu/perf_counters.c, sharing most of the logic
between Intel and AMD perfcounters.
> The following changes since commit f39e09b3b2c11ad1b008518a05bc2b7c25eabc7d:
> Ingo Molnar (1):
> Merge branch 'tracing/ftrace'
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tip.git master
>
> Jaswinder Singh Rajput (2):
> x86: prepare perf_counter to add more cpus
> x86: AMD Support for perf_counter
>
> arch/x86/kernel/cpu/amd.c | 4 +
> arch/x86/kernel/cpu/perf_counter.c | 189 ++++++++++++++++++++++++++++++------
> 2 files changed, 163 insertions(+), 30 deletions(-)
Pulled into tip:perfcounters/core, thanks Jaswinder!
Ingo
next prev parent reply other threads:[~2009-02-28 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 17:37 [git-pull -tip] x86: Basic AMD Support for performance counters Jaswinder Singh Rajput
2009-02-28 9:40 ` Ingo Molnar [this message]
2009-02-28 13:44 ` Ingo Molnar
2009-03-01 8:36 ` Ingo Molnar
2009-03-01 10:41 ` Jaswinder Singh Rajput
2009-03-01 11:30 ` Ingo Molnar
2009-03-01 11:41 ` Jaswinder Singh Rajput
2009-03-01 11:58 ` Ingo Molnar
2009-03-01 12:00 ` Ingo Molnar
2009-03-01 12:14 ` Jaswinder Singh Rajput
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=20090228094018.GF12095@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--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