public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Avi Kivity <avi@qumranet.com>,
	Glauber de Oliveira Costa <glommer@gmail.com>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	hollisb@us.ibm.com
Subject: Re: [kvm-devel] include files for kvmclock
Date: Wed, 07 Nov 2007 10:49:35 -0200	[thread overview]
Message-ID: <4731B45F.20300@redhat.com> (raw)
In-Reply-To: <47315421.7080706@goop.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeremy Fitzhardinge escreveu:
> 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
The wc_nsec is legacy, and should be gone. It's not really used in
current code. However, you gave me a very good idea. Living forever
would be awesome! Where can I apply ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org

iD8DBQFHMbRfjYI8LaFUWXMRAjsQAJ4vDBW0M48fMaL9sl6XfN0+Pd82egCgutwe
9rR7+H8MUQznyinlJc76kbo=
=b3wx
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-11-07 12:49 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
2007-11-07 12:49         ` Glauber de Oliveira Costa [this message]
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=4731B45F.20300@redhat.com \
    --to=gcosta@redhat.com \
    --cc=avi@qumranet.com \
    --cc=glommer@gmail.com \
    --cc=hollisb@us.ibm.com \
    --cc=jeremy@goop.org \
    --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