Roman Kagan writes:
> On Wed, Nov 13, 2019 at 10:29:00AM +0100, Vitaly Kuznetsov wrote:
>> Roman Kagan writes:
>> > On Tue, Nov 12, 2019 at 11:34:27AM +0800, lantianyu1...@gmail.com wrote:
>> >> From: Tianyu Lan
>> >>
>> >> Hyper-V direct tlb flush targets KVM on Hyper-V guest.
>> >> Enable
On Wed, Nov 13, 2019 at 10:29:00AM +0100, Vitaly Kuznetsov wrote:
> Roman Kagan writes:
> > On Tue, Nov 12, 2019 at 11:34:27AM +0800, lantianyu1...@gmail.com wrote:
> >> From: Tianyu Lan
> >>
> >> Hyper-V direct tlb flush targets KVM on Hyper-V guest.
> >> Enable direct TLB flush for its guests
Roman Kagan writes:
> On Tue, Nov 12, 2019 at 11:34:27AM +0800, lantianyu1...@gmail.com wrote:
>> From: Tianyu Lan
>>
>> Hyper-V direct tlb flush targets KVM on Hyper-V guest.
>> Enable direct TLB flush for its guests meaning that TLB
>> flush hypercalls are handled by Level 0 hypervisor
On Tue, Nov 12, 2019 at 11:34:27AM +0800, lantianyu1...@gmail.com wrote:
> From: Tianyu Lan
>
> Hyper-V direct tlb flush targets KVM on Hyper-V guest.
> Enable direct TLB flush for its guests meaning that TLB
> flush hypercalls are handled by Level 0 hypervisor (Hyper-V)
> bypassing KVM in Level
From: Tianyu Lan
Hyper-V direct tlb flush targets KVM on Hyper-V guest.
Enable direct TLB flush for its guests meaning that TLB
flush hypercalls are handled by Level 0 hypervisor (Hyper-V)
bypassing KVM in Level 1. Due to the different ABI for hypercall
parameters between Hyper-V and KVM, KVM