From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43486) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RI0FN-0000AA-Sr for qemu-devel@nongnu.org; Sun, 23 Oct 2011 11:46:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RI0FM-0007vf-Qx for qemu-devel@nongnu.org; Sun, 23 Oct 2011 11:46:01 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:59895) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RI0FM-0007vW-DH for qemu-devel@nongnu.org; Sun, 23 Oct 2011 11:46:00 -0400 Message-ID: <4EA436A6.4050702@web.de> Date: Sun, 23 Oct 2011 17:45:42 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <1318989353-5576-1-git-send-email-pingfank@linux.vnet.ibm.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFF3E81C2BEAE378D58661768" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [PATCH 1/1] Introduce a new bus "ICC" to connect APIC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: aliguori@us.ibm.com, pingfank@linux.vnet.ibm.com, qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFF3E81C2BEAE378D58661768 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2011-10-23 14:40, Blue Swirl wrote: > I'm not sure that a full bus is needed for now, even if it could match > real HW better, since the memory API already provides the separation > needed. Perhaps this would be needed later to make IRQs per-CPU also, > or to put IOAPIC also to the bus? The ICC interconnects LAPICs and IOAPICs. So it should next take over the management of the local_apics array from apic.c and the ioapics array from ioapic.c. It could implement generic message delivery services. Every bus participant would then have a reception handler that first checks the type and additional fields of a generic ICC message and, on match, forwards it to the corresponding device model functions. That would allow for something nicer than global apic_deliver_irq or ioapic_eoi_broadcast. That's clearly beyond the scope of this series but a good reason to model the ICC as accurately as qdev allows right from the start. Jan --------------enigFF3E81C2BEAE378D58661768 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6kNqgACgkQitSsb3rl5xRLAACfU9H2pahxALg9J8UflA3RPuGz s3cAoIXshqf7M23E2Efxecg0Gj+NiKIf =eY/Z -----END PGP SIGNATURE----- --------------enigFF3E81C2BEAE378D58661768--