From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.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 09:34:31 -0800 [thread overview]
Message-ID: <32680000.1040578470@titus> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1912E1B2@fmsmsx405.fm.intel.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) ?
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 ....
next prev parent reply other threads:[~2002-12-22 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 6:59 [PATCH][2.4] generic support for systems with more than 8 CPUs (1/2) Pallipadi, Venkatesh
2002-12-22 17:34 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 1:24 Pallipadi, Venkatesh
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=32680000.1040578470@titus \
--to=mbligh@aracnet.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=sunil.saxena@intel.com \
--cc=venkatesh.pallipadi@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