From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kan.liang@linux.intel.com
Subject: Re: [PATCH v3 2/7] perf/x86/intel: Support PEBS output to PT
Date: Wed, 31 Jul 2019 18:50:14 +0200 [thread overview]
Message-ID: <20190731165014.GY31381@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190731143041.64678-3-alexander.shishkin@linux.intel.com>
On Wed, Jul 31, 2019 at 05:30:36PM +0300, Alexander Shishkin wrote:
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index cfe256ca76df..6cf2a7ba822a 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -1006,6 +1006,28 @@ static int collect_events(struct cpu_hw_events *cpuc, struct perf_event *leader,
> /* current number of events already accepted */
> n = cpuc->n_events;
>
> + if (!cpuc->is_fake && leader->attr.precise_ip) {
> + if (!n)
> + cpuc->pebs_output = 0;
I think this can go wobbly if we add a !pebs event first.
That is, in that case '!n && !precise_ip' and we'll not reset the output
state.
> +
> + /*
> + * For PEBS->PT, if !aux_event, the group leader (PT) went
> + * away, the group was broken down and this singleton event
> + * can't schedule any more.
> + */
> + if (WARN_ON_ONCE(is_pebs_pt(leader) && !leader->aux_event))
> + return -EINVAL;
> +
> + /*
> + * pebs_output: 0: no PEBS so far, 1: PT, 2: DS
> + */
> + if (cpuc->pebs_output &&
> + cpuc->pebs_output != is_pebs_pt(leader) + 1)
> + return -EINVAL;
> +
> + cpuc->pebs_output = is_pebs_pt(leader) + 1;
> + }
> +
> if (is_x86_event(leader)) {
> if (n >= max_count)
> return -EINVAL;
next prev parent reply other threads:[~2019-07-31 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:30 [PATCH v3 0/7] perf, intel: Add support for PEBS output to Intel PT Alexander Shishkin
2019-07-31 14:30 ` [PATCH v3 1/7] perf: Allow normal events to be sources of AUX data Alexander Shishkin
2019-07-31 16:16 ` Peter Zijlstra
2019-07-31 16:21 ` Peter Zijlstra
2019-07-31 14:30 ` [PATCH v3 2/7] perf/x86/intel: Support PEBS output to PT Alexander Shishkin
2019-07-31 16:50 ` Peter Zijlstra [this message]
2019-07-31 14:30 ` [PATCH v3 3/7] perf tools: Add aux_source attribute flag Alexander Shishkin
2019-07-31 14:30 ` [PATCH v3 4/7] perf tools: Add itrace option 'o' to synthesize aux-source events Alexander Shishkin
2019-07-31 14:30 ` [PATCH v3 5/7] perf intel-pt: Process options for PEBS event synthesis Alexander Shishkin
2019-07-31 14:30 ` [PATCH v3 6/7] perf tools: Add aux-source config term Alexander Shishkin
2019-07-31 14:30 ` [PATCH v3 7/7] perf intel-pt: Add brief documentation for PEBS via Intel PT Alexander Shishkin
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=20190731165014.GY31381@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.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;
as well as URLs for NNTP newsgroup(s).