From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
William Lee Irwin III <wli@holomorphy.com>,
Christoph Hellwig <hch@infradead.org>,
James Cleverdon <jamesclv@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: APIC version
Date: Mon, 13 Jan 2003 15:22:58 -0800 [thread overview]
Message-ID: <417390000.1042500178@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0301131752030.2102-100000@montezuma.mastecende.com>
>> The entries in acpi_version[] are indexed by the APIC id, not
>> smp_processor_id(). So you can overwrite acpi_version[] for a different
>> processor.
>
> Is it possible to use smp_processor_id instead to avoid wasting memory
> for the sparse APIC id case?
No, the array is set up in mpparse.c before we know the real processor
numbers.
M.
next prev parent reply other threads:[~2003-01-13 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 18:59 APIC version Nakajima, Jun
2003-01-13 19:26 ` Martin J. Bligh
2003-01-13 22:53 ` Zwane Mwaikambo
2003-01-13 23:22 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 4:51 Protasevich, Natalie
2003-01-14 3:55 Protasevich, Natalie
2003-01-14 4:43 ` Martin J. Bligh
2003-01-14 2:26 Nakajima, Jun
2003-01-14 0:09 Protasevich, Natalie
2003-01-13 23:49 Protasevich, Natalie
2003-01-13 23:54 ` Martin J. Bligh
2003-01-13 23:35 Nakajima, Jun
2003-01-13 23:14 Protasevich, Natalie
2003-01-13 20:21 Protasevich, Natalie
2003-01-13 20:12 Nakajima, Jun
2003-01-13 19:55 Protasevich, Natalie
2003-01-13 19:39 Protasevich, Natalie
2003-01-13 18:44 Protasevich, Natalie
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=417390000.1042500178@flay \
--to=mbligh@aracnet.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=hch@infradead.org \
--cc=jamesclv@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=wli@holomorphy.com \
--cc=zwane@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