From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Mark Hounschell <markh@compro.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH -rt] irqd starvation on SMP by a single process?
Date: Fri, 12 May 2006 10:10:56 +0200 [thread overview]
Message-ID: <20060512081056.GA25378@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.58.0605120337150.26721@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 12 May 2006, Ingo Molnar wrote:
>
> > ah. This actually uncovered a real bug. We were calling __do_softirq()
> > with interrupts enabled (and being preemptible) - which is certainly
> > bad.
>
> Hmm, I wonder if this is also affecting Mark's problem.
>
> But since I showed that if hardirqs_disabled and running PREEMPT not
> PREEMPT_RT, disable_irq can call schedule. This is done in
> drivers/net/3c59x.c. It has a watchdog timeout calling disable_irq,
> which calls synchronize_irq which might schedule:
>
> void synchronize_irq(unsigned int irq)
> {
> struct irq_desc *desc = irq_desc + irq;
>
> if (irq >= NR_IRQS)
> return;
>
> if (hardirq_preemption && !(desc->status & IRQ_NODELAY))
> wait_event(desc->wait_for_handler,
> !(desc->status & IRQ_INPROGRESS));
> else
> while (desc->status & IRQ_INPROGRESS)
> cpu_relax();
> }
>
> -- Steve
>
> >
> > this was hidden before because the smp_processor_id() debugging code
> > handles tasks bound to a single CPU as per-cpu-safe.
> >
> > could you check the (totally untested) patch below and see if that fixes
> > things for you? I've also added your affinity change.
> >
next prev parent reply other threads:[~2006-05-12 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 2:43 [RFC][PATCH -rt] irqd starvation on SMP by a single process? john stultz
2006-05-12 5:50 ` Ingo Molnar
2006-05-12 7:59 ` Steven Rostedt
2006-05-12 8:10 ` Ingo Molnar [this message]
2006-05-12 11:39 ` Mark Hounschell
2006-05-12 11:56 ` Ingo Molnar
2006-05-12 11:59 ` Mark Hounschell
2006-05-12 12:53 ` Mark Hounschell
2006-05-12 13:03 ` Steven Rostedt
2006-05-12 13:06 ` Mark Hounschell
2006-05-12 13:19 ` Mark Hounschell
2006-05-12 17:47 ` john stultz
2006-05-12 18:04 ` john stultz
2006-05-12 19:16 ` Mark Hounschell
2006-05-12 20:04 ` Mark Hounschell
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 4:22 Edward Killips
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=20060512081056.GA25378@elte.hu \
--to=mingo@elte.hu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox