From: ebiederm@xmission.com (Eric W. Biederman)
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>,
Ingo Molnar <mingo@elte.hu>,
asit.k.mallick@intel.com
Subject: Re: [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling
Date: Fri, 22 Jun 2007 11:27:20 -0600 [thread overview]
Message-ID: <m18xabdhmv.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200706130058.43227.rjw@sisk.pl> (Rafael J. Wysocki's message of "Wed, 13 Jun 2007 00:58:42 +0200")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
>
> OK, thanks.
>
> Eric, would you agree to follow this plan without making the entire CPU hotplug
> (on x86) depend on BROKEN?
Sorry for the delay, I missed this email. If we can actually move irq
migration into process context on x86. I would be happy to.
Currently I am dubious if this can be done reliably. But I think
the benefits of doing irq migration outside of the irq handler
are sufficient to give another go at making it work.
However this isn't just Intel's ioapics we have to worry about,
but Intel's were the worst so that is a reasonable starting point.
Eric
next prev parent reply other threads:[~2007-06-22 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 13:32 [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling Eric W. Biederman
2007-06-07 14:01 ` Pavel Machek
2007-06-12 18:19 ` Eric W. Biederman
2007-06-12 20:52 ` Rafael J. Wysocki
2007-06-12 21:56 ` Siddha, Suresh B
2007-06-12 22:16 ` Rafael J. Wysocki
2007-06-12 22:24 ` Siddha, Suresh B
2007-06-12 22:58 ` Rafael J. Wysocki
2007-06-22 17:27 ` Eric W. Biederman [this message]
[not found] <fa.tUMR7tAB+jMgtfyl/LJ7U9QMgBs@ifi.uio.no>
2007-05-31 14:34 ` Robert Hancock
2007-05-31 15:47 ` Eric W. Biederman
2007-05-31 20:12 ` Rafael J. Wysocki
2007-06-01 19:48 ` Eric W. Biederman
2007-06-01 20:06 ` Rafael J. Wysocki
2007-06-01 20:29 ` Eric W. Biederman
2007-06-01 20:44 ` Rafael J. Wysocki
2007-06-01 20:34 ` 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=m18xabdhmv.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=asit.k.mallick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=suresh.b.siddha@intel.com \
/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