From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RT 3.18] irq_work: Provide a soft-irq based queue
Date: Thu, 23 Apr 2015 09:19:26 +0200 [thread overview]
Message-ID: <1429773566.3419.42.camel@gmail.com> (raw)
In-Reply-To: <55389B67.3000703@siemens.com>
On Thu, 2015-04-23 at 09:12 +0200, Jan Kiszka wrote:
> On 2015-04-23 09:01, Mike Galbraith wrote:
> > On Thu, 2015-04-23 at 08:50 +0200, Jan Kiszka wrote:
> > > On 2015-04-23 08:11, Mike Galbraith wrote:
> > > > @@ -103,6 +98,9 @@ EXPORT_SYMBOL_GPL(irq_work_queue_on);
> > > > /* Enqueue the irq work @work on the current CPU */
> > > > bool irq_work_queue(struct irq_work *work)
> > > > {
> > > > + bool realtime = IS_ENABLED(CONFIG_PREEMPT_RT_FULL);
> > > > + bool raise = false;
> > > > +
> > > > /* Only queue if not already pending */
> > > > if (!irq_work_claim(work))
> > > > return false;
> > > > @@ -110,25 +108,22 @@ bool irq_work_queue(struct irq_work *wor
> > > > /* Queue the entry and raise the IPI if needed. */
> > > > preempt_disable();
> > > >
> > > > -#ifdef CONFIG_PREEMPT_RT_FULL
> > > > - if (work->flags & IRQ_WORK_HARD_IRQ) {
> > > > + if (realtime && (work->flags & IRQ_WORK_HARD_IRQ)) {
> > > > if (llist_add(&work->llnode,
> > > > this_cpu_ptr(&hirq_work_list)))
> > >
> > > This boils down to
> > >
> > > #ifdef CONFIG_X
> > > some_type x;
> > > #endif
> > > ...
> > >
> > > if (IS_ENABLED(CONFIG_X) && ...)
> > > use(x);
> > >
> > > And here we even have an indirection for IS_ENABLED via that
> > > local
> > > bool
> > > variable. Is that pattern OK for Linux? Does it compile in all
> > > supported
> > > optimization levels of all supported compilers?
> >
> > I hope it all goes away, that being what IS_ENABLED() is there for.
>
> Hope is good - but not enough here: it breaks the build under
> !CONFIG_X, even the case without the bool var.
>
> CC kernel/irq_work.o
> In file included from ../include/asm-generic/percpu.h:6:0,
> from ../arch/x86/include/asm/percpu.h:522,
> from ../arch/x86/include/asm/current.h:5,
> from ../arch/x86/include/asm/processor.h:15,
> from ../arch/x86/include/asm/irq_work.h:4,
> from ../include/linux/irq_work.h:47,
> from ../kernel/irq_work.c:11:
> ../kernel/irq_work.c: In function ‘irq_work_queue_on’:
> ../kernel/irq_work.c:85:17: error: ‘hirq_work_list’ undeclared
> (first use in this function)
> &per_cpu(hirq_work_list, cpu));
Aw poo, so that's just what I _thought_ it was for.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-23 7:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 14:06 [PATCH RT 3.18] ring-buffer: Mark irq_work as HARD_IRQ to prevent deadlocks Jan Kiszka
2015-04-16 14:12 ` Steven Rostedt
2015-04-16 14:26 ` Sebastian Andrzej Siewior
2015-04-16 14:28 ` Jan Kiszka
2015-04-16 14:57 ` Sebastian Andrzej Siewior
2015-04-16 15:31 ` Jan Kiszka
2015-04-16 15:10 ` Steven Rostedt
2015-04-16 15:29 ` Jan Kiszka
2015-04-16 15:33 ` Sebastian Andrzej Siewior
2015-04-16 16:28 ` [PATCH RT 3.18] irq_work: Provide a soft-irq based queue Jan Kiszka
2015-04-20 8:03 ` Mike Galbraith
2015-04-23 6:11 ` Mike Galbraith
2015-04-23 6:29 ` Jan Kiszka
2015-04-23 6:58 ` Mike Galbraith
2015-04-23 7:14 ` Jan Kiszka
2015-04-23 6:50 ` Jan Kiszka
2015-04-23 7:01 ` Mike Galbraith
2015-04-23 7:12 ` Jan Kiszka
2015-04-23 7:19 ` Mike Galbraith [this message]
2015-04-23 21:00 ` Steven Rostedt
2015-04-24 6:54 ` Mike Galbraith
2015-04-24 9:00 ` Jan Kiszka
2015-04-24 9:59 ` Mike Galbraith
2015-04-25 7:20 ` Mike Galbraith
2015-04-25 7:26 ` Jan Kiszka
2015-05-18 19:52 ` Sebastian Andrzej Siewior
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=1429773566.3419.42.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).