mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Jason Wessel <jason.wessel@windriver.com>, acme@ghostprotocols.net
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Do not require /lib/modules/* on a guest
Date: Mon, 29 Jul 2013 16:40:58 -0600	[thread overview]
Message-ID: <51F6EF7A.4000209@gmail.com> (raw)
In-Reply-To: <1373920073-4874-1-git-send-email-jason.wessel@windriver.com>

On 7/15/13 2:27 PM, Jason Wessel wrote:
> For some types of work loads and special guest environments, you might
> have a kernel that has no kernel modules.  The perf kvm record tool
> fails instantiate vmlinux maps when the kernel modules directory
> cannot be opened, even though the kallsyms has been properly
> processed.  This leads to a perf kvm report that has no guest symbols
> resolved.

Theoretically, use of modules is an option:

     if (symbol_conf.use_modules && machine__create_modules(machine) < 0) {
...
     }

But, the use_modules option was flipped from false to true by b32d133a 
back in 2009. And the lack of complaints suggests this ominous warning 
in perf-report, diff and annotate is moot:

     OPT_BOOLEAN('m', "modules", &symbol_conf.use_modules,
             "load module symbols - WARNING: use only with -k and LIVE 
kernel"),

>
> This patch changes the failure to locate kernel modules to be
> non-fatal.
>
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
>   tools/perf/util/machine.c |    5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index b2ecad6..eb9ebd6 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -808,7 +808,10 @@ static int machine__create_modules(struct machine *machine)
>   	free(line);
>   	fclose(file);
>
> -	return machine__set_modules_path(machine);
> +	if (machine__set_modules_path(machine) < 0) {
> +		pr_debug("Problems setting modules path maps, continuing anyway...\n");
> +	}
> +	return 0;
>
>   out_delete_line:
>   	free(line);

Acked-by: David Ahern <dsahern@gmail.com>


  reply	other threads:[~2013-07-29 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 20:27 Jason Wessel
2013-07-29 22:40 ` David Ahern [this message]
2013-08-12 10:24 ` [tip:perf/core] perf machine: Do not require /lib/modules/ * " tip-bot for Jason Wessel

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=51F6EF7A.4000209@gmail.com \
    --to=dsahern@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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

Powered by JetHome