From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=38673 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOnVF-0000ok-5H for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:57:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OOnVE-0007Yu-23 for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:57:41 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:59605) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OOnVD-0007YW-Lk for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:57:40 -0400 Message-ID: <4C1883EF.10109@web.de> Date: Wed, 16 Jun 2010 09:57:35 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4C18015C.1070306@web.de> <20100616044047.GF13238@redhat.com> <4C187725.2000902@web.de> <20100616073318.GZ21797@redhat.com> <4C188272.9010201@web.de> <20100616075259.GA21797@redhat.com> In-Reply-To: <20100616075259.GA21797@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEC9ABE68C8BD93B0926ADA7D" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [PATCH] hpet: Clean up initial hpet counter List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEC9ABE68C8BD93B0926ADA7D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Gleb Natapov wrote: > On Wed, Jun 16, 2010 at 09:51:14AM +0200, Jan Kiszka wrote: >> Gleb Natapov wrote: >>> On Wed, Jun 16, 2010 at 09:03:01AM +0200, Jan Kiszka wrote: >>>> Gleb Natapov wrote: >>>>> On Wed, Jun 16, 2010 at 12:40:28AM +0200, Jan Kiszka wrote: >>>>>> From: Jan Kiszka >>>>>> >>>>>> There is no need starting with the special value for hpet_cfg.coun= t. >>>>>> Either Seabios is aware of the new firmware interface and properly= >>>>>> interprets the counter or it simply ignores it anyway. >>>>>> >>>>> I want seabios to be able to distinguish between old qemu and new o= ne. >>>> I see now. But isn't it a good chance to introduce a proper generic >>>> interface for exploring supported fw-cfg keys? >>>> >>> Having such interface would be nice. Pity we haven't introduced it fr= om >>> the start. If we do it now seabios will have to find out somehow that= >>> qemu support such interface. Chicken and egg ;) >> That is easy: Add a key the describes the highest supported key value >> (looks like this is monotonously increasing). Older qemu versions will= >> return 0. >> > That will not support holes in key space, and our key space is already > sparse. Then add a service to obtain a bitmap of supported keys. If that bitmap is empty... Jan --------------enigEC9ABE68C8BD93B0926ADA7D 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 iEYEARECAAYFAkwYg+8ACgkQitSsb3rl5xSCOgCgo5qvMWZxIURlP7ysoRQr3JNy RgQAnjN/WMV82lTFhga71u6WMYogQkDa =cKKz -----END PGP SIGNATURE----- --------------enigEC9ABE68C8BD93B0926ADA7D--