All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf: Fix build on architectures without CONFIG_PERF_REGS
Date: Thu, 8 Oct 2015 14:59:53 -0300	[thread overview]
Message-ID: <20151008175953.GH14409@kernel.org> (raw)
In-Reply-To: <1444323185.2956.260.camel@decadent.org.uk>

Em Thu, Oct 08, 2015 at 05:53:05PM +0100, Ben Hutchings escreveu:
> perf currently fails to link on all architectures other than arm,
> arm64 and x86:

This was fixed recently, merged already, check:

https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=perf/urgent&id=9fb4765451f22c5e782c1590747717550bff34b2
 
> tools/perf/libperf.a(libperf-in.o): In function `parse_regs':
> tools/perf/util/parse-regs-options.c:28: undefined reference to `sample_reg_masks'
> tools/perf/util/parse-regs-options.c:28: undefined reference to `sample_reg_masks'
> tools/perf/util/parse-regs-options.c:45: undefined reference to `sample_reg_masks'
> tools/perf/util/parse-regs-options.c:38: undefined reference to `sample_reg_masks'
> 
> Fixes: bcc84ec65ad1 ("perf record: Add ability to name registers to record")
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Cc: Stephane Eranian <eranian@google.com>
> ---
>  tools/perf/builtin-record.c | 2 ++
>  tools/perf/util/Build       | 2 +-
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 142eeb3..34dd749c 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -1082,9 +1082,11 @@ struct option __record_options[] = {
>  		    "sample transaction flags (special events only)"),
>  	OPT_BOOLEAN(0, "per-thread", &record.opts.target.per_thread,
>  		    "use per-thread mmaps"),
> +#ifdef CONFIG_PERF_REGS
>  	OPT_CALLBACK_OPTARG('I', "intr-regs", &record.opts.sample_intr_regs, NULL, "any register",
>  		    "sample selected machine registers on interrupt,"
>  		    " use -I ? to list register names", parse_regs),
> +#endif
>  	OPT_BOOLEAN(0, "running-time", &record.opts.running_time,
>  		    "Record running/enabled time of read (:S) events"),
>  	OPT_CALLBACK('k', "clockid", &record.opts,
> diff --git a/tools/perf/util/Build b/tools/perf/util/Build
> index 349bc96..333b08d 100644
> --- a/tools/perf/util/Build
> +++ b/tools/perf/util/Build
> @@ -83,7 +83,7 @@ libperf-$(CONFIG_AUXTRACE) += intel-pt-decoder/
>  libperf-$(CONFIG_AUXTRACE) += intel-pt.o
>  libperf-$(CONFIG_AUXTRACE) += intel-bts.o
>  libperf-y += parse-branch-options.o
> -libperf-y += parse-regs-options.o
> +libperf-$(CONFIG_PERF_REGS) += parse-regs-options.o
>  
>  libperf-$(CONFIG_LIBELF) += symbol-elf.o
>  libperf-$(CONFIG_LIBELF) += probe-file.o
> -- 
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.



  reply	other threads:[~2015-10-08 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 16:53 [PATCH] perf: Fix build on architectures without CONFIG_PERF_REGS Ben Hutchings
2015-10-08 17:59 ` Arnaldo Carvalho de Melo [this message]
2015-10-08 19:37   ` Ben Hutchings

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=20151008175953.GH14409@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ben@decadent.org.uk \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.