From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Subject: CPU hot-plugging interface
Date: Thu, 10 Dec 2009 14:55:03 +0100 [thread overview]
Message-ID: <4B20FDB7.1050203@siemens.com> (raw)
Hi,
based on my naive and unsuccessful tests to add a CPU that was not
declared on qemu startup via "-smp", I assume that the monitor command
"cpu_set" lacks some range check, right? Or is it allowed to add CPUs
dynamically that way? Then there would be some bug in qemu-kvm's (next
branch) CPU management.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
reply other threads:[~2009-12-10 13:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B20FDB7.1050203@siemens.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.