From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Vasilis Liaskovitis <vliaskov@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] cpu hotplug issue
Date: Thu, 21 Jul 2011 14:35:09 +0200 [thread overview]
Message-ID: <4E281CFD.2030805@siemens.com> (raw)
In-Reply-To: <20110721122559.GG3044@redhat.com>
On 2011-07-21 14:25, Gleb Natapov wrote:
> On Thu, Jul 21, 2011 at 02:22:07PM +0200, Jan Kiszka wrote:
>> On 2011-07-21 13:06, Vasilis Liaskovitis wrote:
>>> More precisely: To enable cpu-hotplug at each bisect stage, I apply
>>> this patch derived from:
>>> http://lists.gnu.org/archive/html/qemu-devel/2010-08/msg00850.html
>>>
>>> diff --git a/hw/qdev.c b/hw/qdev.c
>>> index 1aa1ea0..aed48ce 100644
>>> --- a/hw/qdev.c
>>> +++ b/hw/qdev.c
>>> @@ -327,6 +327,7 @@ BusState *sysbus_get_default(void)
>>> if (!main_system_bus) {
>>> main_system_bus = qbus_create(&system_bus_info, NULL,
>>> "main-system-bus");
>>> + main_system_bus->allow_hotplug = 1;
>>
>> BTW, this reminds me why "fixing" CPU hotplug won't help a lot. We
> I do not see relation between qdev not allowing cpu hotplug bug
It's not a bug, it's a feature: The system bus we attach APICs to so far
is a statically configured beast, intentionally hotplug-incapable.
Hacking this away in qemu-kvm will be a step towards where we came from
and will break sooner or later again. We need a CPU/APIC bus, also for
other reasons, that can then be made hotplug-capable.
> and cpu been
> created with incorrect state bug. Fixing of former will not magically
> make later disappear. Both should be solved.
The issues hidden by the topology design problem should be solved
nevertheless, that's true.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-07-21 12:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 17:40 cpu hotplug issue Vasilis Liaskovitis
2011-07-20 8:35 ` Gleb Natapov
2011-07-21 11:06 ` [PATCH] " Vasilis Liaskovitis
2011-07-21 11:33 ` Gleb Natapov
2011-07-21 11:42 ` Jan Kiszka
2011-07-21 11:51 ` Gleb Natapov
2011-07-21 11:55 ` Jan Kiszka
2011-07-21 12:00 ` Gleb Natapov
2011-07-21 12:18 ` Avi Kivity
2011-07-21 12:22 ` Gleb Natapov
2011-07-21 12:39 ` Jan Kiszka
2011-07-21 13:27 ` Lucas Meneghel Rodrigues
2011-07-21 12:45 ` Gleb Natapov
2011-07-22 10:56 ` Jan Kiszka
2011-07-24 11:56 ` Gleb Natapov
2011-07-24 16:11 ` Jan Kiszka
2011-07-25 13:18 ` Jan Kiszka
2011-07-25 13:21 ` Gleb Natapov
2011-07-25 13:26 ` Jan Kiszka
2011-07-27 16:35 ` Vasilis Liaskovitis
2011-07-28 16:52 ` Jan Kiszka
2011-08-02 9:46 ` Vasilis Liaskovitis
2011-08-02 10:24 ` Jan Kiszka
2011-08-02 13:41 ` Vasilis Liaskovitis
2011-08-03 10:07 ` Vasilis Liaskovitis
2011-08-03 10:37 ` Jan Kiszka
2011-08-03 10:38 ` Gleb Natapov
2011-08-03 10:42 ` Jan Kiszka
2011-08-03 16:25 ` Vasilis Liaskovitis
2011-08-04 8:01 ` Gleb Natapov
2011-08-04 8:40 ` Jan Kiszka
2011-07-21 13:08 ` Vasilis Liaskovitis
2011-07-21 13:11 ` Gleb Natapov
2011-07-21 13:12 ` Vasilis Liaskovitis
2011-07-21 13:13 ` Gleb Natapov
2011-07-21 13:15 ` Avi Kivity
2011-07-21 13:15 ` Avi Kivity
2011-07-21 11:36 ` Jan Kiszka
2011-07-21 12:22 ` Jan Kiszka
2011-07-21 12:25 ` Gleb Natapov
2011-07-21 12:35 ` Jan Kiszka [this message]
2011-07-21 12:40 ` Gleb Natapov
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=4E281CFD.2030805@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=vliaskov@gmail.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