From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v2 5/5] hpet 'driftfix': add code in hpet_timer() to compensate delayed callbacks and coalesced interrupts Date: Fri, 08 Apr 2011 18:12:32 +0200 Message-ID: <4D9F33F0.9010902@siemens.com> References: <1302276042-3497-1-git-send-email-uobergfe@redhat.com> <1302276042-3497-6-git-send-email-uobergfe@redhat.com> <4D9F2FCC.2070708@siemens.com> <1302278924.3021.10.camel@mothafucka.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Ulrich Obergfell , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , "gcosta@redhat.com" , "avi@redhat.com" , "aliguori@us.ibm.com" To: Glauber Costa Return-path: Received: from david.siemens.de ([192.35.17.14]:25480 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752680Ab1DHQMn (ORCPT ); Fri, 8 Apr 2011 12:12:43 -0400 In-Reply-To: <1302278924.3021.10.camel@mothafucka.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-04-08 18:08, Glauber Costa wrote: > On Fri, 2011-04-08 at 17:54 +0200, Jan Kiszka wrote: >>> + } >> >> Did I miss some change in the plan? I thought we were heading for a >> generic, reusable driftfix tool box (or periodic timer service)? Or is >> this intentionally an intermediate step? > > Which is a medium to long way in the future. There is benefit of having > this early, since it can deliver real functionality - a reliable hpet, > and converting to whatever the api may look like in the future. > Well, if the PIT and the RTC should use it as well, which is probably rather a short term goal, we already have two more users. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux