From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH V3 0/5] bugs fix for large PEBS mmap read and rdpmc read
Date: Wed, 31 Jan 2018 16:41:28 +0100 [thread overview]
Message-ID: <20180131154128.GA2812@krava> (raw)
In-Reply-To: <b16cfe20-53e0-088b-f833-131e0e9e2210@linux.intel.com>
On Wed, Jan 31, 2018 at 10:15:33AM -0500, Liang, Kan wrote:
>
>
> On 1/31/2018 8:15 AM, Jiri Olsa wrote:
> > On Wed, Jan 31, 2018 at 10:15:39AM +0100, Jiri Olsa wrote:
> > > On Tue, Jan 30, 2018 at 07:59:41PM -0800, Andi Kleen wrote:
> > > > > Still, the part I am missing here, is why asking for
> > > > > PERF_SAMPLE_PERIOD voids large PEBS.
> > > >
> > > > I think it was disabled together with frequency mode
> > > > (which we could support too, but it's a bit more work)
> > > >
> > > > But yes PERIOD could probably be allowed.
> > >
> > > looks like it's just a matter of adding PERF_SAMPLE_PERIOD
> > > into PEBS_FREERUNNING_FLAGS, we already populate period
> > > in setup_pebs_sample_data
> > >
> > > jirka
> > >
> > >
> > > ---
> > > diff --git a/arch/x86/events/perf_event.h b/arch/x86/events/perf_event.h
> > > index 8e4ea143ed96..78f91ec1056e 100644
> > > --- a/arch/x86/events/perf_event.h
> > > +++ b/arch/x86/events/perf_event.h
> > > @@ -93,7 +93,8 @@ struct amd_nb {
> > > PERF_SAMPLE_ID | PERF_SAMPLE_CPU | PERF_SAMPLE_STREAM_ID | \
> > > PERF_SAMPLE_DATA_SRC | PERF_SAMPLE_IDENTIFIER | \
> > > PERF_SAMPLE_TRANSACTION | PERF_SAMPLE_PHYS_ADDR | \
> > > - PERF_SAMPLE_REGS_INTR | PERF_SAMPLE_REGS_USER)
> > > + PERF_SAMPLE_REGS_INTR | PERF_SAMPLE_REGS_USER | \
> > > + PERF_SAMPLE_PERIOD)
> >
> > seems to work, getting large PEBS event for following command line:
> >
> > perf record -e cycles:P -c 100 --no-timestamp -C 0 --period
> >
> >
>
> Yes, I tried the patch. The large PEBS can be enabled with the PERIOD flag.
> Everything looks good.
>
> Jirka, could you please post the patch as well?
yes, will post that one as well
jirka
next prev parent reply other threads:[~2018-01-31 15:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 16:29 [PATCH V3 0/5] bugs fix for large PEBS mmap read and rdpmc read kan.liang
2018-01-29 16:29 ` [PATCH V3 1/5] perf/x86/intel: fix event update for auto-reload kan.liang
2018-02-06 15:06 ` Peter Zijlstra
2018-02-06 17:58 ` Liang, Kan
2018-02-09 14:09 ` Peter Zijlstra
2018-02-09 15:49 ` Liang, Kan
2018-02-10 14:09 ` Peter Zijlstra
2018-01-29 16:29 ` [PATCH V3 2/5] perf/x86: introduce read function for x86_pmu kan.liang
2018-01-29 16:29 ` [PATCH V3 3/5] perf/x86/intel/ds: introduce read function for large pebs kan.liang
2018-01-29 16:29 ` [PATCH V3 4/5] perf/x86/intel: fix pmu read for large PEBS kan.liang
2018-01-29 16:29 ` [PATCH V3 5/5] perf/x86: fix: disable userspace RDPMC usage " kan.liang
2018-01-30 9:16 ` [PATCH V3 0/5] bugs fix for large PEBS mmap read and rdpmc read Stephane Eranian
2018-01-30 13:39 ` Jiri Olsa
2018-01-30 14:59 ` Liang, Kan
2018-01-30 15:04 ` Jiri Olsa
2018-01-30 15:25 ` Liang, Kan
2018-01-30 16:36 ` Stephane Eranian
2018-01-30 16:48 ` Liang, Kan
2018-01-30 18:52 ` Jiri Olsa
2018-01-30 19:56 ` Stephane Eranian
2018-01-31 3:59 ` Andi Kleen
2018-01-31 9:15 ` Jiri Olsa
2018-01-31 13:15 ` Jiri Olsa
2018-01-31 15:15 ` Liang, Kan
2018-01-31 15:41 ` Jiri Olsa [this message]
2018-01-30 14:41 ` 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=20180131154128.GA2812@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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