public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, ashok.raj@intel.com
Subject: Re: [patch] genapic: optimize & fix APIC mode setup
Date: Sat, 11 Nov 2006 16:27:57 +0100	[thread overview]
Message-ID: <20061111152757.GA2407@elte.hu> (raw)
In-Reply-To: <200611111620.24551.ak@suse.de>


* Andi Kleen <ak@suse.de> wrote:

> On Saturday 11 November 2006 16:14, Ingo Molnar wrote:
> > From: Ingo Molnar <mingo@elte.hu>
> > 
> > this patch fixes a couple of inconsistencies/problems i found while 
> > reviewing the x86_64 genapic code (when i was chasing mysterious eth0 
> > timeouts that would only trigger if CPU_HOTPLUG is enabled):
> > 
> >  - AMD systems defaulted to the slower flat-physical mode instead
> >    of the flat-logical mode. The only restriction on AMD systems
> >    is that they should not use clustered APIC mode.
> 
> This will open a race on CPU hotunplug unfortunately (common for multi 
> core suspend)

Note that i386 still defaults to logical flat mode, so whatever hotplug 
CPU races there are, they need to be fixed! Given how rare CPU hotplug 
systems are i have no problem with having these races in the kernel for 
a while until it's fixed.

Also, distro kernels enable CPU_HOTPLUG frequently. It is just ugly 
beyond recognition to switch the programming of the IRQ hardware on 
non-hotplug hardware just because a mostly-software feature (hotplug) is 
enabled ...

if hotplug breaks suspend then fix it, dont hack it around (on one 
platform) by slowing down the system [and causing other problems] ...

	Ingo

  reply	other threads:[~2006-11-11 15:29 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 [this message]
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
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=20061111152757.GA2407@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 \
    /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