public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5] Honour dont_enable_local_apic flag
Date: 02 Jun 2003 09:46:18 -0400	[thread overview]
Message-ID: <1054561578.22451.19.camel@pc> (raw)
In-Reply-To: <Pine.LNX.4.50.0306011950080.31534-100000@montezuma.mastecende.com>

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

On Mon, 2003-06-02 at 00:50, Zwane Mwaikambo wrote:
> I agree with doing the clear apic capability flag,

Indeed.  I sure does seem to be the right way to go.

>  Brian how does this 
> fare? This patch alone should fix it.

It looks good and will try it out.  But before I do, should not:

	set_bit(X86_FEATURE_APIC, &disabled_x86_caps);

also be done?

> 
> Index: linux-2.5/arch/i386/kernel/apic.c
> ===================================================================
> RCS file: /home/cvs/linux-2.5/arch/i386/kernel/apic.c,v
> retrieving revision 1.54
> diff -u -p -B -r1.54 apic.c
> --- linux-2.5/arch/i386/kernel/apic.c	31 May 2003 19:01:05 -0000	1.54
> +++ linux-2.5/arch/i386/kernel/apic.c	2 Jun 2003 03:50:31 -0000
> @@ -609,7 +609,7 @@ static int __init detect_init_APIC (void
>  
>  	/* Disabled by DMI scan or kernel option? */
>  	if (dont_enable_local_apic)
> -		return -1;
> +		goto no_apic;
>  
>  	/* Workaround for us being called before identify_cpu(). */
>  	get_cpu_vendor(&boot_cpu_data);
> @@ -665,6 +665,7 @@ static int __init detect_init_APIC (void
>  	return 0;
>  
>  no_apic:
> +	clear_bit(X86_FEATURE_APIC, boot_cpu_data.x86_capability);
>  	printk("No local APIC present or hardware disabled\n");
>  	return -1;
>  }

b.

-- 
Brian J. Murrell <brian@interlinx.bc.ca>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-02 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-01 23:08 [PATCH][2.5] Honour dont_enable_local_apic flag mikpe
2003-06-01 23:52 ` Brian J. Murrell
2003-06-02  4:50   ` Zwane Mwaikambo
2003-06-02 13:46     ` Brian J. Murrell [this message]
2003-06-02 14:56     ` mikpe
2003-06-02 16:20       ` Zwane Mwaikambo
2003-06-02 17:30         ` Brian J. Murrell
  -- strict thread matches above, loose matches on Subject: below --
2003-06-01 23:09 mikpe
2003-06-01 11:23 mikpe
2003-06-01 16:26 ` Brian J. Murrell
2003-06-01 17:25 ` 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=1054561578.22451.19.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