From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IS7VH-0001Rr-Q1
	for qemu-devel@nongnu.org; Mon, 03 Sep 2007 04:41:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IS7VG-0001RU-Py
	for qemu-devel@nongnu.org; Mon, 03 Sep 2007 04:41:50 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IS7VG-0001RO-Ez
	for qemu-devel@nongnu.org; Mon, 03 Sep 2007 04:41:50 -0400
Received: from mail-out.criltechnology.com ([195.115.177.11]
	helo=criltechnology.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <francois.guerraz@alyotech.fr>) id 1IS7VG-0006kY-2W
	for qemu-devel@nongnu.org; Mon, 03 Sep 2007 04:41:50 -0400
Received: from cril01.criltechnology.net by criltechnology.com
	(MDaemon PRO v9.6.0) with ESMTP id md50000129487.msg
	for <qemu-devel@nongnu.org>; Mon, 03 Sep 2007 10:40:05 +0200
Subject: Re: [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer.
From: GUERRAZ Francois <francois.guerraz@alyotech.fr>
In-Reply-To: <68676e00708211240k7237bf21k131257dd28063d26@mail.gmail.com>
References: <20070817231149.544849769@gmail.com>
	<20070817231406.493008599@gmail.com> <1187724245.2562.28.camel@fuego>
	<68676e00708211240k7237bf21k131257dd28063d26@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Mon, 03 Sep 2007 10:40:04 +0200
Message-Id: <1188808804.6468.13.camel@BODDINGTONX.criltechnology.net>
Mime-Version: 1.0
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hello,

Can you confirm to me that if I have only one periodic timer on my
motherboard I can only have one qemu-instance running using hpet?

Thanks.

Fran=C3=A7ois.

Le mardi 21 ao=C3=BBt 2007 =C3=A0 21:40 +0200, Luca a =C3=A9crit :
> On 8/21/07, Matthew Kent <mkent@magoazul.com> wrote:
> > On Sat, 2007-18-08 at 01:11 +0200, Luca Tettamanti wrote:
> > > plain text document attachment (clock-hpet)
> > > Linux operates the HPET timer in legacy replacement mode, which means=
 that
> > > the periodic interrupt of the CMOS RTC is not delivered (qemu won't b=
e able
> > > to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement f=
or the
> > > RTC; the periodic interrupt is delivered via SIGIO and is handled in =
the
> > > same way as the RTC timer.
> > >
> > > Signed-off-by: Luca Tettamanti <kronos.it@gmail.com>
> >
> > I must be missing something silly here.. should I be able to open more
> > than one instance of qemu with -clock hpet? Because upon invoking a
> > second instance of qemu HPET_IE_ON fails.
>=20
> It depends on your hardware. Theoretically it's possible, but I've yet
> to see a motherboard with more than one periodic timer.
>=20
> "dmesg | grep hpet" should tell you something like:
>=20
> hpet0: 3 64-bit timers, 14318180 Hz
>=20
> Luca
>=20
>=20
>=20