From: Jonathan Corbet <corbet@lwn.net>
To: Connor Kuehl <ckuehl@redhat.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: kvm: fix referenced ioctl symbol
Date: Wed, 9 Sep 2020 11:20:08 -0600 [thread overview]
Message-ID: <20200909112008.23859385@lwn.net> (raw)
In-Reply-To: <20200819211952.251984-1-ckuehl@redhat.com>
On Wed, 19 Aug 2020 16:19:52 -0500
Connor Kuehl <ckuehl@redhat.com> wrote:
> The actual symbol that is exported and usable is
> 'KVM_MEMORY_ENCRYPT_OP', not 'KVM_MEM_ENCRYPT_OP'
>
> $ git grep -l KVM_MEM_ENCRYPT_OP
> Documentation/virt/kvm/amd-memory-encryption.rst
>
> $ git grep -l KVM_MEMORY_ENCRYPT_OP
> Documentation/virt/kvm/api.rst
> arch/x86/kvm/x86.c
> include/uapi/linux/kvm.h
> tools/include/uapi/linux/kvm.h
>
> While we're in there, update the KVM API category for
> KVM_MEMORY_ENCRYPT_OP. It is called on a VM file descriptor.
>
> Signed-off-by: Connor Kuehl <ckuehl@redhat.com>
> ---
> Documentation/virt/kvm/amd-memory-encryption.rst | 6 +++---
> Documentation/virt/kvm/api.rst | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/virt/kvm/amd-memory-encryption.rst b/Documentation/virt/kvm/amd-memory-encryption.rst
> index 2d44388438cc..09a8f2a34e39 100644
> --- a/Documentation/virt/kvm/amd-memory-encryption.rst
> +++ b/Documentation/virt/kvm/amd-memory-encryption.rst
> @@ -53,11 +53,11 @@ key management interface to perform common hypervisor activities such as
> encrypting bootstrap code, snapshot, migrating and debugging the guest. For more
> information, see the SEV Key Management spec [api-spec]_
>
> -The main ioctl to access SEV is KVM_MEM_ENCRYPT_OP. If the argument
> -to KVM_MEM_ENCRYPT_OP is NULL, the ioctl returns 0 if SEV is enabled
> +The main ioctl to access SEV is KVM_MEMORY_ENCRYPT_OP. If the argument
> +to KVM_MEMORY_ENCRYPT_OP is NULL, the ioctl returns 0 if SEV is enabled
> and ``ENOTTY` if it is disabled (on some older versions of Linux,
> the ioctl runs normally even with a NULL argument, and therefore will
> -likely return ``EFAULT``). If non-NULL, the argument to KVM_MEM_ENCRYPT_OP
> +likely return ``EFAULT``). If non-NULL, the argument to KVM_MEMORY_ENCRYPT_OP
> must be a struct kvm_sev_cmd::
>
> struct kvm_sev_cmd {
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index eb3a1316f03e..506c8426c583 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -4211,7 +4211,7 @@ H_GET_CPU_CHARACTERISTICS hypercall.
>
> :Capability: basic
> :Architectures: x86
> -:Type: system
> +:Type: vm
> :Parameters: an opaque platform specific structure (in/out)
> :Returns: 0 on success; -1 on error
>
So this appears to have fallen through the cracks. It looks correct to
me, so I've applied it, thanks.
jon
prev parent reply other threads:[~2020-09-09 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 21:19 Connor Kuehl
2020-09-09 17:20 ` Jonathan Corbet [this message]
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=20200909112008.23859385@lwn.net \
--to=corbet@lwn.net \
--cc=ckuehl@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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
all inboxes | Powered by JetHome®