public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Andi Kleen <ak@suse.de>, 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:34:47 -0800	[thread overview]
Message-ID: <20061113093447.B17720@unix-os.sc.intel.com> (raw)
In-Reply-To: <20061113084315.GB25604@elte.hu>; from mingo@elte.hu on Mon, Nov 13, 2006 at 09:43:16AM +0100

On Mon, Nov 13, 2006 at 09:43:16AM +0100, Ingo Molnar wrote:
> 
> * Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:
> 
> > There is an issue of using clustered mode along with cpu hotplug. More 
> > details are at the below link.
> > 
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=113261865814107&w=2
> 
> ok, to make sure i understand this right: it is not safe to switch any 
> local APIC in the system into clustered APIC mode on the E850x chipset 
> /at all/, because if one of the CPUs gets an INIT/startup IPI message 
> its local APIC will default to logical flat mode and might confuse the 
> chipset?

"at all" is not quite correct. We are fine as long as all the cpus are up
in clustered APIC mode before the IO-APIC RTE's are programmed.

Once the IO-APIC subsystem is up and running and later if the cpu comes online
then we have a window between the INIT/startup IPI message and the place
where we program the DFR and LDR, with in which the IO-APIC will interpret
the logical mode in RTE as 'logical flat' and will probably result in missing
the interrupt.

thanks,
suresh
> 
> on large systems that have their APIC IDs set up to group CPUs amongst 
> different clusters and hence triggered cluster mode, the chipset does 
> not get confused by this, correct?
> 
> 	Ingo

      reply	other threads:[~2006-11-13 17:57 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
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 [this message]

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=20061113093447.B17720@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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