From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kan.liang@linux.intel.com,
Adrian Hunter <adrian.hunter@intel.com>,
alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v6 7/7] perf intel-pt: Add brief documentation for PEBS via Intel PT
Date: Tue, 13 Aug 2019 19:21:39 +0300 [thread overview]
Message-ID: <87ftm52fzg.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190813141453.GB3754@redhat.com>
Arnaldo Carvalho de Melo <acme@redhat.com> writes:
> I've just blindly followed the provided documentation :)
Yes, I should have checked it also before I sent it out. :)
> So you say I should have tried this instead:
>
> # perf record -c 10000 -e '{intel_pt/branch=0/,cycles/aux-output/ppp}' uname
Right. For the purposes of illustrating the error condition, you can
probably drop the '-c ...' and 'branch=0' also, but either way is fine.
> Error:
> The 'aux_output' feature is not supported, update the kernel.
Or it's not supported by the hardware. I don't think we make a
distinction at the moment. You can tell if it's available from dmesg,
but not otherwise.
> #
>
> Or with leader sampling?
>
> # perf record -c 10000 -e '{intel_pt/branch=0/,cycles/aux-output/ppp}:S' uname
Not sure if we should even allow this. Maybe Adrian can chime in.
Thanks,
--
Alex
next prev parent reply other threads:[~2019-08-13 16:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 8:45 [PATCH v6 0/7] perf, intel: Add support for PEBS output to " Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 1/7] perf: Allow normal events to output AUX data Alexander Shishkin
2019-08-28 13:30 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 2/7] perf/x86/intel: Support PEBS output to PT Alexander Shishkin
2019-08-28 13:30 ` [tip: perf/core] " tip-bot2 for Alexander Shishkin
2019-08-06 8:46 ` [PATCH v6 3/7] perf tools: Add aux_output attribute flag Alexander Shishkin
2019-08-15 9:30 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 4/7] perf tools: Add itrace option 'o' to synthesize aux-output events Alexander Shishkin
2019-08-15 9:30 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 5/7] perf intel-pt: Process options for PEBS event synthesis Alexander Shishkin
2019-08-15 9:31 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 6/7] perf tools: Add aux-output config term Alexander Shishkin
2019-08-15 9:32 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 8:46 ` [PATCH v6 7/7] perf intel-pt: Add brief documentation for PEBS via Intel PT Alexander Shishkin
2019-08-13 13:51 ` Arnaldo Carvalho de Melo
2019-08-13 14:05 ` Alexander Shishkin
2019-08-13 14:14 ` Arnaldo Carvalho de Melo
2019-08-13 16:21 ` Alexander Shishkin [this message]
2019-08-15 9:33 ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-08-06 14:30 ` [PATCH v6 0/7] perf, intel: Add support for PEBS output to " Peter Zijlstra
2019-08-06 14:43 ` Arnaldo Carvalho de Melo
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=87ftm52fzg.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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®