From: Michael Wolf <mjw@linux.vnet.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com,
kvm@vger.kernel.org, peterz@infradead.org, glommer@parallels.com,
mingo@redhat.com
Subject: Re: [PATCH 0/5] Alter steal time reporting in KVM
Date: Wed, 28 Nov 2012 12:43:22 -0600 [thread overview]
Message-ID: <50B65B4A.50508@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121127232442.GA8295@amt.cnet>
On 11/27/2012 05:24 PM, Marcelo Tosatti wrote:
> On Mon, Nov 26, 2012 at 02:36:24PM -0600, Michael Wolf wrote:
>> In the case of where you have a system that is running in a
>> capped or overcommitted environment the user may see steal time
>> being reported in accounting tools such as top or vmstat.
> The definition of stolen time is 'time during which the virtual CPU is
> runnable to not running'. Overcommit is the main scenario which steal
> time helps to detect.
>
> Can you describe the 'capped' case?
In the capped case, the time that the guest spends waiting due to it
having used its full allottment of time shows up as steal time. The way
my patchset currently stands is that you would set up the
bandwidth control and you would have to pass it a matching value from
qemu. In the future, it would
be possible to have something parse the bandwidth setting and
automatically adjust the setting in the
host used for steal time reporting.
>
>> This can
>> cause confusion for the end user. To ease the confusion this patch set
>> adds the idea of consigned (expected steal) time. The host will separate
>> the consigned time from the steal time. The consignment limit passed to the
>> host will be the amount of steal time expected within a fixed period of
>> time. Any other steal time accruing during that period will show as the
>> traditional steal time.
>>
>> ---
>>
>> Michael Wolf (5):
>> Alter the amount of steal time reported by the guest.
>> Expand the steal time msr to also contain the consigned time.
>> Add the code to send the consigned time from the host to the guest
>> Add a timer to allow the separation of consigned from steal time.
>> Add an ioctl to communicate the consign limit to the host.
>>
>>
>> arch/x86/include/asm/kvm_host.h | 11 +++++++
>> arch/x86/include/asm/kvm_para.h | 3 +-
>> arch/x86/include/asm/paravirt.h | 4 +--
>> arch/x86/include/asm/paravirt_types.h | 2 +
>> arch/x86/kernel/kvm.c | 8 ++---
>> arch/x86/kernel/paravirt.c | 4 +--
>> arch/x86/kvm/x86.c | 50 ++++++++++++++++++++++++++++++++-
>> fs/proc/stat.c | 9 +++++-
>> include/linux/kernel_stat.h | 2 +
>> include/linux/kvm_host.h | 2 +
>> include/uapi/linux/kvm.h | 2 +
>> kernel/sched/core.c | 10 ++++++-
>> kernel/sched/cputime.c | 21 +++++++++++++-
>> kernel/sched/sched.h | 2 +
>> virt/kvm/kvm_main.c | 7 +++++
>> 15 files changed, 120 insertions(+), 17 deletions(-)
>>
>> --
>> Signature
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-28 18:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 20:36 [PATCH 0/5] Alter steal time reporting in KVM Michael Wolf
2012-11-26 20:36 ` [PATCH 1/5] Alter the amount of steal time reported by the guest Michael Wolf
2012-11-26 20:36 ` [PATCH 2/5] Expand the steal time msr to also contain the consigned time Michael Wolf
2012-11-27 21:03 ` Konrad Rzeszutek Wilk
2012-11-28 15:23 ` Michael Wolf
2012-11-26 20:36 ` [PATCH 3/5] Add the code to send the consigned time from the host to the guest Michael Wolf
2012-11-26 20:37 ` [PATCH 4/5] Add a timer to allow the separation of consigned from steal time Michael Wolf
2012-11-26 20:37 ` [PATCH 5/5] Add an ioctl to communicate the consign limit to the host Michael Wolf
2012-11-27 8:48 ` [PATCH 0/5] Alter steal time reporting in KVM Glauber Costa
2012-11-27 15:10 ` Michael Wolf
2012-11-28 8:45 ` Glauber Costa
2012-11-28 18:44 ` Michael Wolf
2012-11-28 19:16 ` Anthony Liguori
2012-11-27 23:24 ` Marcelo Tosatti
2012-11-28 0:32 ` Marcelo Tosatti
2012-11-28 18:43 ` Michael Wolf [this message]
2012-11-28 20:55 ` Glauber Costa
2012-11-29 17:43 ` Michael Wolf
2012-12-05 12:46 ` Glauber Costa
2012-12-07 15:50 ` Michael Wolf
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=50B65B4A.50508@linux.vnet.ibm.com \
--to=mjw@linux.vnet.ibm.com \
--cc=glommer@parallels.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--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 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).