From: John Kacur <jkacur@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 2/2] Compile error with allmodconfig and CONFIG_PREEMPT_RT_FULL=y
Date: Mon, 14 Nov 2011 18:39:47 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1111141837100.6707@localhost6.localdomain6> (raw)
In-Reply-To: <20111114165148.GB2372@linux.vnet.ibm.com>
On Mon, 14 Nov 2011, Paul E. McKenney wrote:
> On Mon, Nov 14, 2011 at 02:44:43AM +0100, John Kacur wrote:
> > ERROR: "in_serving_softirq" [net/sched/cls_cgroup.ko] undefined!
> >
> > The above can be fixed by exporting in_serving_softirq
> >
> > Signed-off-by: John Kacur <jkacur@redhat.com>
> >
> > The above patch was originally for 3.0.9-rt25
> > But I also needed to cherry-pick it for 3.2-rc1-rt1
> > ---
> > kernel/softirq.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/kernel/softirq.c b/kernel/softirq.c
> > index 3db1d6f..5452432 100644
> > --- a/kernel/softirq.c
> > +++ b/kernel/softirq.c
> > @@ -447,6 +447,7 @@ int in_serving_softirq(void)
> > preempt_enable();
> > return res;
> > }
> > +EXPORT_SYMBOL(in_serving_softirq);
>
> Why not EXPORT_SYMBOL_GPL?
I have no problem with that, note however that the upstream file has
EXPORT_SYMBOL(irq_stat);
EXPORT_SYMBOL(local_bh_disable);
EXPORT_SYMBOL(_local_bh_enable);
EXPORT_SYMBOL(local_bh_enable);
EXPORT_SYMBOL(local_bh_enable_ip);
EXPORT_SYMBOL(__tasklet_schedule);
EXPORT_SYMBOL(__tasklet_hi_schedule);
EXPORT_SYMBOL(__tasklet_hi_schedule_first);
EXPORT_SYMBOL(tasklet_init);
EXPORT_SYMBOL(tasklet_kill);
EXPORT_SYMBOL(__send_remote_softirq);
EXPORT_SYMBOL(send_remote_softirq);
Any reason we can't change all of those to EXPORT_SYMBOL_GPL?
>
> With that change,
>
> Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> Not yet ready for mainline, because mainline does not yet have
> in_serving_softirq(). Therefore not queued for -rcu.
>
> Thanx, Paul
>
> > /*
> > * Called with bh and local interrupts disabled. For full RT cpu must
next prev parent reply other threads:[~2011-11-14 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:44 [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break John Kacur
2011-11-14 1:44 ` [PATCH 2/2] Compile error with allmodconfig and CONFIG_PREEMPT_RT_FULL=y John Kacur
2011-11-14 16:51 ` Paul E. McKenney
2011-11-14 17:39 ` John Kacur [this message]
2011-11-14 17:57 ` Paul E. McKenney
2011-11-14 20:51 ` Steven Rostedt
2011-11-14 21:07 ` John Kacur
2011-11-15 5:22 ` Mike Galbraith
2011-11-15 12:23 ` Steven Rostedt
2011-11-15 13:27 ` Mike Galbraith
2011-11-15 13:45 ` Mike Galbraith
2011-11-16 14:21 ` Mike Galbraith
2012-04-13 5:34 ` SUSE question wrt RT locking primitives Mike Galbraith
2012-04-13 12:58 ` Steven Rostedt
2012-04-13 14:53 ` Mike Galbraith
2012-04-13 15:47 ` Thomas Gleixner
2011-11-14 16:50 ` [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break Paul E. McKenney
2011-11-14 20:57 ` Steven Rostedt
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=alpine.LFD.2.00.1111141837100.6707@localhost6.localdomain6 \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox