On Fri, Jan 25, Jan Beulich wrote:
> >>> On 24.01.13 at 19:59, Olaf Hering wrote:
> > On Thu, Jan 24, KY Srinivasan wrote:
> >
> >
> >> > Question is - considering you stated that this is supported
> >> > starting in Win8, doesn't Hyper-V itself announce that
> >> > capability in some explicit
On Fri, Jan 25, Jan Beulich wrote:
On 24.01.13 at 19:59, Olaf Hering o...@aepfle.de wrote:
On Thu, Jan 24, KY Srinivasan wrote:
Question is - considering you stated that this is supported
starting in Win8, doesn't Hyper-V itself announce that
capability in some explicit way?
>>> On 24.01.13 at 19:59, Olaf Hering wrote:
> On Thu, Jan 24, KY Srinivasan wrote:
>
>
>> > Question is - considering you stated that this is supported
>> > starting in Win8, doesn't Hyper-V itself announce that
>> > capability in some explicit way?
>>
>> Thanks Jan. Unfortunately I don't
>>> On 24.01.13 at 20:03, KY Srinivasan wrote:
> I was under the impression that only Dom0 Xen would emulate Hyper-V.
How that? It's the hypervisor that does the emulation, and obviously
not for Dom0, but for (HVM) DomU-s.
Jan
--
To unsubscribe from this list: send the line "unsubscribe
>>> On 24.01.13 at 20:10, "H. Peter Anvin" wrote:
> I also have to point out the obvious problem with Xen masquerading as HyperV
> without implementing the same feature set...
I can't resist to state that this is what feature bits have been
introduced for in CPUID leaves. As long as Xen's shim
>>> On 24.01.13 at 20:04, "H. Peter Anvin" wrote:
> Can't you discover Xen emulation by looking for Xen first? Or does Xen go
> "stealth"?
That's already being done - the ordering currently is Xen, VMWare,
Hyper-V, KVM. I.e. there's only a problem when !CONFIG_XEN_PVHVM.
Jan
--
To
And there is no evidence of Xen in CPUID?
Olaf Hering wrote:
>On Thu, Jan 24, H. Peter Anvin wrote:
>
>> Can't you discover Xen emulation by looking for Xen first? Or does
>Xen go "stealth"?
>
>The current code looks at cpuid to decide what the host type is. One
>thing to detect a Xen host is
On Thu, Jan 24, H. Peter Anvin wrote:
> Can't you discover Xen emulation by looking for Xen first? Or does Xen go
> "stealth"?
The current code looks at cpuid to decide what the host type is. One
thing to detect a Xen host is to look for the DIM strings, which still
have "Xen HVM DomU" or
l...@suse.com]
>> >> Sent: Thursday, January 24, 2013 3:48 AM
>> >> To: KY Srinivasan
>> >> Cc: o...@aepfle.de; b...@alien8.de; a...@canonical.com;
>x...@kernel.org;
>> >> t...@linutronix.de; de...@linuxdriverproject.org;
>> > gre...@linuxfound
Can't you discover Xen emulation by looking for Xen first? Or does Xen go
"stealth"?
Olaf Hering wrote:
>On Thu, Jan 24, KY Srinivasan wrote:
>
>
>> > Question is - considering you stated that this is supported
>> > starting in Win8, doesn't Hyper-V itself announce that
>> > capability in
ation.org;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
> Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
> special hypervisor interrupts
>
> On Thu, Jan 24, KY Srinivasan wrote:
>
>
> > > Question is - considering
On Thu, Jan 24, KY Srinivasan wrote:
> > Question is - considering you stated that this is supported
> > starting in Win8, doesn't Hyper-V itself announce that
> > capability in some explicit way?
>
> Thanks Jan. Unfortunately I don't think tis interrupt delivery model
> is specified via a
inuxfoundation.org;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
> Subject: RE: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
> special hypervisor interrupts
>
> >>> On 24.01.13 at 17:07, KY Srinivasan wrote:
>
> >
>
nical.com;
> jasow...@redhat.com; t...@linutronix.de; h...@zytor.com; jbeul...@suse.com
> Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
> special hypervisor interrupts
>
> On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
> > diff --
On 01/24/2013 11:35 AM, Borislav Petkov wrote:
> On Thu, Jan 24, 2013 at 06:11:32AM -0600, H. Peter Anvin wrote:
>> Sounds great in theory at least, as long as it doesn't mean pushing a
>> bunch of #ifdefs into other code.
>
> Just one set in hypervisor.h but this is the RightWay™ we do it in the
On Thu, Jan 24, 2013 at 06:11:32AM -0600, H. Peter Anvin wrote:
> Sounds great in theory at least, as long as it doesn't mean pushing a
> bunch of #ifdefs into other code.
Just one set in hypervisor.h but this is the RightWay™ we do it in the
kernel :-).
Anyway, it turned out to be easier than I
x...@kernel.org;
>> t...@linutronix.de; de...@linuxdriverproject.org;
> gre...@linuxfoundation.org;
>> jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
>> Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
>> special hypervisor
inuxfoundation.org;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
> Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
> special hypervisor interrupts
>
> >>> On 24.01.13 at 02:17, "K. Y. Srinivasan" wrote:
> > @@ -69,6
Sounds great in theory at least, as long as it doesn't mean pushing a bunch of
#ifdefs into other code.
Borislav Petkov wrote:
>On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
>> diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
>> index 1975122..803ca69
On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
> diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
> index 1975122..803ca69 100644
> --- a/arch/x86/kernel/entry_64.S
> +++ b/arch/x86/kernel/entry_64.S
> @@ -1446,11 +1446,16 @@ ENTRY(xen_failsafe_callback)
>
>>> On 24.01.13 at 02:17, "K. Y. Srinivasan" wrote:
> @@ -69,6 +74,11 @@ static void __init ms_hyperv_init_platform(void)
> ms_hyperv.features, ms_hyperv.hints);
>
> clocksource_register_hz(_cs, NSEC_PER_SEC/100);
> +
> + /*
> + * Setup the IDT for hypervisor
Sounds great in theory at least, as long as it doesn't mean pushing a bunch of
#ifdefs into other code.
Borislav Petkov b...@alien8.de wrote:
On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
index
...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On 24.01.13 at 02:17, K. Y. Srinivasan k...@microsoft.com wrote:
@@ -69,6 +74,11 @@ static void __init ms_hyperv_init_platform(void
...@linuxdriverproject.org;
gre...@linuxfoundation.org;
jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On 24.01.13 at 02:17, K. Y. Srinivasan k...@microsoft.com wrote
On Thu, Jan 24, 2013 at 06:11:32AM -0600, H. Peter Anvin wrote:
Sounds great in theory at least, as long as it doesn't mean pushing a
bunch of #ifdefs into other code.
Just one set in hypervisor.h but this is the RightWay™ we do it in the
kernel :-).
Anyway, it turned out to be easier than I
On 01/24/2013 11:35 AM, Borislav Petkov wrote:
On Thu, Jan 24, 2013 at 06:11:32AM -0600, H. Peter Anvin wrote:
Sounds great in theory at least, as long as it doesn't mean pushing a
bunch of #ifdefs into other code.
Just one set in hypervisor.h but this is the RightWay™ we do it in the
...@redhat.com; t...@linutronix.de; h...@zytor.com; jbeul...@suse.com
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel
...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
Subject: RE: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On 24.01.13 at 17:07, KY Srinivasan k...@microsoft.com wrote:
-Original Message-
From: Jan Beulich [mailto:jbeul
On Thu, Jan 24, KY Srinivasan wrote:
Question is - considering you stated that this is supported
starting in Win8, doesn't Hyper-V itself announce that
capability in some explicit way?
Thanks Jan. Unfortunately I don't think tis interrupt delivery model
is specified via a feature bit
...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus interrupts as
special hypervisor interrupts
On Thu, Jan 24, KY Srinivasan wrote:
Question is - considering you stated that this is supported
starting in Win8, doesn't Hyper-V
Can't you discover Xen emulation by looking for Xen first? Or does Xen go
stealth?
Olaf Hering o...@aepfle.de wrote:
On Thu, Jan 24, KY Srinivasan wrote:
Question is - considering you stated that this is supported
starting in Win8, doesn't Hyper-V itself announce that
capability in
...@kernel.org;
t...@linutronix.de; de...@linuxdriverproject.org;
gre...@linuxfoundation.org;
jasow...@redhat.com; linux-kernel@vger.kernel.org; h...@zytor.com
Subject: Re: [PATCH RESEND 1/1] X86: Handle Hyper-V vmbus
interrupts as
special hypervisor interrupts
On 24.01.13 at 02:17, K. Y
On Thu, Jan 24, H. Peter Anvin wrote:
Can't you discover Xen emulation by looking for Xen first? Or does Xen go
stealth?
The current code looks at cpuid to decide what the host type is. One
thing to detect a Xen host is to look for the DIM strings, which still
have Xen HVM DomU or similar.
And there is no evidence of Xen in CPUID?
Olaf Hering o...@aepfle.de wrote:
On Thu, Jan 24, H. Peter Anvin wrote:
Can't you discover Xen emulation by looking for Xen first? Or does
Xen go stealth?
The current code looks at cpuid to decide what the host type is. One
thing to detect a Xen host
On 24.01.13 at 20:04, H. Peter Anvin h...@zytor.com wrote:
Can't you discover Xen emulation by looking for Xen first? Or does Xen go
stealth?
That's already being done - the ordering currently is Xen, VMWare,
Hyper-V, KVM. I.e. there's only a problem when !CONFIG_XEN_PVHVM.
Jan
--
To
On 24.01.13 at 20:10, H. Peter Anvin h...@zytor.com wrote:
I also have to point out the obvious problem with Xen masquerading as HyperV
without implementing the same feature set...
I can't resist to state that this is what feature bits have been
introduced for in CPUID leaves. As long as
On 24.01.13 at 20:03, KY Srinivasan k...@microsoft.com wrote:
I was under the impression that only Dom0 Xen would emulate Hyper-V.
How that? It's the hypervisor that does the emulation, and obviously
not for Dom0, but for (HVM) DomU-s.
Jan
--
To unsubscribe from this list: send the line
On 24.01.13 at 19:59, Olaf Hering o...@aepfle.de wrote:
On Thu, Jan 24, KY Srinivasan wrote:
Question is - considering you stated that this is supported
starting in Win8, doesn't Hyper-V itself announce that
capability in some explicit way?
Thanks Jan. Unfortunately I don't think
On 24.01.13 at 02:17, K. Y. Srinivasan k...@microsoft.com wrote:
@@ -69,6 +74,11 @@ static void __init ms_hyperv_init_platform(void)
ms_hyperv.features, ms_hyperv.hints);
clocksource_register_hz(hyperv_cs, NSEC_PER_SEC/100);
+
+ /*
+ * Setup the IDT for
On Wed, Jan 23, 2013 at 05:56:09PM -0800, K. Y. Srinivasan wrote:
diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
index 1975122..803ca69 100644
--- a/arch/x86/kernel/entry_64.S
+++ b/arch/x86/kernel/entry_64.S
@@ -1446,11 +1446,16 @@ ENTRY(xen_failsafe_callback)
40 matches
Mail list logo
