linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	zamsden@redhat.com, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH v2 1/7] Enable pvclock flags in vcpu_time_info structure
Date: Wed, 05 May 2010 11:29:12 +0300	[thread overview]
Message-ID: <4BE12C58.6040101@redhat.com> (raw)
In-Reply-To: <1272901927-829-2-git-send-email-glommer@redhat.com>

On 05/03/2010 06:52 PM, Glauber Costa wrote:
> This patch removes one padding byte and transform it into a flags
> field. New versions of guests using pvclock will query these flags
> upon each read.
>
> Flags, however, will only be interpreted when the guest decides to.
> It uses the pvclock_valid_flags function to signal that a specific
> set of flags should be taken into consideration. Which flags are valid
> are usually devised via HV negotiation.
>
> Signed-off-by: Glauber Costa<glommer@redhat.com>
> CC: Jeremy Fitzhardinge<jeremy@goop.org>
> ---
>   arch/x86/include/asm/pvclock-abi.h |    3 ++-
>   arch/x86/include/asm/pvclock.h     |    1 +
>   arch/x86/kernel/pvclock.c          |    9 +++++++++
>   3 files changed, 12 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/include/asm/pvclock-abi.h b/arch/x86/include/asm/pvclock-abi.h
> index 6d93508..ec5c41a 100644
> --- a/arch/x86/include/asm/pvclock-abi.h
> +++ b/arch/x86/include/asm/pvclock-abi.h
> @@ -29,7 +29,8 @@ struct pvclock_vcpu_time_info {
>   	u64   system_time;
>   	u32   tsc_to_system_mul;
>   	s8    tsc_shift;
> -	u8    pad[3];
> +	u8    flags;
> +	u8    pad[2];
>   } __attribute__((__packed__)); /* 32 bytes */
>
>   struct pvclock_wall_clock {
> diff --git a/arch/x86/include/asm/pvclock.h b/arch/x86/include/asm/pvclock.h
> index 53235fd..cd02f32 100644
> --- a/arch/x86/include/asm/pvclock.h
> +++ b/arch/x86/include/asm/pvclock.h
> @@ -6,6 +6,7 @@
>
>   /* some helper functions for xen and kvm pv clock sources */
>   cycle_t pvclock_clocksource_read(struct pvclock_vcpu_time_info *src);
> +void pvclock_set_flags(u8 flags);
>   unsigned long pvclock_tsc_khz(struct pvclock_vcpu_time_info *src);
>   void pvclock_read_wallclock(struct pvclock_wall_clock *wall,
>   			    struct pvclock_vcpu_time_info *vcpu,
> diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
> index 03801f2..aa2262b 100644
> --- a/arch/x86/kernel/pvclock.c
> +++ b/arch/x86/kernel/pvclock.c
> @@ -31,8 +31,16 @@ struct pvclock_shadow_time {
>   	u32 tsc_to_nsec_mul;
>   	int tsc_shift;
>   	u32 version;
> +	u8  flags;
>   };
>
> +static u8 valid_flags = 0;
> +
>    

Minor optimization: __read_mostly.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-05-05  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 15:52 [PATCH v2 0/7] Pvclock fixes , version two Glauber Costa
2010-05-03 15:52 ` [PATCH v2 1/7] Enable pvclock flags in vcpu_time_info structure Glauber Costa
2010-05-03 15:52   ` [PATCH v2 2/7] Add a global synchronization point for pvclock Glauber Costa
2010-05-03 15:52     ` [PATCH v2 3/7] change msr numbers for kvmclock Glauber Costa
2010-05-03 15:52       ` [PATCH v2 4/7] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Glauber Costa
2010-05-03 15:52         ` [PATCH v2 5/7] Try using new kvm clock msrs Glauber Costa
2010-05-03 15:52           ` [PATCH v2 6/7] don't compute pvclock adjustments if we trust the tsc Glauber Costa
2010-05-03 15:52             ` [PATCH v2 7/7] Tell the guest we'll warn it about tsc stability Glauber Costa
2010-05-05  8:28             ` [PATCH v2 6/7] don't compute pvclock adjustments if we trust the tsc Avi Kivity
2010-05-05  8:23         ` [PATCH v2 4/7] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Avi Kivity
2010-05-05  8:29   ` Avi Kivity [this message]
2010-05-05  3:57 ` [PATCH v2 0/7] Pvclock fixes , version two Zachary Amsden

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=4BE12C58.6040101@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=jeremy@goop.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zamsden@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).