diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2022-05-25 13:59:47 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-05-25 21:26:35 +0200 |
| commit | aa6bb5fad58d049c6ea97448d4caba4499d60634 (patch) | |
| tree | a8b0cacf9ef47ce0a5e1bacbd26f0c8d776dc6ee /docs | |
| parent | 9411e8b6faeb1d88d4441c63c5ec072a01b2914e (diff) | |
| download | qemu-aa6bb5fad58d049c6ea97448d4caba4499d60634.zip qemu-aa6bb5fad58d049c6ea97448d4caba4499d60634.tar.gz qemu-aa6bb5fad58d049c6ea97448d4caba4499d60634.tar.bz2 | |
i386: Hyper-V Support extended GVA ranges for TLB flush hypercalls
KVM kind of supported "extended GVA ranges" (up to 4095 additional GFNs
per hypercall) since the implementation of Hyper-V PV TLB flush feature
(Linux-4.18) as regardless of the request, full TLB flush was always
performed. "Extended GVA ranges for TLB flush hypercalls" feature bit
wasn't exposed then. Now, as KVM gains support for fine-grained TLB
flush handling, exposing this feature starts making sense.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20220525115949.1294004-5-vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/hyperv.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/hyperv.txt b/docs/hyperv.txt index af1b10c..4b132b1 100644 --- a/docs/hyperv.txt +++ b/docs/hyperv.txt @@ -255,6 +255,13 @@ Hyper-V specification allows to pass parameters for certain hypercalls using XMM registers ("XMM Fast Hypercall Input"). When the feature is in use, it allows for faster hypercalls processing as KVM can avoid reading guest's memory. +3.24. hv-tlbflush-ext +===================== +Allow for extended GVA ranges to be passed to Hyper-V TLB flush hypercalls +(HvFlushVirtualAddressList/HvFlushVirtualAddressListEx). + +Requires: hv-tlbflush + 4. Supplementary features ========================= |