From: Michael Wolf <mjw@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, peterz@infradead.org, mtosatti@redhat.com,
glommer@parallels.com, mingo@redhat.com, avi@redhat.com,
anthony@codemonkey.ws
Subject: [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time.
Date: Tue, 16 Oct 2012 21:23:45 -0500 [thread overview]
Message-ID: <20121017022249.16949.2775.stgit@lambeau> (raw)
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. 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.
TODO:
* Change native_clock to take params and not return a value
* Change update_rq_clock_task
Changes from V1:
* Removed the steal time allowed percentage from the guest
* Moved the separation of consigned (expected steal) and steal time to the
host.
* No longer include a sysctl interface.
---
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/kernel/kvm.c | 8 ++----
arch/x86/kvm/x86.c | 50 ++++++++++++++++++++++++++++++++++++++-
fs/proc/stat.c | 9 +++++--
include/linux/kernel_stat.h | 2 ++
include/linux/kvm.h | 2 ++
include/linux/kvm_host.h | 2 ++
kernel/sched/cputime.c | 21 +++++++++++++++-
kernel/sched/sched.h | 2 ++
virt/kvm/kvm_main.c | 7 +++++
12 files changed, 108 insertions(+), 13 deletions(-)
next reply other threads:[~2012-10-17 2:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 2:23 Michael Wolf [this message]
2012-10-17 2:24 ` [PATCH RFC V2 1/5] Alter the amount of steal time reported by the guest Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 2/5] Expand the steal time msr to also contain the consigned time Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 3/5] Add the code to send the consigned time from the host to the guest Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 4/5] Add a timer to allow the separation of consigned from steal time Michael Wolf
2012-10-17 2:24 ` [PATCH RFC V2 5/5] Add an ioctl to communicate the consign limit to the host Michael Wolf
2012-10-17 17:14 ` [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time Glauber Costa
2012-10-17 15:13 ` Michael Wolf
2012-10-22 15:33 ` Rik van Riel
2012-11-26 20:00 ` 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=20121017022249.16949.2775.stgit@lambeau \
--to=mjw@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.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 \
/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).