From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: [PATCH 0/2] Improve hpet accuracy Date: Fri, 13 Jun 2008 09:39:49 -0600 Message-ID: <20080613093949156.00000057128@djm-pc> References: Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , Dave Winchell , xen-devel Cc: Ben Guthro List-Id: xen-devel@lists.xenproject.org > I think apic=3D0 is not a particularly useful configuration = > though, right? We've seen it proposed sometimes as a workaround for a boot-time problem, but I agree its not useful enough to warrant concern or stand in the way of Dave's patch. > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: Friday, June 13, 2008 1:34 AM > To: dan.magenheimer@oracle.com; Dave Winchell; xen-devel > Cc: Ben Guthro > Subject: Re: [Xen-devel] [PATCH 0/2] Improve hpet accuracy > = > = > On 13/6/08 05:47, "Dan Magenheimer" = > wrote: > = > > I wondered what was different between apic=3D1 vs 0. Using: > > > > # cat /proc/interrupts | grep 'LOC|timer'; sleep 10; \ > > cat /proc/interrupts | grep 'LOC|timer' > > > > you can see that there are always 1000 LOC/sec. But > > with apic=3D1 there are also about 350 IO-APIC-edge-timer/sec > > and with apic=3D0 there are 1000 XT-PIC-timer/sec. > > > > I suspect that the latter of these (XT-PIC-timer) is > > messing up your policy and the former (edge-timer) is not. > = > I think apic=3D0 is not a particularly useful configuration = > though, right? > = > -- Keir > = > = >