Re: [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy PIC
From: Vivek Goyal
Date: Fri Apr 04 2014 - 11:16:43 EST
On Fri, Apr 04, 2014 at 03:01:51PM +0000, KY Srinivasan wrote:
> The problem we were having is that the initial boot on the EFI firmware
> would succeed as the legacy PIC would be NULL legacy PIC, however
> in the kexeced kernel, the initial boot information is not available and so
> we would not set the legacy PIC to NULL legacy PIC.
I am curious to know what "initial boot information" is not available
in kexeced kernel and who is supposed to provide that.
Is it a bug or that's how it is supposed to work.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/