From: Ingo Molnar <mingo@kernel.org>
To: Vinson Lee <vlee@twitter.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@redhat.com>,
Irina Tirdea <irina.tirdea@intel.com>,
Paul Mackerras <paulus@samba.org>,
Pekka Enberg <penberg@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH v3] perf tools: Fix LIBNUMA build with glibc 2.12 and older.
Date: Thu, 14 Mar 2013 08:34:18 +0100 [thread overview]
Message-ID: <20130314073418.GA10245@gmail.com> (raw)
In-Reply-To: <1363214064-4671-2-git-send-email-vlee@twitter.com>
* Vinson Lee <vlee@twitter.com> wrote:
> The tokens MADV_HUGEPAGE and MADV_NOHUGEPAGE are not available with
> glibc 2.12 and older. Define these tokens if they are not already
> defined.
>
> This patch fixes these build errors with older versions of glibc.
>
> CC bench/numa.o
> bench/numa.c: In function ???alloc_data???:
> bench/numa.c:334: error: ???MADV_HUGEPAGE??? undeclared (first use in this function)
> bench/numa.c:334: error: (Each undeclared identifier is reported only once
> bench/numa.c:334: error: for each function it appears in.)
> bench/numa.c:341: error: ???MADV_NOHUGEPAGE??? undeclared (first use in this function)
> make: *** [bench/numa.o] Error 1
>
> Signed-off-by: Vinson Lee <vlee@twitter.com>
> Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Irina Tirdea <irina.tirdea@intel.com>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Pekka Enberg <penberg@kernel.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> ---
> tools/perf/bench/bench.h | 24 ++++++++++++++++++++++++
> 1 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/bench/bench.h b/tools/perf/bench/bench.h
> index a5223e6..c132ee7 100644
> --- a/tools/perf/bench/bench.h
> +++ b/tools/perf/bench/bench.h
> @@ -1,6 +1,30 @@
> #ifndef BENCH_H
> #define BENCH_H
>
> +/*
> + * The madvise transparent hugepage constants were added in glibc
> + * 2.13. For compatibility with older versions of glibc, define these
> + * tokens if they are not already defined.
> + *
> + * PA-RISC uses different madvise values from other architectures and
> + * needs to be special-cased.
> + */
> +#ifdef __hppa__
> +# ifndef MADV_HUGEPAGE
> +# define MADV_HUGEPAGE 67
> +# endif
> +# ifndef MADV_NOHUGEPAGE
> +# define MADV_NOHUGEPAGE 68
> +# endif
> +#else
> +# ifndef MADV_HUGEPAGE
> +# define MADV_HUGEPAGE 14
> +# endif
> +# ifndef MADV_NOHUGEPAGE
> +# define MADV_NOHUGEPAGE 15
> +# endif
> +#endif
Thanks!
Acked-by: Ingo Molnar <mingo@kernel.org>
Arnaldo, will you be picking this up for perf/urgent, or should I?
Thanks,
Ingo
next prev parent reply other threads:[~2013-03-14 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 5:03 [PATCH] perf tools: Fix LIBNUMA build with glibc 2.12 and older Vinson Lee
2013-03-06 8:52 ` Ingo Molnar
2013-03-06 23:12 ` Vinson Lee
2013-03-08 2:42 ` [PATCH v2] " Vinson Lee
2013-03-08 2:42 ` Vinson Lee
2013-03-11 8:36 ` Ingo Molnar
2013-03-13 22:34 ` [PATCH v3] " Vinson Lee
2013-03-13 22:34 ` Vinson Lee
2013-03-14 7:34 ` Ingo Molnar [this message]
2013-03-18 11:01 ` [tip:perf/urgent] " tip-bot for Vinson Lee
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=20130314073418.GA10245@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=irina.tirdea@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
--cc=vlee@twitter.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.