From: Dave Winchell <dwinchell@virtualiron.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
xen-devel@lists.xensource.com,
Dave Winchell <dwinchell@virtualiron.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: RE: question about hvm vhpet
Date: Fri, 21 Nov 2008 11:37:18 -0500 [thread overview]
Message-ID: <4926E3BE.8000408@virtualiron.com> (raw)
In-Reply-To: <147d5297-53e4-4b8e-848c-df8637f7dab1@default>
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
prev parent reply other threads:[~2008-11-21 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 6:59 question about hvm vhpet Tian, Kevin
2008-11-21 8:10 ` Tian, Kevin
2008-11-21 9:02 ` Keir Fraser
2008-11-21 9:05 ` Tian, Kevin
2008-11-21 15:26 ` Dan Magenheimer
2008-11-21 15:32 ` Keir Fraser
2008-11-21 15:41 ` Dan Magenheimer
2008-11-21 16:37 ` Dave Winchell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4926E3BE.8000408@virtualiron.com \
--to=dwinchell@virtualiron.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.