public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ben Collins <bcollins@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/4] [APIC] Allow disabling of UP APIC/IO-APIC by default, with command line option to turn it on.
Date: Fri, 1 Dec 2006 09:39:00 +0100	[thread overview]
Message-ID: <20061201083900.GA26703@elte.hu> (raw)
In-Reply-To: <11648607732981-git-send-email-bcollins@ubuntu.com>


* Ben Collins <bcollins@ubuntu.com> wrote:

> +config X86_UP_APIC_DEFAULT_OFF
> +	bool "APIC support on uniprocessors defaults to off"
> +	depends on X86_UP_APIC
> +	default n

'n' is the default

>  /*
>   * Knob to control our willingness to enable the local APIC.
> + * -2=default-disable, -1=force-disable, 1=force-enable, 0=automatic
>   */
> -static int enable_local_apic __initdata = 0; /* -1=force-disable, +1=force-enable */
> +static int enable_local_apic __initdata = (X86_APIC_DEFAULT_OFF ? -2 : 0);

i guess this begs for enums?

>  		if (enable_local_apic <= 0) {
> -			printk("Local APIC disabled by BIOS -- "
> +			printk("Local APIC disabled by BIOS (or by default) -- "
>  			       "you can enable it with \"lapic\"\n");

that message should be more intelligent, depending on whether the value 
is 0, -1 or -2.

> +	/* If local apic is off due to config_x86_apic_off option, jump
> +	 * out here. */

nitpick: proper comment style for new code is:

	/*
	 * If local APIC is off due to config_x86_apic_off option, jump
	 * out here.
	 */

> +	if (enable_local_apic < -1) {
> +		printk(KERN_INFO "Local APIC disabled by default -- "
> +		       "use 'lapic' to enable it.\n");
> +		return -1;
> +	}

this should be enable_local_apic == -2. (and should use the enum)

> -int skip_ioapic_setup;
> +int skip_ioapic_setup = X86_APIC_DEFAULT_OFF;

nitpick: should be X86_IOAPIC_DEFAULT_VALUE - if the config option is 
not set then this 'OFF' value will mean 'on' ...

> +static int __init parse_apic(char *arg)
> +{
> +	/* enable IO-APIC */
> +	enable_ioapic_setup();
> +	return 0;
> +}
> +early_param("apic", parse_apic);

that should be "ioapic", not "apic". The CPU has a piece of silicon 
called the "local APIC" - enabled via the 'lapic' option, and disabled 
via noapic. What the option above wants to enable is the IO-APIC in the 
chipset (a different piece of silicon) and the interrupt routing 
capabilities attached to it. That piece is what is causing the installer 
problems.

looks good in principle, but needs these cleanups.

	Ingo

  reply	other threads:[~2006-12-01  8:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  4:26 Ubuntu patch sync for 2.6.20 Ben Collins
2006-11-30  4:26 ` Ben Collins
2006-11-30  4:26 ` Ben Collins
2006-11-30  4:26 ` [PATCH 1/4] [x86] Add command line option to enable/disable hyper-threading Ben Collins
2006-11-30 11:06   ` Alan
2006-11-30 18:08     ` Siddha, Suresh B
2006-12-01 13:29   ` Pavel Machek
2006-12-01 13:41     ` Ben Collins
2006-12-01 14:32       ` Arjan van de Ven
2006-12-01 15:09         ` Ben Collins
2006-12-01 16:10           ` Arjan van de Ven
2006-12-01 16:14             ` Ben Collins
2006-12-01 16:20             ` Linus Torvalds
2006-12-01 16:56               ` Alan
2006-12-01 17:13                 ` Mark Rustad
2006-11-30  4:26 ` [PATCH 2/4] [APIC] Allow disabling of UP APIC/IO-APIC by default, with command line option to turn it on Ben Collins
2006-12-01  8:39   ` Ingo Molnar [this message]
2006-12-01 20:56     ` Ben Collins
2006-12-02  8:56       ` Ingo Molnar
2006-11-30  4:26 ` [PATCH 3/4] [ATM] Add CPPFLAGS to byteorder.h check Ben Collins
2006-11-30  4:26 ` [PATCH 4/4] [HVCS] Select HVC_CONSOLE if HVCS is enabled Ben Collins
2006-11-30 12:32   ` Roman Zippel
2006-11-30 15:04     ` Ben Collins

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=20061201083900.GA26703@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=bcollins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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