From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Glauber de Oliveira Costa <glommer@gmail.com>,
Glauber de Oliveira Costa <gcosta@redhat.com>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
hollisb@us.ibm.com
Subject: Re: [kvm-devel] include files for kvmclock
Date: Tue, 06 Nov 2007 21:58:57 -0800 [thread overview]
Message-ID: <47315421.7080706@goop.org> (raw)
In-Reply-To: <4731535E.5000808@qumranet.com>
Avi Kivity wrote:
> Glauber de Oliveira Costa wrote:
>
>>> +union kvm_hv_clock {
>>> + struct {
>>> + u64 tsc_mult;
>>> + u64 now_ns;
>>> + /* That's the wall clock, not the water closet */
>>> + u64 wc_sec;
>>> + u64 wc_nsec;
>>>
>>>
>
> Do we really need 128-bit time? you must be planning to live forever.
>
Well, he's planning on having lots of very small nanoseconds.
J
next prev parent reply other threads:[~2007-11-07 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 22:18 KVM paravirt clocksource - Take 3 out of <put your number here> Glauber de Oliveira Costa
2007-11-06 22:18 ` include files for kvmclock Glauber de Oliveira Costa
2007-11-06 21:35 ` [kvm-devel] " Glauber de Oliveira Costa
2007-11-07 5:55 ` Avi Kivity
2007-11-07 5:58 ` Jeremy Fitzhardinge [this message]
2007-11-07 12:49 ` Glauber de Oliveira Costa
2007-11-06 22:18 ` kvmclock - the host part Glauber de Oliveira Costa
2007-11-06 22:18 ` kvmclock implementation, the guest part Glauber de Oliveira Costa
2007-11-07 5:50 ` kvmclock - the host part Avi Kivity
2007-11-07 13:08 ` Glauber de Oliveira Costa
2007-11-07 13:59 ` Avi Kivity
2007-11-06 22:50 ` include files for kvmclock Jeremy Fitzhardinge
2007-11-06 22:58 ` Glauber de Oliveira Costa
2007-11-07 8:16 ` [kvm-devel] " Akio Takebe
2007-11-07 13:16 ` Glauber de Oliveira Costa
2007-11-07 13:27 ` Akio Takebe
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=47315421.7080706@goop.org \
--to=jeremy@goop.org \
--cc=avi@qumranet.com \
--cc=gcosta@redhat.com \
--cc=glommer@gmail.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox