From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org, acme@kernel.org, namhyung@kernel.org
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH] perf: Fix "Track with sched_switch" test by not printing warnings in quiet mode
Date: Wed, 12 Oct 2022 12:13:36 +0100 [thread overview]
Message-ID: <62f485df-4f5e-64a2-1294-6e162de25556@arm.com> (raw)
In-Reply-To: <20221012111025.30609-1-james.clark@arm.com>
On 12/10/2022 12:10, James Clark wrote:
> Especially when CONFIG_LOCKDEP and other debug configs are enabled,
> Perf can print the following warning when running the "Track with
> sched_switch" test:
Oops got the wrong test name here and in the title. Should be "kernel
lock contention analysis test"
>
> Warning:
> Processed 1378918 events and lost 4 chunks!
>
> Check IO/CPU overload!
>
> Warning:
> Processed 4593325 samples and lost 70.00%!
>
> The test already supplies -q to run in quiet mode, so extend quiet mode
> to perf_stdio__warning() and also ui__warning() for consistency.
>
> This fixes the following failure due to the extra lines counted:
>
> perf test "lock cont" -vvv
>
> 82: kernel lock contention analysis test :
> --- start ---
> test child forked, pid 3125
> Testing perf lock record and perf lock contention
> [Fail] Recorded result count is not 1: 9
> test child finished with -1
> ---- end ----
> kernel lock contention analysis test: FAILED!
>
> Fixes: ec685de25b67 ("perf test: Add kernel lock contention test")
> Cc: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: James Clark <james.clark@arm.com>
> ---
> tools/perf/ui/util.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tools/perf/ui/util.c b/tools/perf/ui/util.c
> index 689b27c34246..1d38ddf01b60 100644
> --- a/tools/perf/ui/util.c
> +++ b/tools/perf/ui/util.c
> @@ -15,6 +15,9 @@ static int perf_stdio__error(const char *format, va_list args)
>
> static int perf_stdio__warning(const char *format, va_list args)
> {
> + if (quiet)
> + return 0;
> +
> fprintf(stderr, "Warning:\n");
> vfprintf(stderr, format, args);
> return 0;
> @@ -45,6 +48,8 @@ int ui__warning(const char *format, ...)
> {
> int ret;
> va_list args;
> + if (quiet)
> + return 0;
>
> va_start(args, format);
> ret = perf_eops->warning(format, args);
next prev parent reply other threads:[~2022-10-12 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 11:10 James Clark
2022-10-12 11:13 ` James Clark [this message]
2022-10-12 16:50 ` Namhyung Kim
2022-10-12 17:12 ` James Clark
2022-10-13 16:57 ` Namhyung Kim
2022-10-14 9:47 ` James Clark
2022-10-17 12:33 ` Arnaldo Carvalho de Melo
2022-10-17 23:47 ` Namhyung Kim
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=62f485df-4f5e-64a2-1294-6e162de25556@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®