linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Jin Yao <yao.jin@linux.intel.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf stat: Poll for monitored tasks being alive
Date: Mon, 22 Oct 2018 11:56:43 -0300	[thread overview]
Message-ID: <20181022145643.GI3849@kernel.org> (raw)
In-Reply-To: <20181022093015.9106-1-jolsa@kernel.org>

Em Mon, Oct 22, 2018 at 11:30:15AM +0200, Jiri Olsa escreveu:
> Adding the check for tasks we monitor via -p/-t options,
> and finish stat if there's no longer task to monitor.

Wonder if instead of doing all those scnprintf, etc, we couldn't have a
perf ring buffer with a dummy event and then ask for PERF_RECORD_EXIT on
it, poll it, etc.

Thought about using getpgid(pid) but thagt also involves radix tree
lookups, so should also be more expensive than asking the kernel perf to
tell us about the exits.

Anyway, that can be done on top, if someone is interested, applying.

- Arnaldo
 
> Cc: Jin Yao <yao.jin@linux.intel.com>
> Requested-by: Stephane Eranian <eranian@google.com>
> Link: http://lkml.kernel.org/n/tip-dfqvnvz0oqu5zg149aquz1jb@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
>  tools/perf/builtin-stat.c | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index b86aba1c8028..d1028d7755bb 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -409,6 +409,28 @@ static struct perf_evsel *perf_evsel__reset_weak_group(struct perf_evsel *evsel)
>  	return leader;
>  }
>  
> +static bool is_target_alive(struct target *_target,
> +			    struct thread_map *threads)
> +{
> +	struct stat st;
> +	int i;
> +
> +	if (!target__has_task(_target))
> +		return true;
> +
> +	for (i = 0; i < threads->nr; i++) {
> +		char path[PATH_MAX];
> +
> +		scnprintf(path, PATH_MAX, "%s/%d", procfs__mountpoint(),
> +			  threads->map[i].pid);
> +
> +		if (!stat(path, &st))
> +			return true;
> +	}
> +
> +	return false;
> +}
> +
>  static int __run_perf_stat(int argc, const char **argv, int run_idx)
>  {
>  	int interval = stat_config.interval;
> @@ -579,6 +601,8 @@ static int __run_perf_stat(int argc, const char **argv, int run_idx)
>  		enable_counters();
>  		while (!done) {
>  			nanosleep(&ts, NULL);
> +			if (!is_target_alive(&target, evsel_list->threads))
> +				break;
>  			if (timeout)
>  				break;
>  			if (interval) {
> -- 
> 2.17.2

  reply	other threads:[~2018-10-22 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22  9:30 [PATCH] perf stat: Poll for monitored tasks being alive Jiri Olsa
2018-10-22 14:56 ` Arnaldo Carvalho de Melo [this message]
2018-10-26  7:33 ` [tip:perf/urgent] " tip-bot for 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=20181022145643.GI3849@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=yao.jin@linux.intel.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).