From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49383) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMydO-0001VO-Gi for qemu-devel@nongnu.org; Thu, 19 May 2011 04:31:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMydN-0006ey-Gb for qemu-devel@nongnu.org; Thu, 19 May 2011 04:31:06 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:57512) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMydM-0006d2-SJ for qemu-devel@nongnu.org; Thu, 19 May 2011 04:31:05 -0400 Message-ID: <4DD4D53F.1090108@web.de> Date: Thu, 19 May 2011 10:30:55 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4DD3C5B9.1080908@redhat.com> <4DD3D236.90708@siemens.com> <4DD3D95E.2060105@redhat.com> <4DD3E1B3.3020405@siemens.com> <4DD3E610.1080201@siemens.com> <4DD4199E.2000702@codemonkey.ws> <4DD41DBB.2020108@web.de> <20110519082644.GC28399@redhat.com> In-Reply-To: <20110519082644.GC28399@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA9C6B7483452752027D5A912" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [RFC] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Peter Maydell , Avi Kivity , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA9C6B7483452752027D5A912 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-05-19 10:26, Gleb Natapov wrote: > On Wed, May 18, 2011 at 09:27:55PM +0200, Jan Kiszka wrote: >>> if an I/O is to the APIC page, >>> it's handled by the APIC >> >> That's not that simple. We need to tell apart: >> - if a cpu issued the request, and which one =3D> forward to APIC > And cpu mode may affect where access is forwarded to. If cpu is in SMM > mode access to frame buffer may be forwarded to a memory (depends on > chipset configuration). So we have a second use case for CPU-local I/O regions? I wonder if only a single CPU can enter SMM or if all have to. Right now only the first CPU can switch to that mode, and that affects the behaviour of the chipset /wrt SMRAM mapping. Is that another hack? Jan --------------enigA9C6B7483452752027D5A912 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.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3U1T8ACgkQitSsb3rl5xSCGQCfVqh/AMW4JTwzBxldccay6+XV CfcAoI1RkFmCmsixWvNFJvMAzVoeZ6Qg =IyCN -----END PGP SIGNATURE----- --------------enigA9C6B7483452752027D5A912--