public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Corey Ashford <cjashfor@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf_counter: do not create perf counter mlock sysctl when CONFIG_PERF_COUNTERS=n
Date: Fri, 22 May 2009 21:25:10 +0200	[thread overview]
Message-ID: <20090522192510.GB18651@elte.hu> (raw)
In-Reply-To: <1242985373.22654.225.camel@zakaz.uk.xensource.com>


* Ian Campbell <Ian.Campbell@citrix.com> wrote:

> Building tip from 82811bee3 without CONFIG_PERF_COUNTERS results in:
> 
>   CC      kernel/sysctl.o
> kernel/sysctl.c:928: error: 'sysctl_perf_counter_mlock' undeclared here (not in a function)
> 
> This is due to c5078f78b "perf_counter: provide an mlock threshold"
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 44ebd90..c2a4467 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -922,6 +922,7 @@ static struct ctl_table kern_table[] = {
>  		.child		= slow_work_sysctls,
>  	},
>  #endif
> +#ifdef CONFIG_PERF_COUNTERS
>  	{
>  		.ctl_name	= CTL_UNNUMBERED,
>  		.procname	= "perf_counter_mlock_kb",
> @@ -930,6 +931,7 @@ static struct ctl_table kern_table[] = {
>  		.mode		= 0644,
>  		.proc_handler	= &proc_dointvec,
>  	},
> +#endif
>  /*
>   * NOTE: do not add new entries to this table unless you have read
>   * Documentation/sysctl/ctl_unnumbered.txt

Hm, is this still needed? It doesnt apply here and i'm not seeing 
build failures.

Thanks,

	Ingo

  reply	other threads:[~2009-05-22 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22  9:42 [PATCH] perf_counter: do not create perf counter mlock sysctl when CONFIG_PERF_COUNTERS=n Ian Campbell
2009-05-22 19:25 ` Ingo Molnar [this message]
2009-05-24  8:25   ` Ian Campbell

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=20090522192510.GB18651@elte.hu \
    --to=mingo@elte.hu \
    --cc=Ian.Campbell@citrix.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cjashfor@linux.vnet.ibm.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