From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Winchell Subject: Re: RE: question about hvm vhpet Date: Fri, 21 Nov 2008 11:37:18 -0500 Message-ID: <4926E3BE.8000408@virtualiron.com> References: <147d5297-53e4-4b8e-848c-df8637f7dab1@default> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <147d5297-53e4-4b8e-848c-df8637f7dab1@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: "Tian, Kevin" , xen-devel@lists.xensource.com, Dave Winchell , Keir Fraser List-Id: xen-devel@lists.xenproject.org Dan Magenheimer wrote: >>vhpet is now based on vpt.c. >> >> > >Yes, understood. IIRC the main problem is that a new >timer mode is needed that guarantees that no two >ticks can be delivered too close together (and doesn't >ever care if they are delivered too far apart). >I think I had suggested the mode be called "no_fast_ticks". > >However, my memory may be faulty here, so I cc'ed Dave >hoping he would chime in. > >Dan > > Hi Dan, Keir, Kevin: Yes, I have not had the time to work on the hpet resubmission. I hope to be able to do so soon. Dan, the no_fast_ticks policy is one of the things that made our hpet implementation work well. Keir, thanks for doing the layering work. When I get back to working on this I'll start with what you have and characterize it. Then go from there. -Dave