From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QO6Hi-0000hi-QS for qemu-devel@nongnu.org; Sun, 22 May 2011 06:53:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QO6Hh-0002NM-RO for qemu-devel@nongnu.org; Sun, 22 May 2011 06:53:22 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:42602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QO6Hh-0002N0-E2 for qemu-devel@nongnu.org; Sun, 22 May 2011 06:53:21 -0400 Message-ID: <4DD8EB14.8050305@web.de> Date: Sun, 22 May 2011 12:53:08 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20110519182203.GH27310@redhat.com> <4DD56126.20808@web.de> <20110519184056.GJ27310@redhat.com> <4DD56543.9020404@web.de> <20110519185019.GK27310@redhat.com> <4DD567B5.1060205@web.de> <20110520072358.GL27310@redhat.com> <4DD61ADD.9050103@web.de> <20110520112534.GM27310@redhat.com> <4DD8C03E.3020904@redhat.com> <20110522084142.GS27310@redhat.com> In-Reply-To: <20110522084142.GS27310@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4FF4538118E8DBF227699427" 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: Avi Kivity , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4FF4538118E8DBF227699427 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-05-22 10:41, Gleb Natapov wrote: >> The chipset knows about the priorities. How to communicate them to >> the core? >> >> - at runtime, with hierarchical dispatch of ->read() and ->write(): >> slow, and doesn't work at all for RAM. >> - using registration order: fragile >> - using priorities >> > - by resolving overlapping and registering flattened list with the core= =2E > (See example above). [Registration would happens with the help of the core against the next higher layer.] To do this, you need to - open-code the resolution logic at every level (very bad idea) - provide library services to obtain a flattened representation Please try to specify such an API without any parameters that are priority-like. Jan --------------enig4FF4538118E8DBF227699427 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/ iEYEARECAAYFAk3Y6xcACgkQitSsb3rl5xRMNwCfeR3QaPJm/HLAKhLvm3hDXde6 gyEAoJB1BzuO2T5PuvzYcMBspvZUCC4g =yIcD -----END PGP SIGNATURE----- --------------enig4FF4538118E8DBF227699427--