From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] qemu-kvm: Remove kvm_set_boot_cpu_id
Date: Mon, 20 Jun 2011 11:56:21 -0300 [thread overview]
Message-ID: <20110620145621.GB15986@amt.cnet> (raw)
In-Reply-To: <4DE8F23B.1030508@siemens.com>
On Fri, Jun 03, 2011 at 04:39:55PM +0200, Jan Kiszka wrote:
> Upstream just as well as qemu-kvm only support CPU 0 as boot CPU. And
> that is also the KVM ABI default if the user does not issue any
> KVM_SET_BOOT_CPU_ID.
>
> So let's drop this redundancy. It can be re-introduced via upstream once
> we support something more sophisticated.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> qemu-kvm.c | 11 -----------
> qemu-kvm.h | 2 --
> target-i386/kvm.c | 5 -----
> 3 files changed, 0 insertions(+), 18 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2011-06-20 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 14:39 [PATCH] qemu-kvm: Remove kvm_set_boot_cpu_id Jan Kiszka
2011-06-20 14:56 ` Marcelo Tosatti [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=20110620145621.GB15986@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
/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