From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/5] Fix mismatched variable in rcutree_trace.c
Date: Tue, 7 Jun 2011 16:13:06 -0700 [thread overview]
Message-ID: <20110607231306.GH2286@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1106080040320.11814@ionos>
On Wed, Jun 08, 2011 at 12:42:17AM +0200, Thomas Gleixner wrote:
>
>
> On Tue, 7 Jun 2011, Andi Kleen wrote:
>
> > From: Andi Kleen <ak@linux.intel.com>
> >
> > rcutree.c defines rcu_cpu_kthread_cpu as int, not unsigned int,
> > so the extern has to follow that.
> >
> > Cc: paulmck@linux.vnet.ibm.com
> > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> > ---
> > kernel/rcutree_trace.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/kernel/rcutree_trace.c b/kernel/rcutree_trace.c
> > index 9678cc3..91c56e5 100644
> > --- a/kernel/rcutree_trace.c
> > +++ b/kernel/rcutree_trace.c
> > @@ -47,7 +47,7 @@
> > #include "rcutree.h"
> >
> > DECLARE_PER_CPU(unsigned int, rcu_cpu_kthread_status);
> > -DECLARE_PER_CPU(unsigned int, rcu_cpu_kthread_cpu);
> > +DECLARE_PER_CPU(int, rcu_cpu_kthread_cpu);
>
> Can we rather fix the DEFINE to use unsigned int. Signed cpu numbers
> are pointless in that context, right ?
Hmmm... Some arches have signed CPU numbers while others have unsigned
CPU numbers. I do use "-1" to mean "no CPU" in some cases (for example,
in rcu_node_kthread_setaffinity()), so I guess for consistency I should
be using "int" everywhere.
So, any plans for systems with 2,147,483,648 CPUs? ;-)
Thanx, Paul
> > DECLARE_PER_CPU(unsigned int, rcu_cpu_kthread_loops);
> > DECLARE_PER_CPU(char, rcu_cpu_has_work);
> >
> > --
> > 1.7.4.4
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
next prev parent reply other threads:[~2011-06-07 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 22:26 [PATCH 1/5] SH: drop const from io port variiable Andi Kleen
2011-06-07 22:26 ` [PATCH 2/5] Fix mismatched variable in rcutree_trace.c Andi Kleen
2011-06-07 22:42 ` Thomas Gleixner
2011-06-07 23:13 ` Paul E. McKenney [this message]
2011-06-07 23:43 ` Andi Kleen
2011-06-08 0:13 ` Paul E. McKenney
2011-06-07 22:26 ` [PATCH 3/5] IRDA: Fix global type conflicts in net/irda/irsysctl.c Andi Kleen
2011-06-09 7:29 ` David Miller
2011-06-07 22:26 ` [PATCH 4/5] ixgbe: Fix incorrect declaration of ixgbevf_mbx_ops Andi Kleen
2011-06-07 22:56 ` Rose, Gregory V
2011-06-08 19:04 ` Jeff Kirsher
2011-06-07 22:26 ` [PATCH 5/5] Avoid section type conflict in dma/ioat/dma_v3.c Andi Kleen
2011-06-07 23:07 ` Dan Williams
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=20110607231306.GH2286@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.