From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35760) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6IHM-0006O0-Op for qemu-devel@nongnu.org; Mon, 05 Aug 2013 06:44:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V6IHF-0004SS-Ep for qemu-devel@nongnu.org; Mon, 05 Aug 2013 06:44:44 -0400 Received: from mout.web.de ([212.227.15.14]:53874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6IHF-0004SE-5W for qemu-devel@nongnu.org; Mon, 05 Aug 2013 06:44:37 -0400 Received: from mchn199C.mchp.siemens.de ([95.157.58.223]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0LtCm3-1U3eB619id-012pQa for ; Mon, 05 Aug 2013 12:44:35 +0200 Message-ID: <51FF8211.3050509@web.de> Date: Mon, 05 Aug 2013 12:44:33 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <51FCBFCD.5020608@web.de> <51FF71BD.5040400@suse.de> <51FF7ED6.3050101@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GRwgTfGWmVfWOB7v4WW7C21l1a7X7mogl" Subject: Re: [Qemu-devel] [PATCH 1/2] memory: Provide separate handling of unassigned io ports accesses List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paolo Bonzini , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Aurelien Jarno , qemu-devel This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GRwgTfGWmVfWOB7v4WW7C21l1a7X7mogl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2013-08-05 12:36, Peter Maydell wrote: > On 5 August 2013 11:30, Jan Kiszka wrote: >> On 2013-08-05 11:59, Peter Maydell wrote: >>> Or do you mean that if we had: >>> >>> [ system memory region, with its own default read/write ops ] >> >> I cannot imagine how this could work. The system memory region has no >> clue about what the regions below it can handle and what not. So it ha= s >> to pass through the io window. >=20 > The system memory region's just a container, you can add a > background region to it at lowest-possible-priority, which > then takes accesses which are either (a) not in any subregion > or (b) in a subregion but that container doesn't specify > its own io ops and nothing in that container handles the > access. (Or you could create the system memory region with > its own IO ops, which would have the same effect.) First, we do not render MMIO and IO within the same address space so far. But even if we would, the IO container now catches all accesses, so the system memory region will never have its default handler run for that window. Jan --GRwgTfGWmVfWOB7v4WW7C21l1a7X7mogl 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlH/ghEACgkQitSsb3rl5xSyAACfVUNQF2giH4Rjj6aaxgHeRoym AsgAni0rCJUT/FGwOty071viREZmiWRe =pzdX -----END PGP SIGNATURE----- --GRwgTfGWmVfWOB7v4WW7C21l1a7X7mogl--