mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Jihong <yangjihong1@huawei.com>
To: Adrian Hunter <adrian.hunter@intel.com>, <peterz@infradead.org>,
	<mingo@redhat.com>, <acme@kernel.org>, <mark.rutland@arm.com>,
	<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
	<namhyung@kernel.org>, <irogers@google.com>,
	<kan.liang@linux.intel.com>, <kim.phillips@amd.com>,
	<german.gomez@arm.com>, <ravi.bangoria@amd.com>,
	<linux-perf-users@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tool: Fix output unexpected messages in quiet mode
Date: Mon, 19 Dec 2022 21:14:08 +0800	[thread overview]
Message-ID: <0e06416c-fac3-1149-2660-9a1981e3460d@huawei.com> (raw)
In-Reply-To: <d2189ccc-26aa-250a-ad43-59d53ef01d5e@intel.com>

Hello,

On 2022/12/19 18:28, Adrian Hunter wrote:
> On 19/12/22 11:28, Yang Jihong wrote:
>> Hello,
>>
>> On 2022/12/19 14:59, Adrian Hunter wrote:
>>> On 19/12/22 04:49, Yang Jihong wrote:
>>>> When perf uses quiet mode, perf_quiet_option sets debug_peo_args to -1,
>>>
>>> Seems like redirect_to_stderr has similar issue?
>> The redirect_to_stderr is used only in the veprintf function:
>>
>>    int veprintf(int level, int var, const char *fmt, va_list args)
>>    {
>>            int ret = 0;
>>
>>            if (var >= level) {
>>                    if (use_browser >= 1 && redirect_to_stderr <= 0) {
>>                            ui_helpline__vshow(fmt, args);
>>                    } else {
>>                            ret = fprintf_time(debug_file);
>>                            ret += vfprintf(debug_file, fmt, args);
>>                    }
>>            }
>>
>>            return ret;
>>    }
>>
>> If use quiet mode, verbose sets to -1. (also assigned in the perf_quiet_option function)
>> Because "var >= level" is false, veprintf function returns directly, which avoids this problem.
>>
>> However, there are cases where:
>>    # perf --debug stderr=-1 report -vvv 2>/tmp/debug
>>
>> If stderr is -1, should we redirect pr_debug in this case?
> 
> tools/perf/Documentation/perf.txt says debug variables are in value
> range (0, 10), so -1 is invalid anyway.
> 
Okay, I see.
>>
>> Because I'm not sure if this is a problem,
>> if redirect_to_stderr needs to be fixed as well,
>> let me know and I'll submit a patch to fix it.
> 
> perf_quiet_option() sets redirect_to_stderr = -1 with the intention
> that it turns it off, but it doesn't, although it gets turned of by
> verbose = -1. Perhaps set redirect_to_stderr = 0 in perf_quiet_option() ?
> 
I think it's better to fix redirect_to_stderr and debug_peo_args in the 
same way (because they're similar):

Solution A:
   diff --git a/tools/perf/util/debug.c b/tools/perf/util/debug.c
   index 65e6c22f38e4..908b26e579e5 100644
   --- a/tools/perf/util/debug.c
   +++ b/tools/perf/util/debug.c
   @@ -68,7 +68,7 @@ int veprintf(int level, int var, const char *fmt, 
va_list args)
           int ret = 0;

           if (var >= level) {
   -               if (use_browser >= 1 && !redirect_to_stderr) {
   +               if (use_browser >= 1 && redirect_to_stderr <= 0) {
                           ui_helpline__vshow(fmt, args);
                   } else {
                           ret = fprintf_time(debug_file);
   diff --git a/tools/perf/util/debug.h b/tools/perf/util/debug.h
   index f99468a7f681..f6ab84c93ec0 100644
   --- a/tools/perf/util/debug.h
   +++ b/tools/perf/util/debug.h
   @@ -41,7 +41,7 @@ extern int debug_data_convert;

    /* Special macro to print perf_event_open arguments/return value. */
    #define pr_debug2_peo(fmt, ...) {                              \
   -       if (debug_peo_args)                                             \
   +       if (debug_peo_args > 0)                                         \
                   pr_debugN(0, pr_fmt(fmt), ##__VA_ARGS__);       \
           else                                                    \
                   pr_debugN(2, pr_fmt(fmt), ##__VA_ARGS__);       \
   diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
   index 999dd1700502..45cf144c5d5d 100644
   --- a/tools/perf/util/evsel.c
   +++ b/tools/perf/util/evsel.c
   @@ -1775,7 +1775,7 @@ static int __open_attr__fprintf(FILE *fp, const 
char *name, const char *val,

    static void display_attr(struct perf_event_attr *attr)
    {
   -       if (verbose >= 2 || debug_peo_args) {
   +       if (verbose >= 2 || debug_peo_args > 0) {
                   fprintf(stderr, "%.60s\n", graph_dotted_line);
                   fprintf(stderr, "perf_event_attr:\n");
                   perf_event_attr__fprintf(stderr, attr, 
__open_attr__fprintf, NULL);

or
Solution B:

   diff --git a/tools/perf/util/debug.c b/tools/perf/util/debug.c
   index 908b26e579e5..e3acc213edd1 100644
   --- a/tools/perf/util/debug.c
   +++ b/tools/perf/util/debug.c
   @@ -241,6 +241,9 @@ int perf_quiet_option(void)
                   opt++;
           }

   +       redirect_to_stderr = 0;
   +       debug_peo_args = 0;
   +

> I see we have another problem as well: places that check "if (verbose)"
> instead of "if (verbose > 0)"
Yes,  places that "if (verbose)" also have problems, I'll submit a patch 
to change them to "if (verbose > 0)"

In addition, I found another problem, perf lock/stat/probe does not call 
the perf_quiet_option function when quiet is true.

Thanks,
Yang

  reply	other threads:[~2022-12-19 13:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  2:49 Yang Jihong
2022-12-19  6:59 ` Adrian Hunter
2022-12-19  9:28   ` Yang Jihong
2022-12-19 10:28     ` Adrian Hunter
2022-12-19 13:14       ` Yang Jihong [this message]
2022-12-19 13:19         ` Adrian Hunter

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=0e06416c-fac3-1149-2660-9a1981e3460d@huawei.com \
    --to=yangjihong1@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=german.gomez@arm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kim.phillips@amd.com \
    --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 \
    --cc=ravi.bangoria@amd.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

all inboxes | Powered by JetHome®