All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <pranith@gatech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kernel/rcu/rcutorture.c: use macro to define module parameter
Date: Wed, 16 Apr 2014 14:14:07 -0700	[thread overview]
Message-ID: <20140416211407.GA4496@linux.vnet.ibm.com> (raw)
In-Reply-To: <534EEC6B.8030500@gatech.edu>

On Wed, Apr 16, 2014 at 04:47:39PM -0400, Pranith Kumar wrote:
> use the defined macro for module parameter definition
> 
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>

This fails for me.  The problem is that the defined macro makes everything
static, and rcutorture_runnable is used in kernel/sysctl.c.  :-/

In theory, it would be possible to make torture_param() take "static"
as a parameter, but this adds more characters than it removes.

							Thanx, Paul

> ---
>  kernel/rcu/rcutorture.c |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
> index bd30bc6..1a0298c 100644
> --- a/kernel/rcu/rcutorture.c
> +++ b/kernel/rcu/rcutorture.c
> @@ -143,9 +143,8 @@ static struct list_head rcu_torture_removed;
>  #else
>  #define RCUTORTURE_RUNNABLE_INIT 0
>  #endif
> -int rcutorture_runnable = RCUTORTURE_RUNNABLE_INIT;
> -module_param(rcutorture_runnable, int, 0444);
> -MODULE_PARM_DESC(rcutorture_runnable, "Start rcutorture at boot");
> +torture_param(int, rcutorture_runnable, RCUTORTURE_RUNNABLE_INIT,
> +		"Start rcutorture at boot");
> 
>  #if defined(CONFIG_RCU_BOOST) && !defined(CONFIG_HOTPLUG_CPU)
>  #define rcu_can_boost() 1
> -- 
> 1.7.9.5
> 


  reply	other threads:[~2014-04-16 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 20:47 [PATCH 2/2] kernel/rcu/rcutorture.c: use macro to define module parameter Pranith Kumar
2014-04-16 21:14 ` Paul E. McKenney [this message]
2014-04-16 23:10   ` Pranith Kumar
2014-04-16 23:23     ` Paul E. McKenney

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=20140416211407.GA4496@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranith@gatech.edu \
    /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.