linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com
Subject: Re: [PATCH] perf record: Remove unnecessary warning for missing sysfs entry
Date: Thu, 12 Apr 2018 10:05:13 -0300	[thread overview]
Message-ID: <20180412130513.GB9818@kernel.org> (raw)
In-Reply-To: <20180412114723.48550-1-tmricht@linux.ibm.com>

Em Thu, Apr 12, 2018 at 01:47:23PM +0200, Thomas Richter escreveu:
> Using perf on 4.16.0 kernel on s390 shows warning
>    failed: can't open node sysfs data
> each time I run command perf record ... for example:
> 
> [root@s35lp76 perf]# ./perf record -e rB0000 -- sleep 1
> [ perf record: Woken up 1 times to write data ]
> failed: can't open node sysfs data
> [ perf record: Captured and wrote 0.001 MB perf.data (4 samples) ]
> [root@s35lp76 perf]#
> 
> BTW: I find this error message not very informative.

What an understatement :-)
 
> It turns out commit e2091cedd51bf ("perf tools: Add MEM_TOPOLOGY
> feature to perf data file") tries to open directory named
> /sys/devices/system/node/ which does not exist on s390.
> 
> This is the call stack:
>  __cmd_record
>  +---> perf_session__write_header
>        +---> perf_header__adds_write
>              +---> do_write_feat
> 	           +---> write_mem_topology
> 		         +---> build_mem_topology
> 			       prints warning
> The issue starts in do_write_feat() which unconditionally
> loops over all features and now includes HEADER_MEM_TOPOLOGY and calls
> write_mem_topology().
> Function record__init_features() at the beginning of __cmd_record()
> sets all features and then turns off some.
> 
> Fix this by removed the warning, if the directory is not present
> memory node information is not available and won't be displayed.

Can't we instead improve the error message and turn this into a
pr_debug2? Isn't it a reasonable scenario that the user expects this
topology information to be present and then ends up without it?

Perhaps something like:

	pr_debug2("%s: could't read %s, does this arch have topology information?\n", __func__, path);

- Arnaldo
 
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> ---
>  tools/perf/util/header.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index 121df1683c36..4a3bfc900a68 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -1320,7 +1320,6 @@ static int build_mem_topology(struct memory_node *nodes, u64 size, u64 *cntp)
>  
>  	dir = opendir(path);
>  	if (!dir) {
> -		pr_warning("failed: can't open node sysfs data\n");
>  		return -1;
>  	}
>  
> -- 
> 2.14.3

  reply	other threads:[~2018-04-12 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 11:47 [PATCH] perf record: Remove unnecessary warning for missing sysfs entry Thomas Richter
2018-04-12 13:05 ` Arnaldo Carvalho de Melo [this message]
2018-04-12 13:19   ` Thomas-Mich Richter

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=20180412130513.GB9818@kernel.org \
    --to=acme@kernel.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tmricht@linux.ibm.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).