From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1INZb3-0005LU-5d for qemu-devel@nongnu.org; Tue, 21 Aug 2007 15:41:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1INZb1-0005J5-JX for qemu-devel@nongnu.org; Tue, 21 Aug 2007 15:41:00 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1INZb1-0005Iu-Ej for qemu-devel@nongnu.org; Tue, 21 Aug 2007 15:40:59 -0400 Received: from rv-out-0910.google.com ([209.85.198.191]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1INZb2-0005Wl-3t for qemu-devel@nongnu.org; Tue, 21 Aug 2007 15:41:00 -0400 Received: by rv-out-0910.google.com with SMTP id g11so4441632rvb for ; Tue, 21 Aug 2007 12:40:57 -0700 (PDT) Message-ID: <68676e00708211240k7237bf21k131257dd28063d26@mail.gmail.com> Date: Tue, 21 Aug 2007 21:40:57 +0200 From: Luca Subject: Re: [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer. In-Reply-To: <1187724245.2562.28.camel@fuego> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070817231149.544849769@gmail.com> <20070817231406.493008599@gmail.com> <1187724245.2562.28.camel@fuego> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Matthew Kent Cc: kvm-devel@lists.sf.net, qemu-devel@nongnu.org On 8/21/07, Matthew Kent 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 be able > > to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for 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 > > 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. It depends on your hardware. Theoretically it's possible, but I've yet to see a motherboard with more than one periodic timer. "dmesg | grep hpet" should tell you something like: hpet0: 3 64-bit timers, 14318180 Hz Luca