From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"Liang, Kan" <kan.liang@intel.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] perf record: enable multiplexing scaling via -R
Date: Mon, 21 Aug 2017 18:25:45 -0700 [thread overview]
Message-ID: <20170822012545.GJ2482@two.firstfloor.org> (raw)
In-Reply-To: <CABPqkBR1F8c2sjntSxR7fTbbh_1pp6bp=aG2BnHUAYq-hzUg5A@mail.gmail.com>
On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote:
> On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen <andi@firstfloor.org> wrote:
> >
> > Stephane Eranian <eranian@google.com> writes:
> > >
> > > To activate, the user must use:
> > > $ perf record -a -R ....
> >
> > I don't know why you're overloading the existing raw mode?
> >
> > It has nothing to do with that.
> >
> I explained this in the changelog. So that is does not change any of
> the processing in perf report, i.e., no faced with data it does not
> know how to handle.
> Also trying to avoid adding yet another option.
But raw is needed for some of the non Intel PMUs. I believe it's
the only way to use AMD IBS. You may as well break their usage.
You'll need a new option.
-Andi
next prev parent reply other threads:[~2017-08-22 1:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:14 [PATCH] perf record: enable multiplexing scaling via -R Stephane Eranian
2017-08-21 23:02 ` Andi Kleen
2017-08-22 0:13 ` Stephane Eranian
2017-08-22 1:25 ` Andi Kleen [this message]
2017-08-22 7:03 ` Jiri Olsa
2017-08-22 7:24 ` Stephane Eranian
2017-08-28 19:27 ` Stephane Eranian
2017-08-28 20:41 ` Andi Kleen
2017-08-31 6:21 ` Stephane Eranian
2017-09-01 7:55 ` Jiri Olsa
2017-09-01 7:59 ` Jiri Olsa
2017-09-01 8:21 ` Stephane Eranian
2017-09-01 8:31 ` Jiri Olsa
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=20170822012545.GJ2482@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.