From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Ninad Palsule" <ninad@linux.ibm.com>,
sebott@redhat.com, maz@kernel.org,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Alistair Francis" <alistair@alistair23.me>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Tyrone Ting" <kfting@nuvoton.com>,
"Hao Wu" <wuhaotsh@google.com>,
"Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>, "Joel Stanley" <joel@jms.id.au>,
"Eric Auger" <eric.auger@redhat.com>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
"Yi Liu" <yi.l.liu@intel.com>,
qemu-arm@nongnu.org, "Alexandre Iooss" <erdnaxe@crans.org>,
"Kashyap Chamarthy" <kchamart@redhat.com>
Subject: [PATCH v2 1/3] docs/cpu-features: Consistently use vCPU instead of VCPU
Date: Mon, 17 Feb 2025 22:07:27 +0530 [thread overview]
Message-ID: <20250217163732.3718617-2-kchamart@redhat.com> (raw)
In-Reply-To: <20250217163732.3718617-1-kchamart@redhat.com>
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
docs/system/arm/cpu-features.rst | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index 37d5dfd15b..a596316384 100644
--- a/docs/system/arm/cpu-features.rst
+++ b/docs/system/arm/cpu-features.rst
@@ -27,7 +27,7 @@ disabled, enables the optional AArch32 CPU feature, is only supported
when using the KVM accelerator and when running on a host CPU type that
supports the feature. While ``aarch64`` currently only works with KVM,
it could work with TCG. CPU features that are specific to KVM are
-prefixed with "kvm-" and are described in "KVM VCPU Features".
+prefixed with "kvm-" and are described in "KVM vCPU Features".
CPU Feature Probing
===================
@@ -167,22 +167,22 @@ disabling many SVE vector lengths would be quite verbose, the ``sve<N>`` CPU
properties have special semantics (see "SVE CPU Property Parsing
Semantics").
-KVM VCPU Features
+KVM vCPU Features
=================
-KVM VCPU features are CPU features that are specific to KVM, such as
+KVM vCPU features are CPU features that are specific to KVM, such as
paravirt features or features that enable CPU virtualization extensions.
The features' CPU properties are only available when KVM is enabled and
-are named with the prefix "kvm-". KVM VCPU features may be probed,
+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
-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 means that by default
the virtual time adjustment is enabled (vtime is not *not* adjusted).
When virtual time adjustment is enabled each time the VM transitions
- back to running state the VCPU's virtual counter is updated to
+ back to running state the vCPU's virtual counter is updated to
ensure stopped time is not counted. This avoids time jumps
surprising guest OSes and applications, as long as they use the
virtual counter for timekeeping. However it has the side effect of
@@ -200,15 +200,15 @@ the list of KVM VCPU features and their descriptions.
When kvm-steal-time is enabled a 64-bit guest can account for time
its CPUs were not running due to the host not scheduling the
- corresponding VCPU threads. The accounting statistics may influence
+ corresponding vCPU threads. The accounting statistics may influence
the guest scheduler behavior and/or be exposed to the guest
userspace.
-TCG VCPU Features
+TCG vCPU Features
=================
-TCG VCPU features are CPU features that are specific to TCG.
-Below is the list of TCG VCPU features and their descriptions.
+TCG vCPU features are CPU features that are specific to TCG.
+Below is the list of TCG vCPU features and their descriptions.
``pauth``
Enable or disable ``FEAT_Pauth`` entirely.
--
2.48.1
next prev parent reply other threads:[~2025-02-17 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 16:37 [PATCH v2 0/3] docs: Small changes to system/arm/cpu-features and more Kashyap Chamarthy
2025-02-17 16:37 ` Kashyap Chamarthy [this message]
2025-02-17 16:42 ` [PATCH v2 1/3] docs/cpu-features: Consistently use vCPU instead of VCPU Peter Maydell
2025-02-17 17:45 ` Eric Auger
2025-02-17 16:37 ` [PATCH v2 2/3] docs/cpu-features: Update "PAuth" (Pointer Authentication) details Kashyap Chamarthy
2025-02-17 17:43 ` Eric Auger
2025-02-18 11:28 ` Kashyap Chamarthy
2025-02-18 11:34 ` Peter Maydell
2025-02-18 11:42 ` Eric Auger
2025-02-18 12:02 ` Kashyap Chamarthy
2025-02-17 16:37 ` [PATCH v2 3/3] docs: Fix "Arm" capitalization Kashyap Chamarthy
2025-02-17 16:44 ` Peter Maydell
2025-02-17 17:44 ` Eric Auger
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 13:50 [PATCH v2 0/3] docs: Small changes to system/arm/cpu-features and more Kashyap Chamarthy
2025-02-13 13:50 ` [PATCH v2 1/3] docs/cpu-features: Consistently use vCPU instead of VCPU Kashyap Chamarthy
2025-02-13 21:09 ` Alex Bennée
2025-02-14 15:06 ` Kashyap Chamarthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250217163732.3718617-2-kchamart@redhat.com \
--to=kchamart@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair@alistair23.me \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=edgar.iglesias@gmail.com \
--cc=erdnaxe@crans.org \
--cc=eric.auger@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kfting@nuvoton.com \
--cc=leetroy@gmail.com \
--cc=maz@kernel.org \
--cc=ninad@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sebott@redhat.com \
--cc=steven_lee@aspeedtech.com \
--cc=wuhaotsh@google.com \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).