From: ebiederm@xmission.com (Eric W. Biederman)
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Emmanuel Fust? <emmanuel.fuste@laposte.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Device hang when offlining a CPU due to IRQ misrouting
Date: Fri, 01 Jun 2007 21:48:25 -0600 [thread overview]
Message-ID: <m1k5unxbhy.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070602021906.GC13751@tree.beaverton.ibm.com> (Darrick J. Wong's message of "Fri, 1 Jun 2007 19:19:07 -0700")
"Darrick J. Wong" <djwong@us.ibm.com> writes:
> On Fri, Jun 01, 2007 at 06:18:32PM -0600, Eric W. Biederman wrote:
>
>> I doubt it. The practical problem is that cpu_down does not
>> and by design can not call the irq balancing part properly
>> and I haven't yet seen anything to suggest that we don't migrate
>> irq properly.
>>
>> So I'm guessing it was the decision part.
>
> I'm not using any IRQ balancer, afaik. As I recall, CONFIG_IRQBALANCE
> is i386-only, and I'm not running the userland irqbalance program
> either. Just messing around with /proc/irq/*/smp_affinity by hand. :)
This is just getting confusing.
Emmanuel Fust. Please play with /proc/irq/*/smp_affinity by hand and
confirm that you can move your irqs. This will confirm it is the decision
part.
Darrick. The cpu hotplug architecture makes it impossible to properly
call irq migration code that backs /proc/irq/*/smp_affinity. Therefore
the cpu hotplug interface to irq migration is broken by design. There
are some other bugs in the implementation of migrating irqs off of cpus
as well. I'm pretty certain that some combination of those problems is
biting you.
Eric
next prev parent reply other threads:[~2007-06-02 3:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 21:57 Emmanuel Fusté
2007-06-02 0:18 ` Eric W. Biederman
2007-06-02 2:19 ` Darrick J. Wong
2007-06-02 3:48 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-03 21:03 Emmanuel Fusté
2007-06-01 0:44 Darrick J. Wong
2007-06-01 19:39 ` Eric W. Biederman
2007-06-05 17:23 ` Siddha, Suresh B
2007-06-05 17:36 ` Darrick J. Wong
2007-06-05 18:13 ` Siddha, Suresh B
2007-06-05 18:33 ` Darrick J. Wong
2007-06-05 18:40 ` Siddha, Suresh B
2007-06-05 20:09 ` Darrick J. Wong
2007-06-05 21:14 ` Siddha, Suresh B
2007-06-05 23:57 ` Darrick J. Wong
2007-06-06 1:37 ` Siddha, Suresh B
2007-06-06 18:58 ` Darrick J. Wong
2007-06-06 19:35 ` Siddha, Suresh B
2007-06-06 23:16 ` Darrick J. Wong
2007-06-08 0:57 ` Siddha, Suresh B
2007-06-18 22:38 ` Darrick J. Wong
2007-06-18 23:54 ` Siddha, Suresh B
2007-06-19 0:51 ` Darrick J. Wong
2007-06-19 17:54 ` Eric W. Biederman
2007-06-19 18:00 ` Siddha, Suresh B
2007-06-19 18:55 ` Eric W. Biederman
2007-06-19 19:06 ` Darrick J. Wong
2007-06-19 19:59 ` Siddha, Suresh B
2007-06-19 20:49 ` Darrick J. Wong
2007-06-19 22:08 ` Siddha, Suresh B
2007-06-23 23:54 ` Rafael J. Wysocki
2007-06-23 23:58 ` Andrew Morton
2007-06-24 0:45 ` Eric W. Biederman
2007-06-24 0:51 ` Siddha, Suresh B
2007-06-24 12:50 ` Rafael J. Wysocki
2007-06-24 0:28 ` Siddha, Suresh B
2007-06-24 12:48 ` Rafael J. Wysocki
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=m1k5unxbhy.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=djwong@us.ibm.com \
--cc=emmanuel.fuste@laposte.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®