Linux Documentation
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Emanuele Giuseppe Esposito <eesposit@redhat.com>,
	linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Andrew Jones <drjones@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation/kvm: additional explanations on KVM_SET_BOOT_CPU_ID
Date: Fri, 19 Mar 2021 10:31:43 +0100	[thread overview]
Message-ID: <8d48bf1b-208c-89fb-1150-b9d7f589e152@redhat.com> (raw)
In-Reply-To: <20210319091650.11967-1-eesposit@redhat.com>

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@redhat.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


      reply	other threads:[~2021-03-19  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  9:16 [PATCH] documentation/kvm: additional explanations on KVM_SET_BOOT_CPU_ID Emanuele Giuseppe Esposito
2021-03-19  9:31 ` Paolo Bonzini [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=8d48bf1b-208c-89fb-1150-b9d7f589e152@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=corbet@lwn.net \
    --cc=drjones@redhat.com \
    --cc=eesposit@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkuznets@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