From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: windows acpi time drift
Date: Wed, 19 Mar 2008 17:39:51 +0200 [thread overview]
Message-ID: <47E133C7.1080607@qumranet.com> (raw)
In-Reply-To: <47E11EA7.5000405@codemonkey.ws>
Anthony Liguori wrote:
> Avi Kivity wrote:
>> The fourth is probably impossible from userspace (and very
>> difficult in the kernel).
>
> What makes it impossible to do in userspace? If you managed a
> tsc_offset in userspace, you would of course need to adjust that
> tsc_offset within the kernel for the particular PCPU that you were on.
>
In the kernel you can to tricks like local_irq_disable(); rdtsc();
ktime_get(); local_irq_enable() to get a sense where the tsc is.
Take a look at kvm_inject_pit_timer_irqs() and
kvm_pit_timer_intr_post(). An attempt to have a accurate userspace pit
needs to take into account what those functions do. I believe it's
doable, but will require careful design of the interface (which should
be usable for rtc and hpet as well).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-19 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 23:09 windows acpi time drift Dor Laor
2008-03-18 23:33 ` Dor Laor
2008-03-18 23:57 ` Anthony Liguori
2008-03-18 23:35 ` Anthony Liguori
2008-03-19 8:19 ` Avi Kivity
2008-03-19 14:09 ` Anthony Liguori
2008-03-19 15:39 ` Avi Kivity [this message]
2008-03-19 16:27 ` Dor Laor
2008-03-19 17:45 ` Avi Kivity
2008-03-19 0:07 ` Anthony Liguori
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=47E133C7.1080607@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=kvm-devel@lists.sourceforge.net \
/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.