From: Stephen Hemminger <stephen@networkplumber.org>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "LKML" <linux-kernel@vger.kernel.org>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Simon Xiao" <sixiao@microsoft.com>,
"KY Srinivasan" <kys@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Denys Vlasenko" <dvlasenk@redhat.com>,
"Brian Gerst" <brgerst@gmail.com>,
"Borislav Petkov" <bp@alien8.de>,
"Andy Lutomirski" <luto@kernel.org>
Subject: Re: [PATCH] x86/idt: Unbreak MS HyperV hypercall vector install
Date: Fri, 8 Sep 2017 09:57:26 -0700 [thread overview]
Message-ID: <20170908095726.35b82463@xeon-e3> (raw)
In-Reply-To: <alpine.DEB.2.20.1709081013530.1888@nanos>
On Fri, 8 Sep 2017 01:19:52 -0700
"Thomas Gleixner" <tglx@linutronix.de> wrote:
> The rework of the IDT setup changed the way how unused system gates are
> accounted. At the end of the gate initialization all unused gates in the
> system vector area are set to the spurios handler and marked as used for
> consistency reasons.
>
> Marking them as used breaks MS HyperV because it installs its hypercall
> vector after that point and the installation is guarded by the bit in the
> used_vectors map. So the hyperv vector stays directed to the spurious
> interrupt handler.
>
> Leave them marked as unused again and unbreak HyperV that way.
>
> Fixes: dc20b2d52653 ("x86/idt: Move interrupt gate initialization to IDT
> code")
> Reported-by: Stephen Hemminger <sthemmin@microsoft.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
This fixes it, thanks.
Tested-by: Stephen Hemminger <sthemmin@microsoft.com>
next prev parent reply other threads:[~2017-09-08 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 8:19 [PATCH] x86/idt: Unbreak MS HyperV hypercall vector install Thomas Gleixner
2017-09-08 16:12 ` Haiyang Zhang
2017-09-08 16:57 ` Stephen Hemminger [this message]
2017-09-08 17:09 ` Thomas Gleixner
2017-09-08 17:15 ` 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=20170908095726.35b82463@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sixiao@microsoft.com \
--cc=sthemmin@microsoft.com \
--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 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.