From: Arjan van de Ven <arjan@infradead.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Zachary Amsden <zach@vmware.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21
Date: Tue, 06 Feb 2007 10:07:36 +0100 [thread overview]
Message-ID: <1170752856.7324.5.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1170738676.29293.35.camel@localhost.localdomain>
On Tue, 2007-02-06 at 16:11 +1100, Rusty Russell wrote:
> On Mon, 2007-02-05 at 20:54 -0800, Zachary Amsden wrote:
> > Rusty Russell wrote:
> > > Indeed, I'm expecting to push lguest this week, and this code will
> > > effect me, so I'd like to see this in a -mm soon...
> >
> > Yes, I took a look at the lguest changes today and I think these won't
> > generate conflicts, just make stuff easier for you ;) Course you've now
> > got a couple new paravirt-ops to support, but the native ones are fine
> > for temporary use.
>
> Implementing stolen time is something I'd like to do, since it'd be a
> nice self-contained example the expectations.
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...
next prev parent reply other threads:[~2007-02-06 9:08 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 [this message]
2007-02-06 9:25 ` Zachary Amsden
2007-02-06 12:25 ` Andi Kleen
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=1170752856.7324.5.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--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 \
--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.