From: Steven Price <steven.price@arm.com>
To: Usama Arif <usama.arif@bytedance.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-doc@vger.kernel.org,
virtualization@lists.linux-foundation.org, linux@armlinux.org.uk,
yezengruan@huawei.com, catalin.marinas@arm.com, will@kernel.org,
maz@kernel.org, mark.rutland@arm.com, bagasdotme@gmail.com
Cc: fam.zheng@bytedance.com, liangma@liangbit.com,
punit.agrawal@bytedance.com
Subject: Re: [PATCH] kvm/arm: Fix pvtime documentation
Date: Thu, 3 Nov 2022 13:45:06 +0000 [thread overview]
Message-ID: <fbdec740-5654-ee23-caa0-22cc7d7b1f02@arm.com> (raw)
In-Reply-To: <20221103131210.3603385-1-usama.arif@bytedance.com>
On 03/11/2022 13:12, Usama Arif wrote:
> This includes table format and using reST labels for
> cross-referencing to vcpu.rst.
>
> Suggested-by: Bagas Sanjaya <bagasdotme@gmail.com>
> Signed-off-by: Usama Arif <usama.arif@bytedance.com>
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> Documentation/virt/kvm/arm/pvtime.rst | 14 ++++++++------
> Documentation/virt/kvm/devices/vcpu.rst | 2 ++
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/virt/kvm/arm/pvtime.rst b/Documentation/virt/kvm/arm/pvtime.rst
> index 392521af7c90..e88b34e586be 100644
> --- a/Documentation/virt/kvm/arm/pvtime.rst
> +++ b/Documentation/virt/kvm/arm/pvtime.rst
> @@ -23,21 +23,23 @@ the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1
> ARCH_FEATURES mechanism before calling it.
>
> PV_TIME_FEATURES
> - ============= ======== ==========
> +
> + ============= ======== =================================================
> Function ID: (uint32) 0xC5000020
> PV_call_id: (uint32) The function to query for support.
> Currently only PV_TIME_ST is supported.
> Return value: (int64) NOT_SUPPORTED (-1) or SUCCESS (0) if the relevant
> PV-time feature is supported by the hypervisor.
> - ============= ======== ==========
> + ============= ======== =================================================
>
> PV_TIME_ST
> - ============= ======== ==========
> +
> + ============= ======== ==============================================
> Function ID: (uint32) 0xC5000021
> Return value: (int64) IPA of the stolen time data structure for this
> VCPU. On failure:
> NOT_SUPPORTED (-1)
> - ============= ======== ==========
> + ============= ======== ==============================================
>
> The IPA returned by PV_TIME_ST should be mapped by the guest as normal memory
> with inner and outer write back caching attributes, in the inner shareable
> @@ -76,5 +78,5 @@ It is advisable that one or more 64k pages are set aside for the purpose of
> these structures and not used for other purposes, this enables the guest to map
> the region using 64k pages and avoids conflicting attributes with other memory.
>
> -For the user space interface see Documentation/virt/kvm/devices/vcpu.rst
> -section "3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL".
> +For the user space interface see
> +:ref:`Documentation/virt/kvm/devices/vcpu.rst <kvm_arm_vcpu_pvtime_ctrl>`.
> \ No newline at end of file
> diff --git a/Documentation/virt/kvm/devices/vcpu.rst b/Documentation/virt/kvm/devices/vcpu.rst
> index 716aa3edae14..31f14ec4a65b 100644
> --- a/Documentation/virt/kvm/devices/vcpu.rst
> +++ b/Documentation/virt/kvm/devices/vcpu.rst
> @@ -171,6 +171,8 @@ configured values on other VCPUs. Userspace should configure the interrupt
> numbers on at least one VCPU after creating all VCPUs and before running any
> VCPUs.
>
> +.. _kvm_arm_vcpu_pvtime_ctrl:
> +
> 3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL
> ==================================
>
next prev parent reply other threads:[~2022-11-03 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:12 [PATCH] kvm/arm: Fix pvtime documentation Usama Arif
2022-11-03 13:45 ` Steven Price [this message]
2022-11-03 13:55 ` Bagas Sanjaya
2022-11-03 15:42 ` Marc Zyngier
2022-11-04 1:48 ` Bagas Sanjaya
2022-11-04 11:06 ` Marc Zyngier
2022-11-04 12:19 ` Bagas Sanjaya
2022-11-03 15:47 ` Marc Zyngier
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=fbdec740-5654-ee23-caa0-22cc7d7b1f02@arm.com \
--to=steven.price@arm.com \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=fam.zheng@bytedance.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=liangma@liangbit.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=punit.agrawal@bytedance.com \
--cc=usama.arif@bytedance.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@kernel.org \
--cc=yezengruan@huawei.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