From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Natalie.Protasevich@unisys.com
Cc: akpm@osdl.org, ak@suse.de, len.brown@intel.com,
venkatesh.pallipadi@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] Do not enforce unique IO_APIC_ID for Xeon processors in EM64T mode (x86_64)
Date: Sat, 7 May 2005 19:00:39 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0505071900080.7817@montezuma.fsmlabs.com> (raw)
In-Reply-To: <20050507053435.6DA214749E@linux.site>
On Fri, 6 May 2005 Natalie.Protasevich@unisys.com wrote:
> diff -puN arch/x86_64/kernel/io_apic.c~no-ioapic-check-x86_64-2 arch/x86_64/kernel/io_apic.c
> --- linux-2.6.13-rc3-mm3/arch/x86_64/kernel/io_apic.c~no-ioapic-check-x86_64-2 2005-05-06 21:58:55.149700760 -0700
> +++ linux-2.6.13-rc3-mm3-root/arch/x86_64/kernel/io_apic.c 2005-05-06 22:00:41.361554104 -0700
> @@ -1867,12 +1867,16 @@ int __init io_apic_get_unique_id (int io
> int i = 0;
>
> /*
> + * xAPIC systems take advantage of APIC system bus architecture.
> + */
> +
> + if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL)
> + return apic_id;
> +
Shouldn't this be for both em64t and amd64?
next prev parent reply other threads:[~2005-05-08 0:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 5:34 Natalie.Protasevich
2005-05-08 1:00 ` Zwane Mwaikambo [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 2:22 Protasevich, Natalie
2005-05-11 16:21 Protasevich, Natalie
2005-05-11 19:22 ` Andi Kleen
2005-05-11 7:10 Protasevich, Natalie
2005-05-11 11:22 ` Andi Kleen
2005-05-08 17:28 Protasevich, Natalie
2005-05-08 23:53 ` Andi Kleen
2005-05-08 5:01 Protasevich, Natalie
2005-05-08 13:49 ` Andi Kleen
2005-05-09 19:15 ` James Cleverdon
2005-05-05 22:11 Natalie.Protasevich
2005-05-06 17:34 ` Len Brown
2005-05-06 17:57 ` Zwane Mwaikambo
2005-05-07 13:41 ` Andi Kleen
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=Pine.LNX.4.61.0505071900080.7817@montezuma.fsmlabs.com \
--to=zwane@arm.linux.org.uk \
--cc=Natalie.Protasevich@unisys.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@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®