x86/pvh: drop v2 suffix from pvh.pandoc

There is now only one version of PVH implementation in Xen. Drop "v2" to
avoid confusion.

Signed-off-by: Wei Liu <wl@xen.org>
Acked-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
This commit is contained in:
Wei Liu committed 2020-02-25 17:21:45 +00:00
1 parent 37a5b5f673
commit d90bcb5f10
1 file changed
+2 -2
+2 -2
View File
@@ -64,7 +64,7 @@ The following VCPU hypercalls can be used in order to bring up secondary vCPUs:
## Hardware description ## ## Hardware description ##
PVHv2 guests that have access to hardware (either emulated or real) will also PVH guests that have access to hardware (either emulated or real) will also
have ACPI tables with the description of the hardware that's available to the have ACPI tables with the description of the hardware that's available to the
guest. This applies to both privileged and unprivileged guests. A pointer to guest. This applies to both privileged and unprivileged guests. A pointer to
the position of the RSDP in memory (if present) can be fetched from the start the position of the RSDP in memory (if present) can be fetched from the start
@@ -79,7 +79,7 @@ done for HVM guests.
Interrupts from physical devices are delivered using native methods, this is Interrupts from physical devices are delivered using native methods, this is
done in order to take advantage of new hardware assisted virtualization done in order to take advantage of new hardware assisted virtualization
functions, like posted interrupts. This implies that PVHv2 guests with physical functions, like posted interrupts. This implies that PVH guests with physical
devices will also have the necessary interrupt controllers in order to manage devices will also have the necessary interrupt controllers in order to manage
the delivery of interrupts from those devices, using the same interfaces that the delivery of interrupts from those devices, using the same interfaces that
are available on native hardware. are available on native hardware.
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.