From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"Liu @mail.corp.redhat.com>> \"Liu,
Jinsong\"" <jinsong.liu@intel.com>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup
Date: Mon, 23 Aug 2010 11:05:06 -0500 [thread overview]
Message-ID: <4C729C32.5040803@codemonkey.ws> (raw)
In-Reply-To: <m3aaod5pqn.fsf@blackfin.pond.sub.org>
On 08/23/2010 10:10 AM, Markus Armbruster wrote:
> You lost me. A few messages upthread.
>
> What's the *practical* problem again?
>
CPU hotplug adds a local APIC to Sysbus but Sysbus does not allow hot plug.
I believe the right short term way to fix this is to take the local APIC
off of Sysbus. The right long term fix is to not make the local APIC a
qdev device and instead fold it into CPUX86State.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-08-23 16:05 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 21:14 [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup Blue Swirl
2010-06-13 16:56 ` [Qemu-devel] " Jan Kiszka
2010-06-13 17:03 ` Andreas Färber
2010-06-13 17:53 ` Blue Swirl
2010-06-13 18:17 ` Andreas Färber
2010-06-13 17:49 ` Blue Swirl
2010-08-19 19:33 ` [Qemu-devel] " Anthony Liguori
2010-08-19 20:09 ` Blue Swirl
2010-08-19 20:49 ` Anthony Liguori
2010-08-19 21:21 ` Blue Swirl
2010-08-19 21:51 ` Anthony Liguori
2010-08-19 22:52 ` malc
2010-08-20 1:01 ` Anthony Liguori
2010-08-20 10:00 ` malc
2010-08-20 8:42 ` [Qemu-devel] " Paolo Bonzini
2010-08-20 17:01 ` [Qemu-devel] " Markus Armbruster
2010-08-20 18:38 ` Anthony Liguori
2010-08-22 20:28 ` Avi Kivity
2010-08-22 21:02 ` Anthony Liguori
2010-08-23 5:46 ` Avi Kivity
2010-08-23 13:23 ` Anthony Liguori
2010-08-23 13:42 ` Avi Kivity
2010-08-23 13:48 ` Anthony Liguori
2010-08-23 14:00 ` Avi Kivity
2010-08-23 14:26 ` Anthony Liguori
2010-08-23 14:32 ` Avi Kivity
2010-08-23 14:47 ` Anthony Liguori
2010-08-23 15:10 ` Markus Armbruster
2010-08-23 16:05 ` Anthony Liguori [this message]
2010-08-23 17:36 ` Markus Armbruster
2010-08-23 17:47 ` Anthony Liguori
2010-08-23 18:24 ` [Qemu-devel] " Jan Kiszka
2010-08-23 18:29 ` Anthony Liguori
2010-08-23 15:14 ` [Qemu-devel] " Avi Kivity
2010-08-23 16:02 ` Anthony Liguori
2010-08-24 9:51 ` Avi Kivity
2010-08-20 19:26 ` Blue Swirl
2010-08-20 10:35 ` [Qemu-devel] " Jan Kiszka
2010-08-22 9:37 ` [Qemu-devel] " Avi Kivity
2010-08-22 18:52 ` Anthony Liguori
2010-08-22 19:44 ` Avi Kivity
2010-08-22 20:03 ` Anthony Liguori
2010-08-22 20:33 ` Avi Kivity
2010-08-22 21:06 ` Anthony Liguori
2010-08-23 5:49 ` Avi Kivity
2010-08-23 9:09 ` [Qemu-devel] " Jan Kiszka
2010-08-23 9:25 ` Avi Kivity
2010-08-23 10:11 ` Alexander Graf
2010-08-23 10:15 ` Avi Kivity
2010-08-23 10:18 ` Alexander Graf
2010-08-23 10:25 ` Avi Kivity
2010-08-22 21:07 ` [Qemu-devel] " Anthony Liguori
2010-08-23 5:48 ` Avi Kivity
2010-08-22 9:13 ` Avi Kivity
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=4C729C32.5040803@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jinsong.liu@intel.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).