All of lore.kernel.org
 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,
	Rik van Riel <riel@redhat.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Eric B Munson <emunson@mgebm.net>
Subject: Re: [PATCH v2 3/7] KVM-HV: KVM Steal time implementation
Date: Sun, 19 Jun 2011 12:57:53 +0300	[thread overview]
Message-ID: <4DFDC821.2090905@redhat.com> (raw)
In-Reply-To: <1308262856-5779-4-git-send-email-glommer@redhat.com>

On 06/17/2011 01:20 AM, Glauber Costa wrote:
> To implement steal time, we need the hypervisor to pass the guest information
> about how much time was spent running other processes outside the VM.
> This is per-vcpu, and using the kvmclock structure for that is an abuse
> we decided not to make.
>
> In this patchset, I am introducing a new msr, KVM_MSR_STEAL_TIME, that
> holds the memory area address containing information about steal time
>
> This patch contains the hypervisor part for it. I am keeping it separate from
> the headers to facilitate backports to people who wants to backport the kernel
> part but not the hypervisor, or the other way around.
>
>
>
> +#define KVM_STEAL_ALIGNMENT_BITS 5
> +#define KVM_STEAL_VALID_BITS ((-1ULL<<  (KVM_STEAL_ALIGNMENT_BITS + 1)))
> +#define KVM_STEAL_RESERVED_MASK (((1<<  KVM_STEAL_ALIGNMENT_BITS) - 1 )<<  1)

Clumsy, but okay.

> +static void record_steal_time(struct kvm_vcpu *vcpu)
> +{
> +	u64 delta;
> +
> +	if (vcpu->arch.st.stime&&  vcpu->arch.st.this_time_out) {

0 is a valid value for stime.

> +
> +		if (unlikely(kvm_read_guest(vcpu->kvm, vcpu->arch.st.stime,
> +			&vcpu->arch.st.steal, sizeof(struct kvm_steal_time)))) {
> +
> +			vcpu->arch.st.stime = 0;
> +			return;
> +		}
> +
> +		delta = (get_kernel_ns() - vcpu->arch.st.this_time_out);
> +
> +		vcpu->arch.st.steal.steal += delta;
> +		vcpu->arch.st.steal.version += 2;
> +
> +		if (unlikely(kvm_write_guest(vcpu->kvm, vcpu->arch.st.stime,
> +			&vcpu->arch.st.steal, sizeof(struct kvm_steal_time)))) {
> +
> +			vcpu->arch.st.stime = 0;
> +			return;
> +		}
> +	}
> +
> +}
> +
>
> @@ -2158,6 +2206,8 @@ void kvm_arch_vcpu_load(struct kvm_vcpu *vcpu, int cpu)
>   			kvm_migrate_timers(vcpu);
>   		vcpu->cpu = cpu;
>   	}
> +
> +	record_steal_time(vcpu);
>   }

This records time spent in userspace in the vcpu thread as steal time.  
Is this what we want?  Or just time preempted away?


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


  parent reply	other threads:[~2011-06-19  9:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 22:20 [PATCH v2 0/7] Steal time for KVM Glauber Costa
2011-06-16 22:20 ` [PATCH v2 1/7] KVM-HDR Add constant to represent KVM MSRs enabled bit Glauber Costa
2011-06-17  0:47   ` Eric B Munson
2011-06-16 22:20 ` [PATCH v2 2/7] KVM-HDR: KVM Steal time implementation Glauber Costa
2011-06-17  0:48   ` Eric B Munson
2011-06-19  9:49   ` Avi Kivity
2011-06-20  2:55     ` Glauber Costa
2011-06-16 22:20 ` [PATCH v2 3/7] KVM-HV: " Glauber Costa
2011-06-17  0:48   ` Eric B Munson
2011-06-19  9:57   ` Avi Kivity [this message]
2011-06-20  2:53     ` Glauber Costa
2011-06-20  6:02       ` Avi Kivity
2011-06-20 20:56     ` Marcelo Tosatti
2011-06-28 12:30       ` Glauber Costa
2011-06-28 18:02         ` Marcelo Tosatti
2011-06-16 22:20 ` [PATCH v2 4/7] KVM-GST: Add a pv_ops stub for steal time Glauber Costa
2011-06-17  0:48   ` Eric B Munson
2011-06-16 22:20 ` [PATCH v2 5/7] KVM-GST: KVM Steal time accounting Glauber Costa
2011-06-17  0:48   ` Eric B Munson
2011-06-19 10:04   ` Avi Kivity
2011-06-20  2:38     ` Glauber Costa
2011-06-20  6:07       ` Avi Kivity
2011-06-16 22:20 ` [PATCH v2 6/7] KVM-GST: adjust scheduler cpu power Glauber Costa
2011-06-17  0:49   ` Eric B Munson
2011-06-19 10:05   ` Avi Kivity
2011-06-16 22:20 ` [PATCH v2 7/7] KVM-GST: KVM Steal time registration Glauber Costa
2011-06-17  0:49   ` Eric B Munson

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=4DFDC821.2090905@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=emunson@mgebm.net \
    --cc=glommer@redhat.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.