mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Van Maren, Kevin" <kevin.vanmaren@unisys.com>,
	"William Lee Irwin III" <wli@holomorphy.com>,
	"Christoph Hellwig" <hch@infradead.org>,
	"James Cleverdon" <jamesclv@us.ibm.com>,
	"John Stultz" <johnstul@us.ibm.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Saxena, Sunil" <sunil.saxena@intel.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@unisys.com>
Subject: RE: [PATCH][2.4]  generic support for systems with more than 8 CPUs (1/2)
Date: Sun, 22 Dec 2002 17:24:15 -0800	[thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1912E1B6@fmsmsx405.fm.intel.com> (raw)



> From: Martin J. Bligh [mailto:mbligh@aracnet.com]
> > 1/2 : checking for xAPIC support in the system
> 
> OK, that looks pretty sane - one question:
> 
> > -		if ((clustered_apic_mode != CLUSTERED_APIC_XAPIC) &&
> > +		if (!xapic_support &&
> > +		    (clustered_apic_mode != CLUSTERED_APIC_XAPIC) &&
> 
> When does xapic_support differ from
> (clustered_apic_mode == CLUSTERED_APIC_XAPIC) ?
>

They are quite different. 
Infact CLUSTERED_APIC_XAPIC just means using physical APIC mode and is kind of a
misnomer as xAPIC doesn't necessariy mean physical APIC mode. 
xapic_support says whether xAPIC support is there or not. Then APICs 
can be configured either in physical or logical modes. I mainly need this as
with xAPIC support, we have:
- LAPIC and IOAPIC have there own name space, 
- max or 255 CPUS with 0xff as broadcast, as opposed to 0xf broadcast in case of no xAPIC

> Do you want to use a physical flat xapic mode for your stuff, or the
> same clustered physical mode as the Summit stuff? If the latter, then
> the new switch seems unnecessary ....

Now I am getting a bit confused here. I am using physical mode with no clustering
whatsoever. Thats what I felt even Summit was doing in 2.4.

Thanks,
-Venkatesh

             reply	other threads:[~2002-12-23  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23  1:24 Pallipadi, Venkatesh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-22  6:59 Pallipadi, Venkatesh
2002-12-22 17:34 ` Martin J. Bligh

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=C8C38546F90ABF408A5961FC01FDBF1912E1B6@fmsmsx405.fm.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=Natalie.Protasevich@unisys.com \
    --cc=asit.k.mallick@intel.com \
    --cc=hch@infradead.org \
    --cc=jamesclv@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.vanmaren@unisys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=sunil.saxena@intel.com \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®