From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, ashok.raj@intel.com
Subject: Re: [patch] genapic: optimize & fix APIC mode setup
Date: Mon, 13 Nov 2006 09:16:16 +0100 [thread overview]
Message-ID: <20061113081616.GA25604@elte.hu> (raw)
In-Reply-To: <200611130332.07569.ak@suse.de>
* Andi Kleen <ak@suse.de> wrote:
> Now if it causes device driver issues that's different of course. I
> wasn't aware of this before.
lets try my patch in -mm for a while.
Had i ever noticed this hack in the first place i would have NAK-ed it.
There is a fundamental design friction of a high-level feature like
HOTPLUG_CPU /requiring/ a fundamental change to the lowlevel IRQ
delivery mode! Such a requirement is broken and just serves to hide a
flaw in the hotplug design - which flaw would trigger on i386 /anyway/,
because i386 still uses logical delivery mode for APIC IPIs. Also, i'd
like to have a description of how to reproduce those CPU hotplug
problems, so that i can try to fix it.
Ingo
next prev parent reply other threads:[~2006-11-13 8:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 15:14 [patch] genapic: optimize & fix APIC mode setup Ingo Molnar
2006-11-11 15:20 ` Andi Kleen
2006-11-11 15:27 ` Ingo Molnar
2006-11-11 15:39 ` Ingo Molnar
2006-11-13 1:50 ` Siddha, Suresh B
2006-11-13 2:32 ` Andi Kleen
2006-11-13 8:16 ` Ingo Molnar [this message]
2006-11-13 9:08 ` Andi Kleen
2006-11-13 14:05 ` Ingo Molnar
2006-11-13 14:29 ` Andi Kleen
2006-11-13 15:04 ` Ingo Molnar
2006-11-13 16:10 ` Andi Kleen
2006-11-13 16:32 ` Ingo Molnar
2006-11-13 18:03 ` Siddha, Suresh B
2006-11-13 18:42 ` Ingo Molnar
2006-11-13 18:30 ` Siddha, Suresh B
2006-11-13 19:04 ` Ingo Molnar
2006-11-13 18:58 ` Siddha, Suresh B
2006-11-13 19:31 ` Ashok Raj
2006-11-13 19:08 ` Ingo Molnar
2006-11-13 14:14 ` Ingo Molnar
2006-11-13 8:43 ` Ingo Molnar
2006-11-13 17:34 ` Siddha, Suresh B
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=20061113081616.GA25604@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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