All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Fix inheritance of aux_output groups
Date: Mon, 7 Oct 2019 16:49:54 +0200	[thread overview]
Message-ID: <20191007144954.GA88143@gmail.com> (raw)
In-Reply-To: <20191004125729.32397-1-alexander.shishkin@linux.intel.com>


* Alexander Shishkin <alexander.shishkin@linux.intel.com> wrote:

> Commit
> 
>   b43762ef010 ("perf: Allow normal events to output AUX data")

Missing 'a', the proper SHA1 is:

    ab43762ef010 ("perf: Allow normal events to output AUX data")

:-)

> forgets to configure aux_output relation in the inherited groups, which
> results in child PEBS events forever failing to schedule.
> 
> Fix this by setting up the AUX output link in the inheritance path.
> 
> Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> ---
>  kernel/events/core.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index f5bb2557d5f6..761995f21b30 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -12024,6 +12024,10 @@ static int inherit_group(struct perf_event *parent_event,
>  					    child, leader, child_ctx);
>  		if (IS_ERR(child_ctr))
>  			return PTR_ERR(child_ctr);
> +
> +		if (sub->aux_event == parent_event &&
> +		    !perf_get_aux_event(child_ctr, leader))
> +			return -EINVAL;

Could this explain weird 'perf top' failures I'm seeing on my desktop, 
which I was just about to debug and report?

Thanks,

	Ingo

  reply	other threads:[~2019-10-07 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 12:57 [PATCH] perf: Fix inheritance of aux_output groups Alexander Shishkin
2019-10-07 14:49 ` Ingo Molnar [this message]
2019-10-07 15:01   ` Alexander Shishkin
2019-10-07 14:55 ` [tip: perf/urgent] perf/core: " tip-bot2 for 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=20191007144954.GA88143@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@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 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.