linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Ignore deleted cgroups
Date: Fri, 10 May 2024 10:54:06 -0300	[thread overview]
Message-ID: <Zj4m_v5uEjmSLMb0@x1> (raw)
In-Reply-To: <20240509182235.2319599-1-namhyung@kernel.org>

On Thu, May 09, 2024 at 11:22:35AM -0700, Namhyung Kim wrote:
> On a large system, cgroups can be created and deleted often.  That means
> there's a race between perf tools and cgroups when it gets the cgroup
> name and opens the cgroup.  I got a report that perf stat with many
> cgroups failed a quite often due to the missing cgroups on such a large
> machine.
> 
> I think we can ignore such cgroups when expanding events and use id 0 if
> it fails to read the cgroup id.  IIUC 0 is not a vaild cgroup id so it
> won't update event counts for the failed cgroups.

Thanks, applied to perf-tools-next,

- Arnaldo
 
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
>  tools/perf/util/bpf_counter_cgroup.c | 5 ++---
>  tools/perf/util/cgroup.c             | 4 +++-
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/perf/util/bpf_counter_cgroup.c b/tools/perf/util/bpf_counter_cgroup.c
> index 1c82377ed78b..ea29c372f339 100644
> --- a/tools/perf/util/bpf_counter_cgroup.c
> +++ b/tools/perf/util/bpf_counter_cgroup.c
> @@ -136,9 +136,8 @@ static int bperf_load_program(struct evlist *evlist)
>  		cgrp = evsel->cgrp;
>  
>  		if (read_cgroup_id(cgrp) < 0) {
> -			pr_err("Failed to get cgroup id\n");
> -			err = -1;
> -			goto out;
> +			pr_debug("Failed to get cgroup id for %s\n", cgrp->name);
> +			cgrp->id = 0;
>  		}
>  
>  		map_fd = bpf_map__fd(skel->maps.cgrp_idx);
> diff --git a/tools/perf/util/cgroup.c b/tools/perf/util/cgroup.c
> index fcb509058499..0f759dd96db7 100644
> --- a/tools/perf/util/cgroup.c
> +++ b/tools/perf/util/cgroup.c
> @@ -465,9 +465,11 @@ int evlist__expand_cgroup(struct evlist *evlist, const char *str,
>  		name = cn->name + prefix_len;
>  		if (name[0] == '/' && name[1])
>  			name++;
> +
> +		/* the cgroup can go away in the meantime */
>  		cgrp = cgroup__new(name, open_cgroup);
>  		if (cgrp == NULL)
> -			goto out_err;
> +			continue;
>  
>  		leader = NULL;
>  		evlist__for_each_entry(orig_list, pos) {
> -- 
> 2.45.0.118.g7fe29c98d7-goog

      reply	other threads:[~2024-05-10 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 18:22 [PATCH] perf tools: Ignore deleted cgroups Namhyung Kim
2024-05-10 13:54 ` Arnaldo Carvalho de Melo [this message]

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=Zj4m_v5uEjmSLMb0@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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).