From: Glauber Costa <glommer@parallels.com>
To: Michael Wolf <mjw@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<peterz@infradead.org>, <mtosatti@redhat.com>, <mingo@redhat.com>,
<avi@redhat.com>
Subject: Re: [PATCH RFC 0/3] Add guest cpu_entitlement reporting
Date: Fri, 24 Aug 2012 08:53:28 +0400 [thread overview]
Message-ID: <503708C8.2090401@parallels.com> (raw)
In-Reply-To: <20120823231346.11681.1502.stgit@lambeau>
On 08/24/2012 03:14 AM, Michael Wolf wrote:
> This is an RFC regarding the reporting of stealtime. In the case of
> where you have a system that is running with partial processors such as
> KVM 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 a sysctl interface to set the
> cpu entitlement. This is the percentage of cpu that the guest system is
> expected to receive. As long as the steal time is within its expected
> range it will show up as 0 in /proc/stat. The user will then see in the
> accounting tools that they are getting a full utilization of the cpu
> resources assigned to them.
>
And how is such a knob not confusing?
Steal time is pretty well defined in meaning and is shown in top for
ages. I really don't see the point for this.
next prev parent reply other threads:[~2012-08-24 4:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 23:14 Michael Wolf
2012-08-23 23:14 ` [PATCH RFC 1/3] Add a sysctl interface to control and report the cpu entitlement setting Michael Wolf
2012-08-23 23:14 ` [PATCH RFC 2/3] Add a hypercall to retrieve the cpu entitlement value from the host Michael Wolf
2012-08-23 23:14 ` [PATCH RFC 3/3] Modify the amount of stealtime that the kernel reports via the /proc interface Michael Wolf
2012-08-24 4:53 ` Glauber Costa [this message]
2012-08-24 15:11 ` [PATCH RFC 0/3] Add guest cpu_entitlement reporting Michael Wolf
2012-08-25 23:36 ` Glauber Costa
2012-08-27 15:50 ` Michael Wolf
2012-08-27 18:50 ` Glauber Costa
2012-08-27 20:19 ` Michael Wolf
2012-08-27 20:51 ` Glauber Costa
2012-08-27 18:55 ` Avi Kivity
2012-08-27 20:23 ` Michael Wolf
2012-08-27 20:31 ` Avi Kivity
2012-08-27 21:27 ` Michael Wolf
2012-08-27 21:41 ` Glauber Costa
2012-08-27 21:53 ` Michael Wolf
2012-08-27 21:52 ` Avi Kivity
2012-08-28 16:01 ` Anthony Liguori
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=503708C8.2090401@parallels.com \
--to=glommer@parallels.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjw@linux.vnet.ibm.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
Powered by JetHome