mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: linux-kernel@vger.kernel.org,
	Alexei Starovoitov <ast@plumgrid.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Li Zefan <lizefan@huawei.com>,
	pi3orama@163.com
Subject: Re: [RFC PATCH] perf tools: Don't set inherit bit for system wide evsel
Date: Fri, 23 Oct 2015 10:51:41 -0300	[thread overview]
Message-ID: <20151023135141.GD27006@kernel.org> (raw)
In-Reply-To: <1445597029-133332-1-git-send-email-wangnan0@huawei.com>

Em Fri, Oct 23, 2015 at 10:43:49AM +0000, Wang Nan escreveu:
> Inherit bit is useless for a system wide evsel [1]. Further kernel
> improvements are giving more constrain [2] on inherit events. This
> patch set inherit bit to 0 to avoid potential constrains.
> 
> [1] http://lkml.kernel.org/r/20151022124142.GQ17308@twins.programming.kicks-ass.net
> [2] http://lkml.kernel.org/r/1445559014-4667-1-git-send-email-ast@kernel.org
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Alexei Starovoitov <ast@plumgrid.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Li Zefan <lizefan@huawei.com>
> Cc: pi3orama@163.com
> Link: http://lkml.kernel.org/n/ebpf-0tgilipxoo6fiebcxu3ft866@git.kernel.org
> ---
> 
> evsel->system_wide doesn't correct reflect whether this evsel is system
> wide or not, so checks pid when invoking perf_event_open, and it is
> always correct.

Can't we do this at perf_evlist__config() or perf_evsel__config() time?

We have record_opts at perf_evsel__config() time and I think we should
leave changing the attr at perf_evsel__open() time for feature
fallbacks, i.e. something we will only know when trying to use, which is
different from this inherit-on-syswide case, that we know far in advance
we will not need.

- Arnaldo
 
> ---
>  tools/perf/util/evsel.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index 5566b16..e2d6c9a 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -1337,6 +1337,7 @@ retry_sample_id:
>  
>  		for (thread = 0; thread < nthreads; thread++) {
>  			int group_fd;
> +			struct perf_event_attr attr;
>  
>  			if (!evsel->cgrp && !evsel->system_wide)
>  				pid = thread_map__pid(threads, thread);
> @@ -1346,7 +1347,10 @@ retry_open:
>  			pr_debug2("sys_perf_event_open: pid %d  cpu %d  group_fd %d  flags %#lx\n",
>  				  pid, cpus->map[cpu], group_fd, flags);
>  
> -			FD(evsel, cpu, thread) = sys_perf_event_open(&evsel->attr,
> +			attr = evsel->attr;
> +			if (pid == -1)
> +				attr.inherit = 0;
> +			FD(evsel, cpu, thread) = sys_perf_event_open(&attr,
>  								     pid,
>  								     cpus->map[cpu],
>  								     group_fd, flags);
> -- 
> 1.8.3.4

  reply	other threads:[~2015-10-23 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 10:43 Wang Nan
2015-10-23 13:51 ` Arnaldo Carvalho de Melo [this message]
2015-10-23 13:58   ` pi3orama
2015-10-23 16:17     ` Arnaldo Carvalho de Melo
2015-10-26  9:08       ` Wangnan (F)
2015-10-26  9:25         ` Adrian Hunter
2015-10-26 11:48           ` Wangnan (F)

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=20151023135141.GD27006@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ast@plumgrid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.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

Powered by JetHome