From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Glauber de Oliveira Costa
<glommer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
jeremy-TSDbQ3PG+2Y@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
Glauber de Oliveira Costa
<gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: include files for kvmclock
Date: Wed, 07 Nov 2007 07:55:42 +0200 [thread overview]
Message-ID: <4731535E.5000808@qumranet.com> (raw)
In-Reply-To: <5d6222a80711061335q7ef03b42i335bb1e8c07eb7e4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-11-07 5:55 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
[not found] ` <11943875362987-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-11-06 22:18 ` include files for kvmclock Glauber de Oliveira Costa
[not found] ` <11943875433821-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-11-06 21:35 ` Glauber de Oliveira Costa
[not found] ` <5d6222a80711061335q7ef03b42i335bb1e8c07eb7e4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-07 5:55 ` Avi Kivity [this message]
[not found] ` <4731535E.5000808-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-07 5:58 ` Jeremy Fitzhardinge
[not found] ` <47315421.7080706-TSDbQ3PG+2Y@public.gmane.org>
2007-11-07 12:49 ` Glauber de Oliveira Costa
2007-11-06 22:18 ` kvmclock - the host part Glauber de Oliveira Costa
[not found] ` <11943875471622-git-send-email-gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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
[not found] ` <47315229.1010502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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
[not found] ` <4730EF9F.3020803-TSDbQ3PG+2Y@public.gmane.org>
2007-11-06 22:58 ` Glauber de Oliveira Costa
2007-11-07 8:16 ` Akio Takebe
[not found] ` <1DC8211684B62Btakebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-07 13:16 ` Glauber de Oliveira Costa
[not found] ` <4731BAB2.9040004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
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=4731535E.5000808@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=glommer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=jeremy-TSDbQ3PG+2Y@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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