From: Vivek Goyal <vgoyal@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, olaf@aepfle.de,
apw@canonical.com, jasowang@redhat.com, hpa@zytor.com,
"K. Y. Srinivasan" <kys@microsoft.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/platform/hyperv: When on Hyper-v use NULL legacy PIC
Date: Fri, 4 Apr 2014 10:12:18 -0400 [thread overview]
Message-ID: <20140404141218.GA2161@redhat.com> (raw)
In-Reply-To: <1396574193-12043-1-git-send-email-kys@microsoft.com>
On Thu, Apr 03, 2014 at 06:16:33PM -0700, K. Y. Srinivasan wrote:
> Use the NULL legacy PIC when on Hyper-V. With this change we can support kexec
> even when booting on EFI firmware. This patch has been tested on both EFI as
> well as non-EFI firmware stacks on Hyper-V.
>
> This patch is required to support kexec on EFI firmware on Hyper-V. Please
> apply.
Can you give some more details about what's the problem we run into with
kexec on EFI on hyper-V.
Now EFI should be enabled in kexeced kernel. That means
efi_enabled(EFI_BOOT) should be true and that means you would set
legacy_pic to null anyway.
So with this patch, what changed w.r.t kexec on EFI.
Thansk
Vivek
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Cc: <stable@vger.kernel.org> [3.13+]
> ---
> arch/x86/kernel/cpu/mshyperv.c | 10 ++--------
> 1 files changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
> index 76f98fe..47359f7 100644
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -133,14 +133,8 @@ static void __init ms_hyperv_init_platform(void)
> printk(KERN_INFO "HyperV: LAPIC Timer Frequency: %#x\n",
> lapic_timer_frequency);
>
> - /*
> - * On Hyper-V, when we are booting off an EFI firmware stack,
> - * we do not have many legacy devices including PIC, PIT etc.
> - */
> - if (efi_enabled(EFI_BOOT)) {
> - printk(KERN_INFO "HyperV: Using null_legacy_pic\n");
> - legacy_pic = &null_legacy_pic;
> - }
> + printk(KERN_INFO "HyperV: Using null_legacy_pic\n");
> + legacy_pic = &null_legacy_pic;
> }
> #endif
>
> --
> 1.7.4.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2014-04-04 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 1:16 K. Y. Srinivasan
2014-04-04 5:15 ` [tip:x86/hyperv] x86, hyperv: " tip-bot for K. Y. Srinivasan
2014-04-04 14:12 ` Vivek Goyal [this message]
2014-04-04 15:01 ` [PATCH 1/1] x86/platform/hyperv: " KY Srinivasan
2014-04-04 15:16 ` Vivek Goyal
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
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=20140404141218.GA2161@redhat.com \
--to=vgoyal@redhat.com \
--cc=apw@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome