From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"Liu, Jinsong" <jinsong.liu@intel.com>,
Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH v2 0/7] APIC/IOAPIC cleanup
Date: Fri, 20 Aug 2010 10:42:01 +0200 [thread overview]
Message-ID: <4C6E3FD9.6080106@redhat.com> (raw)
In-Reply-To: <4C6DA75D.40303@codemonkey.ws>
On 08/19/2010 11:51 PM, Anthony Liguori wrote:
>>> Neither approach maps well to real hardware. An x86 CPU cannot exist
>>> without a local APIC and a local APIC cannot exist without an x86
>>> CPU. The
>>> two are fundamentally tied together.
>>
>> What about 486? Or 82489?
>
> Don't confuse the local APIC with the PIC or the I/O APIC.
>
> The local APIC has always existed in the CPU core. There is also an I/O
> APIC which exists outside of the CPU core. The local APIC was introduced
> with SMP support.
In theory it's possible to have a discrete local APIC on the 486 or the
Pentium. See figure 5-1 in the Intel multiprocessor specification.
> When you look at the local APIC (apic.c) however, you see that it's the
> only device in the tree that actually interacts with a CPUState.
Even worse, it does it through an opaque pointer even though the only
CPUState that makes sense there is the i386 CPUState. (BTW, there is
exactly one other example of a CPUState property, and it's in the CRIS PIC).
Paolo
next prev parent reply other threads:[~2010-08-20 8:42 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 ` Paolo Bonzini [this message]
2010-08-20 17:01 ` 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
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=4C6E3FD9.6080106@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--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).