From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Christoph Hellwig" <hch@infradead.org>
Cc: "Martin Bligh" <mbligh@us.ibm.com>,
"John Stultz" <johnstul@us.ibm.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>, <jamesclv@us.ibm.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>
Subject: RE: [PATCH][2.4] generic cluster APIC support for systems with more than 8 CPUs
Date: Wed, 18 Dec 2002 17:05:01 -0800 [thread overview]
Message-ID: <C8C38546F90ABF408A5961FC01FDBF1912E190@fmsmsx405.fm.intel.com> (raw)
I have started working on a similar patch for 2.5. Other thing in my todo list is to
split this patch up into chunks.
Other comments inlined below.
> From: Christoph Hellwig [mailto:hch@infradead.org]
> On Wed, Dec 18, 2002 at 02:36:20PM -0800, Pallipadi, Venkatesh wrote:
> > xAPIC support can actually be determined from the LAPIC version.
>
> Are you sure? IIRC some of the early summit boxens didn't report the
> right versions..
> does this really not break anything in the fragile summit setups?
I am not really sure about the local APIC versions in summit. What I remember seeing on
lkml was summit has older IOAPIC version. Can someone clarify this?
> Okay, this was wrong before, but any chance you could use proper
> style here (i.e. if ()
> Again.
oops.. I somehow missed these 'if' coding style stuff. changing it immediately.
> > + define_bool CONFIG_X86_CLUSTERED_APIC y
> Do we really need CONFIG_X86_APIC_CLUSTER _and_ CONFIG_X86_CLUSTERED_APIC?
I will also eliminate CONFIG_X86_APIC_CLUSTER and use CONFIG_X86_CLUSTERED_APIC directly.
>
> - if (clustered_apic_mode == CLUSTERED_APIC_NUMAQ) {
> + if (clustered_apic_mode &&
> + (configured_platform_type ==
> CONFIGURED_PLATFORM_NUMA) ) {
>
> Doesn;t configured_platform_type == CONFIGURED_PLATFORM_NUMA imply
> clustered_apic_mode? and it should be at least
> CONFIGURED_PLATFORM_NUMAQ,
> btw. Probably better something short like SUBARCH_NUMAQ..
Yes, right now CONFIGURED_PLATFORM_NUMA implies clustered_apic_mode, and one of the
checks in the above 'if' is redundant. Will do a search and replace of NUMA by NUMAQ.
Thanks,
Venkatesh
next reply other threads:[~2002-12-19 0:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 1:05 Pallipadi, Venkatesh [this message]
2002-12-19 1:32 ` James Cleverdon
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 3:19 Kamble, Nitin A
2003-01-07 22:42 Andrew Theurer
2003-01-11 4:28 ` James Cleverdon
2002-12-21 3:27 Nakajima, Jun
2002-12-21 4:43 ` Martin J. Bligh
2002-12-19 2:45 Pallipadi, Venkatesh
2002-12-19 4:14 ` James Cleverdon
2002-12-19 2:35 Pallipadi, Venkatesh
2002-12-19 3:10 ` Martin J. Bligh
2002-12-18 22:36 Pallipadi, Venkatesh
2002-12-18 23:26 ` Christoph Hellwig
2002-12-18 23:41 ` William Lee Irwin III
2002-12-18 23:59 ` Martin J. Bligh
2002-12-19 0:24 ` Martin J. Bligh
2002-12-20 2:04 ` James Cleverdon
2002-12-20 8:00 ` Christoph Hellwig
2002-12-20 11:24 ` William Lee Irwin III
2002-12-20 11:29 ` William Lee Irwin III
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=C8C38546F90ABF408A5961FC01FDBF1912E190@fmsmsx405.fm.intel.com \
--to=venkatesh.pallipadi@intel.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=linux-kernel@vger.kernel.org \
--cc=mbligh@us.ibm.com \
--cc=sunil.saxena@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
all inboxes | Powered by JetHome®