From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Binbin Wu <binbin.wu@linux.intel.com>,
pbonzini@redhat.com, seanjc@google.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: sfr@canb.auug.org.au, rick.p.edgecombe@intel.com,
kai.huang@intel.com, adrian.hunter@intel.com,
reinette.chatre@intel.com, xiaoyao.li@intel.com,
tony.lindgren@intel.com, isaku.yamahata@intel.com,
yan.y.zhao@intel.com
Subject: Re: [PATCH] Documentation: KVM: Fix unexpected unindent warnings
Date: Wed, 25 Jun 2025 13:31:02 +0700 [thread overview]
Message-ID: <aFuXpoxMLa2Qj_S9@archie.me> (raw)
In-Reply-To: <20250625014829.82289-1-binbin.wu@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2804 bytes --]
On Wed, Jun 25, 2025 at 09:48:29AM +0800, Binbin Wu wrote:
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 9abf93ee5f65..a7dbe08dc376 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -7210,21 +7210,21 @@ number from register R11. The remaining field of the union provide the
> inputs and outputs of the TDVMCALL. Currently the following values of
> ``nr`` are defined:
>
> -* ``TDVMCALL_GET_QUOTE``: the guest has requested to generate a TD-Quote
> -signed by a service hosting TD-Quoting Enclave operating on the host.
> -Parameters and return value are in the ``get_quote`` field of the union.
> -The ``gpa`` field and ``size`` specify the guest physical address
> -(without the shared bit set) and the size of a shared-memory buffer, in
> -which the TDX guest passes a TD Report. The ``ret`` field represents
> -the return value of the GetQuote request. When the request has been
> -queued successfully, the TDX guest can poll the status field in the
> -shared-memory area to check whether the Quote generation is completed or
> -not. When completed, the generated Quote is returned via the same buffer.
> -
> -* ``TDVMCALL_GET_TD_VM_CALL_INFO``: the guest has requested the support
> -status of TDVMCALLs. The output values for the given leaf should be
> -placed in fields from ``r11`` to ``r14`` of the ``get_tdvmcall_info``
> -field of the union.
> + * ``TDVMCALL_GET_QUOTE``: the guest has requested to generate a TD-Quote
> + signed by a service hosting TD-Quoting Enclave operating on the host.
> + Parameters and return value are in the ``get_quote`` field of the union.
> + The ``gpa`` field and ``size`` specify the guest physical address
> + (without the shared bit set) and the size of a shared-memory buffer, in
> + which the TDX guest passes a TD Report. The ``ret`` field represents
> + the return value of the GetQuote request. When the request has been
> + queued successfully, the TDX guest can poll the status field in the
> + shared-memory area to check whether the Quote generation is completed or
> + not. When completed, the generated Quote is returned via the same buffer.
> +
> + * ``TDVMCALL_GET_TD_VM_CALL_INFO``: the guest has requested the support
> + status of TDVMCALLs. The output values for the given leaf should be
> + placed in fields from ``r11`` to ``r14`` of the ``get_tdvmcall_info``
> + field of the union.
>
> KVM may add support for more values in the future that may cause a userspace
> exit, even without calls to ``KVM_ENABLE_CAP`` or similar. In this case,
>
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-25 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 1:48 [PATCH] Documentation: KVM: Fix unexpected unindent warnings Binbin Wu
2025-06-25 6:31 ` Bagas Sanjaya [this message]
2025-06-25 22:25 ` Sean Christopherson
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=aFuXpoxMLa2Qj_S9@archie.me \
--to=bagasdotme@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.lindgren@intel.com \
--cc=xiaoyao.li@intel.com \
--cc=yan.y.zhao@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).