From: Vivek Goyal <vgoyal@redhat.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy PIC
Date: Fri, 4 Apr 2014 11:16:20 -0400 [thread overview]
Message-ID: <20140404151620.GB2161@redhat.com> (raw)
In-Reply-To: <fb8d196a0c01479bae9c3669d8ea8be5@BY2PR03MB299.namprd03.prod.outlook.com>
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
next prev parent reply other threads:[~2014-04-04 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 1:16 [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy PIC K. Y. Srinivasan
2014-04-04 5:15 ` [tip:x86/hyperv] x86, hyperv: " tip-bot for K. Y. Srinivasan
2014-04-04 14:12 ` [PATCH 1/1] x86/platform/hyperv: " Vivek Goyal
2014-04-04 15:01 ` KY Srinivasan
2014-04-04 15:16 ` Vivek Goyal [this message]
2014-04-04 20:09 ` KY Srinivasan
2014-04-04 20:32 ` Vivek Goyal
2014-04-04 22:53 ` KY Srinivasan
2014-04-07 7:06 ` Olaf Hering
2014-04-07 15:40 ` KY Srinivasan
2014-04-07 15:40 ` KY Srinivasan
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=20140404151620.GB2161@redhat.com \
--to=vgoyal@redhat.com \
--cc=apw@canonical.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.