linux-kernel - Re: [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <m18xabdhmv.fsf@ebiederm.dsl.xmission.com>
Date:	Fri, 22 Jun 2007 11:27:20 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	Pavel Machek <pavel@....cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	Neil Brown <neilb@...e.de>, Ingo Molnar <mingo@...e.hu>,
	asit.k.mallick@...el.com
Subject: Re: [PATCH] x86: Document the hotplug code is incompatible with x86 irq handling

"Rafael J. Wysocki" <rjw@...k.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/