[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804212248.02986.jdelvare@suse.de>
Date: Mon, 21 Apr 2008 22:48:02 +0200
From: Jean Delvare <jdelvare@...e.de>
To: Andi Kleen <andi@...stfloor.org>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
linux-pci@...ey.karlin.mff.cuni.cz,
LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
Tejun Heo <htejun@...il.com>,
Tom Long Nguyen <tom.l.nguyen@...el.com>,
Randy Dunlap <rdunlap@...otime.net>,
Jeff Garzik <jgarzik@...ox.com>
Subject: Re: PCI MSI breaks when booting with nosmp
Hi Andi,
Le lundi 21 avril 2008, Andi Kleen a écrit :
> > In my case, booting with noapic works fine, so I don't think that the problem
> > is related to APIC being disabled.
>
> noapic is not the same as no ioapic. maxcpus=0 just disables the IO-APIC
> but not the local APIC.
>From init/main.c:
static int __init maxcpus(char *str)
{
get_option(&str, &setup_max_cpus);
if (setup_max_cpus == 0)
disable_ioapic_setup();
return 0;
}
early_param("maxcpus", maxcpus);
>From arch/x86/kernel/io_apic_32.c:
static int __init parse_noapic(char *arg)
{
/* disable IO-APIC */
disable_ioapic_setup();
return 0;
}
early_param("noapic", parse_noapic);
Both call disable_ioapic_setup(), so how can they not be the same?
--
Jean Delvare
Suse L3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists