From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: mikpe@csd.uu.se
Cc: zwane@linuxpower.ca, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5] Honour dont_enable_local_apic flag
Date: 01 Jun 2003 13:25:33 -0400 [thread overview]
Message-ID: <1054488333.6676.68.camel@pc> (raw)
In-Reply-To: <200306011123.h51BNIT7019716@harpo.it.uu.se>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Sun, 2003-06-01 at 07:23, mikpe@csd.uu.se wrote:
>
> (And if its local APIC is broken, cpu_has_apic should be cleared
> rather than setting the dont_enable flag. Post-boot code may
> access the local APIC if CONFIG_X86_LOCAL_APIC && cpu_has_apic.)
So would you prefer something more along the lines of:
--- arch/i386/kernel/setup.c.orig 2003-04-26 10:34:35.000000000 -0400
+++ arch/i386/kernel/setup.c 2003-06-01 13:11:47.000000000 -0400
@@ -845,6 +845,10 @@
*/
else if (!memcmp(from, "highmem=", 8))
highmem_pages = memparse(from+8, &from) >> PAGE_SHIFT;
+ else if (!memcmp(from, "nolapic", 7)) {
+ clear_bit(X86_FEATURE_APIC, &boot_cpu_data.x86_capability);
+ set_bit(X86_FEATURE_APIC, &disabled_x86_caps);
+ }
nextchar:
c = *(from++);
if (!c)
b.
--
Brian J. Murrell <brian@interlinx.bc.ca>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-01 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 11:23 [PATCH][2.5] Honour dont_enable_local_apic flag mikpe
2003-06-01 16:26 ` Brian J. Murrell
2003-06-01 17:25 ` Brian J. Murrell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 23:09 mikpe
2003-06-01 23:08 mikpe
2003-06-01 23:52 ` Brian J. Murrell
2003-06-02 4:50 ` Zwane Mwaikambo
2003-06-02 13:46 ` Brian J. Murrell
2003-06-02 14:56 ` mikpe
2003-06-02 16:20 ` Zwane Mwaikambo
2003-06-02 17:30 ` Brian J. Murrell
2003-06-01 3:30 Zwane Mwaikambo
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=1054488333.6676.68.camel@pc \
--to=brian@interlinx.bc.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=zwane@linuxpower.ca \
/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