From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"acme@kernel.org" <acme@kernel.org>,
"eranian@google.com" <eranian@google.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/8] perf: Add PERF_SAMPLE_PHYS_ADDR
Date: Thu, 7 Jan 2016 20:31:25 +0100 [thread overview]
Message-ID: <20160107193125.GA31607@krava.brq.redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F0770586DED0@SHSMSX103.ccr.corp.intel.com>
On Thu, Jan 07, 2016 at 03:55:23PM +0000, Liang, Kan wrote:
>
>
> > On Wed, Jan 06, 2016 at 06:04:30AM -0500, kan.liang@intel.com wrote:
> > > From: Kan Liang <kan.liang@intel.com>
> > >
> > > For understanding how the workload maps to memory channels and
> > > hardware behavior, it's useful to collect address maps with physical
> > addresses.
> > > This is not intended for detecting page sharing (which can be already
> > > done using the mmap inode), but for lower level hardware behavior
> > > studies.
> > > Perf supports load latency/DLA which can only collect virtual addresses.
> > > This patch add a new sample type PERF_SAMPLE_PHYS_ADDR to expose
> > the
> > > physical addresses.
> > > For kernel direct mapping addresses, the patch uses virt_to_phys to
> > > convert the virtual addresses from DLA to physical address.
> > > For user virtual addresses, __get_user_pages_fast is used to walk the
> > > pages tables for user physical address.
> > > This does not work for vmalloc addresses. Right now these are not
> > > resolved, but code to do that could be added.
> > > For security, the physical address can only be exposed to root or
> > > privileged user.
> > >
> > > Signed-off-by: Kan Liang <kan.liang@intel.com>
> > > ---
> > > arch/x86/kernel/cpu/perf_event.h | 2 +-
> > > arch/x86/kernel/cpu/perf_event_intel_ds.c | 23
> > +++++++++++++++++++++++
> > > include/linux/perf_event.h | 3 +++
> > > include/uapi/linux/perf_event.h | 4 +++-
> > > kernel/events/core.c | 11 +++++++++++
> > > 5 files changed, 41 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/x86/kernel/cpu/perf_event.h
> > > b/arch/x86/kernel/cpu/perf_event.h
> > > index 799e6bd..164de68 100644
> > > --- a/arch/x86/kernel/cpu/perf_event.h
> > > +++ b/arch/x86/kernel/cpu/perf_event.h
> > > @@ -90,7 +90,7 @@ struct amd_nb {
> > > (PERF_SAMPLE_IP | PERF_SAMPLE_TID | PERF_SAMPLE_ADDR | \
> > > PERF_SAMPLE_ID | PERF_SAMPLE_CPU |
> > PERF_SAMPLE_STREAM_ID | \
> > > PERF_SAMPLE_DATA_SRC | PERF_SAMPLE_IDENTIFIER | \
> > > - PERF_SAMPLE_TRANSACTION)
> > > + PERF_SAMPLE_TRANSACTION | PERF_SAMPLE_PHYS_ADDR)
> >
> > could you please add some probe code to detect kernel support, so we get
> > some sensible error message
> >
>
> I'm not quite sure what kind of probe code do you mean.
> Yes, the error message below is not accurate. It could be some errors in
> sample_type, read_format, branch_sample_type or something else.
> Because they share the same error code -EINVAL. Perf tool cannot know
> more.
> I think we may print some error kernel messages when invalid attr is
> detected. So the user can get more detail messages from dmesg.
>
> Or you want me to add some extra code to detect the kernel capability
> before opening event? If so, I think we may do it in separate patches.
yep, could be done later
jirka
next prev parent reply other threads:[~2016-01-07 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 11:04 kan.liang
2016-01-06 11:04 ` [PATCH 2/8] perf tools: add option to record sample physical address kan.liang
2016-01-07 9:56 ` Jiri Olsa
2016-01-06 11:04 ` [PATCH 3/8] perf tools: add sort option phys_daddr kan.liang
2016-01-06 11:04 ` [PATCH 4/8] perf mem: add option phys-data to record physical address kan.liang
2016-01-06 11:04 ` [PATCH 5/8] perf mem: report physical addresses kan.liang
2016-01-07 8:27 ` Jiri Olsa
2016-01-06 11:04 ` [PATCH 6/8] perf mem: dump " kan.liang
2016-01-06 11:04 ` [PATCH 7/8] perf script: support physical addresses in script kan.liang
2016-01-07 9:54 ` Jiri Olsa
2016-01-06 11:04 ` [PATCH 8/8] perf test: add test case for PERF_SAMPLE_PHYS_ADDR kan.liang
2016-01-06 19:21 ` [PATCH 1/8] perf: Add PERF_SAMPLE_PHYS_ADDR Stephane Eranian
2016-01-07 8:33 ` Jiri Olsa
2016-01-07 15:55 ` Liang, Kan
2016-01-07 19:31 ` Jiri Olsa [this message]
2016-01-07 21:50 ` Stephane Eranian
2016-01-08 21:12 ` Liang, Kan
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=20160107193125.GA31607@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome