docs/system/arm/cpu-features.rst: Fix formatting

The markup for the Arm CPU feature documentation is incorrect,
and results in the HTML not rendering correctly -- the first
line of each description is rendered in boldface as if it
were part of the option name.

Reformat to match the styling used in cpu-models-x86.rst.inc.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1479
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Message-id: 20230316105808.1414003-1-peter.maydell@linaro.org
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
This commit is contained in:
Peter Maydell 2023-03-16 10:58:08 +00:00
parent 3202b2628b
commit d4e2cc9aa4
1 changed files with 30 additions and 38 deletions

View File

@ -177,39 +177,32 @@ are named with the prefix "kvm-". KVM VCPU features may be probed,
enabled, and disabled in the same way as other CPU features. Below is enabled, and disabled in the same way as other CPU features. Below is
the list of KVM VCPU features and their descriptions. the list of KVM VCPU features and their descriptions.
kvm-no-adjvtime By default kvm-no-adjvtime is disabled. This ``kvm-no-adjvtime``
means that by default the virtual time By default kvm-no-adjvtime is disabled. This means that by default
adjustment is enabled (vtime is not *not* the virtual time adjustment is enabled (vtime is not *not* adjusted).
adjusted).
When virtual time adjustment is enabled each When virtual time adjustment is enabled each time the VM transitions
time the VM transitions back to running state back to running state the VCPU's virtual counter is updated to
the VCPU's virtual counter is updated to ensure ensure stopped time is not counted. This avoids time jumps
stopped time is not counted. This avoids time surprising guest OSes and applications, as long as they use the
jumps surprising guest OSes and applications, virtual counter for timekeeping. However it has the side effect of
as long as they use the virtual counter for the virtual and physical counters diverging. All timekeeping based
timekeeping. However it has the side effect of on the virtual counter will appear to lag behind any timekeeping
the virtual and physical counters diverging. that does not subtract VM stopped time. The guest may resynchronize
All timekeeping based on the virtual counter its virtual counter with other time sources as needed.
will appear to lag behind any timekeeping that
does not subtract VM stopped time. The guest
may resynchronize its virtual counter with
other time sources as needed.
Enable kvm-no-adjvtime to disable virtual time Enable kvm-no-adjvtime to disable virtual time adjustment, also
adjustment, also restoring the legacy (pre-5.0) restoring the legacy (pre-5.0) behavior.
behavior.
kvm-steal-time Since v5.2, kvm-steal-time is enabled by ``kvm-steal-time``
default when KVM is enabled, the feature is Since v5.2, kvm-steal-time is enabled by default when KVM is
supported, and the guest is 64-bit. enabled, the feature is supported, and the guest is 64-bit.
When kvm-steal-time is enabled a 64-bit guest When kvm-steal-time is enabled a 64-bit guest can account for time
can account for time its CPUs were not running its CPUs were not running due to the host not scheduling the
due to the host not scheduling the corresponding corresponding VCPU threads. The accounting statistics may influence
VCPU threads. The accounting statistics may the guest scheduler behavior and/or be exposed to the guest
influence the guest scheduler behavior and/or be userspace.
exposed to the guest userspace.
TCG VCPU Features TCG VCPU Features
================= =================
@ -217,15 +210,14 @@ TCG VCPU Features
TCG VCPU features are CPU features that are specific to TCG. TCG VCPU features are CPU features that are specific to TCG.
Below is the list of TCG VCPU features and their descriptions. Below is the list of TCG VCPU features and their descriptions.
pauth-impdef When ``FEAT_Pauth`` is enabled, either the ``pauth-impdef``
*impdef* (Implementation Defined) algorithm When ``FEAT_Pauth`` is enabled, either the *impdef* (Implementation
is enabled or the *architected* QARMA algorithm Defined) algorithm is enabled or the *architected* QARMA algorithm
is enabled. By default the impdef algorithm is enabled. By default the impdef algorithm is disabled, and QARMA
is disabled, and QARMA is enabled. is enabled.
The architected QARMA algorithm has good The architected QARMA algorithm has good cryptographic properties,
cryptographic properties, but can be quite slow but can be quite slow to emulate. The impdef algorithm used by QEMU
to emulate. The impdef algorithm used by QEMU
is non-cryptographic but significantly faster. is non-cryptographic but significantly faster.
SVE CPU Properties SVE CPU Properties