From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O63QS-00087S-45 for qemu-devel@nongnu.org; Sun, 25 Apr 2010 11:07:16 -0400 Received: from [140.186.70.92] (port=41021 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O63QQ-00085u-Ma for qemu-devel@nongnu.org; Sun, 25 Apr 2010 11:07:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O63QO-0003uS-GH for qemu-devel@nongnu.org; Sun, 25 Apr 2010 11:07:14 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:49430) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O63QO-0003uH-47 for qemu-devel@nongnu.org; Sun, 25 Apr 2010 11:07:12 -0400 Message-ID: <4BD45A96.3080800@web.de> Date: Sun, 25 Apr 2010 17:07:02 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20100423170410.914857113@amt.cnet> <20100423170645.675040544@amt.cnet> <4BD29F22.8020806@web.de> <4BD4367F.5060307@redhat.com> <4BD44A4D.4060008@web.de> <4BD44F13.3070000@redhat.com> <4BD451D9.4090209@web.de> <4BD4547C.5060907@redhat.com> <4BD45709.9070705@web.de> <4BD458AD.9020500@redhat.com> In-Reply-To: <4BD458AD.9020500@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA82AD8129B4CB19A3F074590" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [uq/master patch 2/5] kvm: add logging count to slots List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA82AD8129B4CB19A3F074590 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > On 04/25/2010 05:51 PM, Jan Kiszka wrote: >> Avi Kivity wrote: >> =20 >>> On 04/25/2010 05:29 PM, Jan Kiszka wrote: >>> =20 >>>> =20 >>>>> There isn't. But I don't like hidden breakage. >>>>> >>>>> =20 >>>> It's (so far) an unproblematic API property we can document. I don't= >>>> like changing APIs just for "there might be the case that...". >>>> >>>> =20 >>> I guess it's one of those agree to disagree things. I dislike known >>> broken APIs even if their none of their users are affected. >>> =20 >> The API is not broken. I intentionally designed it for the single user= >> as I saw no need for more. If I oversaw something, I would really like= >> to learn about these cases. >> =20 >=20 > The fact that the API assumes a single user is what's broken IMO. >=20 > If the API were to take a memory slot as parameter you could say it is > the responsibility of the slot's owner to multiplex (and since vga has = a > single owner, no need to multiplex). But it takes a range. No, the API accepts only a single slot. If you try passing bogus ranges that span multiple or incomplete slots, you get what you deserve - a bug message. Jan --------------enigA82AD8129B4CB19A3F074590 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.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkvUWp0ACgkQitSsb3rl5xQqpQCgyrzAFUAv8/WGeILSKdlrQx89 NaEAn2XbzdVZVpsdylPkSZ9x/1cQto6Z =7kYq -----END PGP SIGNATURE----- --------------enigA82AD8129B4CB19A3F074590--