[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <516EBD1C.3030902@zytor.com>
Date: Wed, 17 Apr 2013 08:17:48 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Jan Beulich <JBeulich@...e.com>
CC: "Michael S. Tsirkin" <mst@...hat.com>,
"olaf@...fle.de" <olaf@...fle.de>, "bp@...en8.de" <bp@...en8.de>,
"apw@...onical.com" <apw@...onical.com>,
"x86@...nel.org" <x86@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] X86: Add a check to catch Xen emulation of Hyper-V
On 04/17/2013 07:09 AM, Jan Beulich wrote:
>
> Iirc it was/is XenServer which enable Hyper-V emulation for all HVM
> guests, which clearly is the wrong thing. I was personally also not
> really in agreement with the override in the kernel, but it was
> decided to do it that way at that point in time. As a consequence,
> I don't object this to be reverted.
>
I was not exactly happy with the idea either. I'm sorry if I mixed up
Xen and KVM.
Furthermore, as I recall, it only affected kernels where Xen was
compiled out, or something like that.
It would definitely be best to fix the HyperV driver to be more
robust... that may be important across HyperV releases, too.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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/
Powered by blists - more mailing lists