Re: [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Roman Kagan
On Fri, Oct 09, 2015 at 04:41:15PM +0200, Paolo Bonzini wrote: > On 09/10/2015 15:39, Denis V. Lunev wrote: > > A new vcpu exit is introduced to notify the userspace of the > > changes in Hyper-V synic configuraion triggered by guest writing to the > > corresponding MSRs. > > Why is this exit

Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Eric Blake
On 10/12/2015 07:42 AM, Eric Blake wrote: > On 10/09/2015 07:39 AM, Denis V. Lunev wrote: >> From: Andrey Smetanin >> >> A new vcpu exit is introduced to notify the userspace of the >> changes in Hyper-V synic configuraion triggered by guest writing to the > >

Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Eric Blake
On 10/09/2015 07:39 AM, Denis V. Lunev wrote: > From: Andrey Smetanin > > A new vcpu exit is introduced to notify the userspace of the > changes in Hyper-V synic configuraion triggered by guest writing to the s/configuraion/configuration/ Is 'synic' intended? Is it

Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Denis V. Lunev
On 10/12/2015 04:42 PM, Eric Blake wrote: On 10/09/2015 07:39 AM, Denis V. Lunev wrote: From: Andrey Smetanin A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V synic configuraion triggered by guest writing to the

Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Roman Kagan
On Mon, Oct 12, 2015 at 07:42:42AM -0600, Eric Blake wrote: > On 10/09/2015 07:39 AM, Denis V. Lunev wrote: > > From: Andrey Smetanin > > > > A new vcpu exit is introduced to notify the userspace of the > > changes in Hyper-V synic configuraion triggered by guest writing

Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread Paolo Bonzini
On 12/10/2015 15:42, Eric Blake wrote: > > +related with Hyper-V emulation. Currently used to synchronize modified > > +Hyper-V synic state with userspace. > > Again, is 'synic' intended? Hmm, I see it throughout the patch, so it > looks intentional, but I keep trying to read it as a typo for

RE: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-12 Thread KY Srinivasan
g; rka...@virtuozzo.com; Paolo > Bonzini <pbonz...@redhat.com>; Andrey Smetanin > <asmeta...@virtuozzo.com>; Vitaly Kuznetsov <vkuzn...@redhat.com>; KY > Srinivasan <k...@microsoft.com> > Subject: Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit > > On 10

[PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-09 Thread Denis V. Lunev
From: Andrey Smetanin A new vcpu exit is introduced to notify the userspace of the changes in Hyper-V synic configuraion triggered by guest writing to the corresponding MSRs. Signed-off-by: Andrey Smetanin Reviewed-by: Roman Kagan

Re: [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-09 Thread Paolo Bonzini
On 09/10/2015 15:39, Denis V. Lunev wrote: > From: Andrey Smetanin > > A new vcpu exit is introduced to notify the userspace of the > changes in Hyper-V synic configuraion triggered by guest writing to the > corresponding MSRs. > > Signed-off-by: Andrey Smetanin

Re: [PATCH 2/2] kvm/x86: Hyper-V kvm exit

2015-10-09 Thread Paolo Bonzini
On 09/10/2015 16:53, Roman Kagan wrote: >> > Why is this exit necessary? > The guest writes to synic-related MSRs and that should take "immediate" > effect. > > E.g. it may decide to disable or relocate the message page by writing to > SIMP MSR. The host is then supposed to stop accessing the