All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Zachary Amsden <zach@vmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21
Date: 6 Feb 2007 13:25:14 +0100
Date: Tue, 6 Feb 2007 13:25:14 +0100	[thread overview]
Message-ID: <20070206122514.GA47229@muc.de> (raw)
In-Reply-To: <1170752856.7324.5.camel@laptopd505.fenrus.org>

> hmm stolen time could even be useful without virtualization; to a large
> degree, if cpufreq reduces the speed of your cpu you have "stolen
> cycles" that way... I wonder if this concept can be used for that as
> well...

If you mean it for the real time clock: Doesn't make sense then 
because Linux time isn't measured in cycles

If you mean it for the scheduler: it only uses estimates for
relative fairness. As long as everybody is sloeed down in the same
way the relative fairness doesn't change.

For time accounting: the regular timer interrupt is fairly imprecise
anyawys because it samples at a low frequency. While it would be possible to 
improve this it would be quite costly by slowing down interrupts and syscalls.
I'm not sure it makes that much difference here either.

I don't see the point, frankly.

-Andi

  parent reply	other threads:[~2007-02-06 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  3:52 [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21 Zachary Amsden
2007-02-06  4:27 ` Rusty Russell
2007-02-06  4:54   ` Zachary Amsden
2007-02-06  5:11     ` Rusty Russell
2007-02-06  5:24       ` Stephen Rothwell
2007-02-06  9:07       ` Arjan van de Ven
2007-02-06  9:25         ` Zachary Amsden
2007-02-06 12:25         ` Andi Kleen [this message]
2007-02-06 12:45           ` Arjan van de Ven
2007-02-06 18:16             ` Andi Kleen
2007-02-13 22:39           ` Rik van Riel

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=20070206122514.GA47229@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zach@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.