From: Jacob Shin <jacob.shin@amd.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<x86@kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Stephane Eranian <eranian@google.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/5] perf: Add support for hardware breakpoint address masks
Date: Mon, 14 Jan 2013 11:21:35 -0600 [thread overview]
Message-ID: <20130114172135.GA5806@jshin-Toonie> (raw)
In-Reply-To: <20130111135449.GD2847@krava.brq.redhat.com>
On Fri, Jan 11, 2013 at 02:54:49PM +0100, Jiri Olsa wrote:
> On Thu, Jan 10, 2013 at 02:10:54PM -0600, Jacob Shin wrote:
> > The following patchset adds address masks to existing perf hardware
> > breakpoint mechanism to allow trapping on an address range (currently
> > only single address) on supported architectures.
>
> I haven't found any spec for that, could you please direct me?
Hello, (sorry for the late reply, was out of office on Friday)
Unfortunately, I don't have a public spec that I can share for the
processor (AMD Family 16h) this feature first appears in yet. But once
the chip gets released sometime later, I will post a link to the
document that will go public. Sorry .. :-(
But the patchset I think is pretty straight forward and there isn't
much more in the documentation, there are 4 MSRs (one for each DRn)
that software writes "don't care" masks (32 bits) to get the processor
to trap on range of addresses.
Thank you for taking the time to review the patchset ..
-Jacob
>
> thanks,
> jirka
>
> >
> > perf uapi is updated, x86 AMD implementation (for AMD Family 16h and
> > beyond) is provided, and perf tool has been extended to do:
> >
> > $ perf stat -e mem:0x1000:w:0xf a.out
> > ^^^
> > "don't care" bit mask
> >
> > which will count writes to [0x1000 ~ 0x1010)
> >
> > Jacob Shin (2):
> > perf: Add hardware breakpoint address mask
> > perf, x86: AMD implementation for hardware breakpoint address mask
> >
> > Suravee Suthikulpanit (3):
> > perf tools: Add breakpoint address mask to the mem event parser
> > perf tools: Add breakpoint address mask syntax to perf list and
> > documentation
> > perf tools: Add breakpoint address mask test case to
> > tests/parse-events
> >
> > arch/Kconfig | 4 ++++
> > arch/x86/Kconfig | 1 +
> > arch/x86/include/asm/cpufeature.h | 2 ++
> > arch/x86/include/asm/hw_breakpoint.h | 6 ++++++
> > arch/x86/include/asm/processor.h | 7 ++++++
> > arch/x86/include/uapi/asm/msr-index.h | 6 ++++++
> > arch/x86/kernel/cpu/amd.c | 21 ++++++++++++++++++
> > arch/x86/kernel/hw_breakpoint.c | 5 +++++
> > include/linux/hw_breakpoint.h | 6 ++++++
> > include/uapi/linux/perf_event.h | 5 ++++-
> > kernel/events/hw_breakpoint.c | 3 +++
> > tools/perf/Documentation/perf-record.txt | 14 ++++++++----
> > tools/perf/tests/parse-events.c | 34 ++++++++++++++++++++++++++++++
> > tools/perf/util/parse-events.c | 5 +++--
> > tools/perf/util/parse-events.h | 2 +-
> > tools/perf/util/parse-events.y | 14 ++++++++++--
> > 16 files changed, 125 insertions(+), 10 deletions(-)
> >
> > --
> > 1.7.9.5
> >
> >
>
prev parent reply other threads:[~2013-01-14 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 20:10 Jacob Shin
2013-01-10 20:10 ` [PATCH RESEND 1/5] perf: Add hardware breakpoint address mask Jacob Shin
2013-01-10 20:10 ` [PATCH RESEND 2/5] perf, x86: AMD implementation for " Jacob Shin
2013-01-10 20:10 ` [PATCH RESEND 3/5] perf tools: Add breakpoint address mask to the mem event parser Jacob Shin
2013-01-11 13:56 ` Jiri Olsa
2013-01-10 20:10 ` [PATCH RESEND 4/5] perf tools: Add breakpoint address mask syntax to perf list and documentation Jacob Shin
2013-01-10 20:10 ` [PATCH RESEND 5/5] perf tools: Add breakpoint address mask test case to tests/parse-events Jacob Shin
2013-01-11 13:54 ` [PATCH RESEND 0/5] perf: Add support for hardware breakpoint address masks Jiri Olsa
2013-01-14 17:21 ` Jacob Shin [this message]
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=20130114172135.GA5806@jshin-Toonie \
--to=jacob.shin@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®