linux-kernel - Re: [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy PIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140404151620.GB2161@redhat.com>
Date:	Fri, 4 Apr 2014 11:16:20 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"jasowang@...hat.com" <jasowang@...hat.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	Dave Young <dyoung@...hat.com>
Subject: Re: [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy
 PIC

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.

Thanks
Vivek
--
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/