From: Rik van Riel <riel@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
Daniel Walker <dwalker@mvista.com>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH 2/9] Sched clock paravirt op fix.patch
Date: Tue, 13 Mar 2007 12:37:53 -0400 [thread overview]
Message-ID: <45F6D361.8080106@redhat.com> (raw)
In-Reply-To: <20070313161656.GA12128@muc.de>
Andi Kleen wrote:
> On Tue, Mar 13, 2007 at 09:07:09AM -0700, Chris Wright wrote:
>> * Jeremy Fitzhardinge (jeremy@goop.org) wrote:
>>> In other words, regardless of whether this particular pv_op lives or
>>> dies, we're going to need to have to deal with stolen time properly. I
>>> think this hook is reasonable and useful step towards doing that.
>> Exactly. Normal interrupts we can handle. Having CPU completely
>> disappear for unkown time periods we can't, and will need to.
>
> But that is just what a interrupt is.
Interrupts tend to be reasonably short though.
Steal time can be several hypervisor/host time slices long.
As an aside, normal interrupts *are* accounted for separately
in /proc/stat, so why not steal time too?
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
next prev parent reply other threads:[~2007-03-13 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 2:54 [PATCH 2/9] Sched clock paravirt op fix.patch Zachary Amsden
2007-03-13 14:01 ` Andi Kleen
2007-03-13 15:26 ` Jeremy Fitzhardinge
2007-03-13 16:07 ` Chris Wright
2007-03-13 16:16 ` Andi Kleen
2007-03-13 16:37 ` Rik van Riel [this message]
2007-03-13 20:56 ` Andi Kleen
2007-03-13 21:05 ` Jeremy Fitzhardinge
2007-03-16 21:29 ` Matt Mackall
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=45F6D361.8080106@redhat.com \
--to=riel@redhat.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.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).