From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <stable@vger.kernel.org>, "H. Peter Anvin" <hpa@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] x86/hyperv fix for v3.15-rc1
Date: Fri, 11 Apr 2014 10:39:27 -0700 [thread overview]
Message-ID: <201404111739.s3BHdRiW025864@terminus.zytor.com> (raw)
Hi Linus,
A single fix for HyperV -- we never NEED the legacy PIC on HyperV, and
in kexec/kdump scenarios we don't always know that we originally
booted EFI. The right answer is probably to augment the legacy PIC
initialization code to detect a not-present PIC, but that is way too
high risk for right now.
The following changes since commit ca3ba2a2f4a49a308e7d78c784d51b2332064f15:
x86, hyperv: Bypass the timer_irq_works() check (2014-03-27 11:02:45 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-hyperv-for-linus
for you to fetch changes up to 8df28b82ff0649dd293f0469b97792cfb9ed10ab:
x86, hyperv: When on Hyper-v use NULL legacy PIC (2014-04-03 22:00:13 -0700)
----------------------------------------------------------------
K. Y. Srinivasan (1):
x86, hyperv: When on Hyper-v use NULL legacy PIC
arch/x86/kernel/cpu/mshyperv.c | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
index 832d05a914ba..b7d82c7e1257 100644
--- a/arch/x86/kernel/cpu/mshyperv.c
+++ b/arch/x86/kernel/cpu/mshyperv.c
@@ -93,14 +93,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
next reply other threads:[~2014-04-11 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 17:39 H. Peter Anvin [this message]
2014-04-11 18:39 ` KY Srinivasan
2014-04-11 18:41 ` H. Peter Anvin
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=201404111739.s3BHdRiW025864@terminus.zytor.com \
--to=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®