public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: linux-kernel@vger.kernel.org, avi@qumranet.com,
	aliguori@us.ibm.com, kvm-devel@lists.sourceforge.net,
	hollisb@us.ibm.com
Subject: Re: include files for kvmclock
Date: Tue, 06 Nov 2007 14:50:07 -0800	[thread overview]
Message-ID: <4730EF9F.3020803@goop.org> (raw)
In-Reply-To: <11943875433821-git-send-email-gcosta@redhat.com>

Glauber de Oliveira Costa wrote:
> This patch introduces the include files for kvm clock.
> They'll be needed for both guest and host part.
>
> Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
> ---
>  include/asm-x86/kvm_para.h |   23 +++++++++++++++++++++++
>  include/linux/kvm.h        |    1 +
>  include/linux/kvm_para.h   |   20 ++++++++++++++++++++
>  3 files changed, 44 insertions(+), 0 deletions(-)
>
> diff --git a/include/asm-x86/kvm_para.h b/include/asm-x86/kvm_para.h
> index c6f3fd8..af9fb75 100644
> --- a/include/asm-x86/kvm_para.h
> +++ b/include/asm-x86/kvm_para.h
> @@ -10,15 +10,38 @@
>   * paravirtualization, the appropriate feature bit should be checked.
>   */
>  #define KVM_CPUID_FEATURES	0x40000001
> +#define KVM_FEATURE_CLOCKEVENTS 0
> +#define KVM_FEATURE_CLOCKSOURCE 1
> +
>  
>  #ifdef __KERNEL__
>  #include <asm/processor.h>
> +extern void kvmclock_init(void);
> +
> +union kvm_hv_clock {
>   

Why two copies of this structure?

> +	struct {
> +		u64 tsc_mult;
> +		u64 now_ns;
> +		/* That's the wall clock, not the water closet */
> +		u64 wc_sec;
> +		u64 wc_nsec;
> +		u64 last_tsc;
> +		/* At first, we could use the tsc value as a marker, but Jeremy
> +		 * well noted that it will cause us locking problems in 32-bit
> +		 * sys, so we have a special version field */
> +		u32 version;
> +	};
> +	char page_align[PAGE_SIZE];
> +};
> +
>   

[...]

> +
> +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;
> +		u64 last_tsc;
> +		/* At first, we could use the tsc value as a marker, but Jeremy
> +		 * well noted that it will cause us locking problems in 32-bit
> +		 * sys, so we have a special version field */
> +		u32 version;
> +	};
> +	char page_align[PAGE_SIZE];
> +};
> +
>  /*
>   * hypercalls use architecture specific
>   */
>   


  parent reply	other threads:[~2007-11-06 22:50 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
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   ` Jeremy Fitzhardinge [this message]
2007-11-06 22:58     ` include files for kvmclock 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=4730EF9F.3020803@goop.org \
    --to=jeremy@goop.org \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=gcosta@redhat.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