LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 2/11] Sched clock paravirt op
Date: Tue, 06 Feb 2007 15:42:18 -0800 [thread overview]
Message-ID: <45C9125A.3040704@vmware.com> (raw)
In-Reply-To: <45C90DDA.3060009@goop.org>
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>
>> Scheduled (or available) time and real time are good notions. Stolen
>> time is debatable. But TSC is basically just always wrong. That's
>> why I don't want to overload the rdtsc operation.
>>
> Well, in the Xen case it is actually guaranteed to be correct and useful
> as real time, but that's definitely not something we can expect in
> general. But you're talking specifically about schedulable vcpu time
> here, right?
>
Not schedulable time, scheduled time (schedulable - scheduled) = stolen
Zach
next prev parent reply other threads:[~2007-02-06 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:52 [PATCH 2/11] Sched clock paravirt op Zachary Amsden
2007-02-06 4:00 ` Zachary Amsden
2007-02-06 12:32 ` Andi Kleen
2007-02-06 22:47 ` Zachary Amsden
2007-02-06 23:23 ` Jeremy Fitzhardinge
2007-02-06 23:42 ` Zachary Amsden [this message]
2007-02-06 23:48 ` Jeremy Fitzhardinge
2007-02-06 23:50 ` Zachary Amsden
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=45C9125A.3040704@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).