[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8d48bf1b-208c-89fb-1150-b9d7f589e152@redhat.com>
Date: Fri, 19 Mar 2021 10:31:43 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Emanuele Giuseppe Esposito <eesposit@...hat.com>,
linux-doc@...r.kernel.org
Cc: Jonathan Corbet <corbet@....net>,
Andrew Jones <drjones@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] documentation/kvm: additional explanations on
KVM_SET_BOOT_CPU_ID
On 19/03/21 10:16, Emanuele Giuseppe Esposito wrote:
> The ioctl KVM_SET_BOOT_CPU_ID fails when called after vcpu creation.
> Add this explanation in the documentation.
>
> Signed-off-by: Emanuele Giuseppe Esposito <eesposit@...hat.com>
> ---
> Documentation/virt/kvm/api.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 38e327d4b479..bece398227f5 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -1495,7 +1495,8 @@ Fails if any VCPU has already been created.
>
> Define which vcpu is the Bootstrap Processor (BSP). Values are the same
> as the vcpu id in KVM_CREATE_VCPU. If this ioctl is not called, the default
> -is vcpu 0.
> +is vcpu 0. This ioctl has to be called before vcpu creation,
> +otherwise it will return EBUSY error.
>
>
> 4.42 KVM_GET_XSAVE
>
Queued, thanks.
Paolo
Powered by blists - more mailing lists