From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt repo rebased to 2.6.21-rc6-mm1
Date: Thu, 12 Apr 2007 08:40:44 -0700 [thread overview]
Message-ID: <461E52FC.7070001@vmware.com> (raw)
In-Reply-To: <20070412085430.GD10574@sequoia.sous-sol.org>
Chris Wright wrote:
> * Jeremy Fitzhardinge (jeremy@goop.org) wrote:
>
>> Seems to work OK for native and Xen. I had to play a bit with the
>> paravirt-sched-clock patch to deal with the VMI changes. Zach, can you
>> check that it still works?
>>
I'm working off the same tree as Jeremy, so I'm not seeing any problems
or failures to apply cleanly. As long as sched_clock units match (cycles
vs. ns), it should be ok. And even if they are off, it would be very
hard to tell by observation.
Zach
prev parent reply other threads:[~2007-04-12 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 23:23 paravirt repo rebased to 2.6.21-rc6-mm1 Jeremy Fitzhardinge
2007-04-10 23:29 ` Zachary Amsden
2007-04-11 0:10 ` Chris Wright
2007-04-10 23:29 ` Zachary Amsden
2007-04-10 23:48 ` Chris Wright
2007-04-12 8:54 ` Chris Wright
2007-04-12 15:40 ` Zachary Amsden [this message]
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=461E52FC.7070001@vmware.com \
--to=zach@vmware.com \
--cc=chrisw@sous-sol.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).