On Fri, Nov 20, 2015 at 09:55:12AM +, Paul Durrant wrote:
> The Microsoft Hypervisor Top Level Functional Spec. (section 3.4) defines
> two bits in CPUID leaf 0x4004:EAX for the hypervisor to recommend
> whether or not to issue a hypercall for local or remote TLB flush.
>
> Whilst it's dou
> -Original Message-
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: 20 November 2015 09:55
> To: xen-de...@lists.xenproject.org
> Cc: Paul Durrant; Ian Jackson; Stefano Stabellini; Ian Campbell; Wei Liu; Keir
> (Xen.org); Andrew Cooper
> Subject: [PATCH v5] x86/hvm/viridian:
>>> On 20.11.15 at 10:55, wrote:
> +/*
> + * For each specified virtual CPU flush all ASIDs to invalidate
> + * TLB entries the next time it is scheduled and then, if it
> + * is currently running, add its physical CPU to a mask of
> + * those which need to
The Microsoft Hypervisor Top Level Functional Spec. (section 3.4) defines
two bits in CPUID leaf 0x4004:EAX for the hypervisor to recommend
whether or not to issue a hypercall for local or remote TLB flush.
Whilst it's doubtful whether using a hypercall for local TLB flush would
be any more ef