[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071213153222.GB4674@hmsreliant.think-freely.org>
Date: Thu, 13 Dec 2007 10:32:22 -0500
From: Neil Horman <nhorman@...driver.com>
To: Andi Kleen <andi@...stfloor.org>
Cc: Ben Woodard <woodard@...hat.com>, Neil Horman <nhorman@...hat.com>,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...e.de>, hbabu@...ibm.com,
"Eric W. Biederman" <ebiederm@...ssion.com>, hpa@...or.com,
tglx@...utronix.de, mingo@...hat.com,
Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH] kexec: force x86_64 arches to boot kdump kernels on
boot cpu
On Thu, Dec 13, 2007 at 04:16:29PM +0100, Andi Kleen wrote:
> On Thu, Dec 13, 2007 at 09:39:22AM -0500, Neil Horman wrote:
> >
> > Ok, new patch attached, taking into account Andi's request for a cleaner method
>
> Sorry for not noticing that earlier, but was there a specific reason this needs
> to be an early quirk at all? kexec can only happen after the standard quirks ran.
> I think it should be fine as a standard "late" quirk.
>
> -Andi
>
Early quirk seemed like the right thing to do to me. Starting from boot up,
this (mis)configuration by the bios can mean that come cpus just don't get
interrupts. I could imagine situations like serial console not working if the
serial port interrupt was routed to a cpu that used extended APIC id. I've
never actually observed it happening, but making sure that all cpus were
eligible to get interrupts early in the boot process made sense to me.
Neil
> _______________________________________________
> kexec mailing list
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
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