Roman Kagan <rkagan@xxxxxxxxxxxxx> writes: > On Mon, Apr 02, 2018 at 06:10:54PM +0200, Vitaly Kuznetsov wrote: >> >> Feature description: >> >> PV TLB flush helps a lot when running overcommited. KVM gained support for >> it recently but it is only available for Linux guests. Windows guests use >> emulated Hyper-V interface and PV TLB flush needs to be added there. >> > > I vaguely remember Denis Plotnikov (cc-d) did a similar attempt a couple > of years ago. IIRC the outcome was that win2012r2 (back then) guests > started to also use this mechanism for local tlb flushes via self-IPI, > which led to noticable degradation on certain workloads. > Thanks for the feedback, in theory it shouldn't do that. Hyper-V has different enlightenments for local and remote TLB flushing: Implementation Recommendations - 0x40000004 ... Bit 1: Recommend using hypercall for local TLB flushes rather than INVLPG or MOV to CR3 instructions Bit 2: Recommend using hypercall for remote TLB flushes rather than inter-processor interrupts ... I see no reason to do local flushes with a hypercall so we'll only be announcing remote. In case things are irreparably broken with WS2012 we can still have the feature in KVM and decide if we want to announce it to guests on a higher level (probably even higher than Qemu as this will just become another 'hv_tlbflush' feature which needs to be enabled) based on Windows version. -- Vitaly
