From: Zachary Amsden <zach@vmware.com>
To: Andi Kleen <ak@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Thu, 08 Feb 2007 23:35:07 -0800 [thread overview]
Message-ID: <45CC242B.4010909@vmware.com> (raw)
In-Reply-To: <200702090821.48478.ak@suse.de>
Andi Kleen wrote:
> On Friday 09 February 2007 06:28, Zachary Amsden wrote:
>
>> So, as 2.6.21-rc1 is approaching, what is the upstream merge status for
>> the paravirt-ops backends? I believe VMI is in Andi's tree, plus or
>> minus some bugfixes that are still being whittled in, but Andi, do you
>> think the VMI code is in good shape for merging?
>>
>
> I don't know in what shape it is in as it hasn't been tested by me.
> From the looks it looks reasonable enough for merging. But I didn't like
> some of your recent updates.
>
If you think any of them can be done cleaner, let me know and I will
redo the patches.
The USE_REAL_TIME_DELAY stuff is really ugly, and mostly a hack. You
can drop it. Our fix should be to not let the virtual hardware drive
the physical hardware that fast, or to recognize the panic state in
delay loops and start respecting instead of ignoring delay.
Zach
prev parent reply other threads:[~2007-02-09 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Paravirt-ops VMI / Xen / lrustyvisor merge status Zachary Amsden
2007-02-09 5:54 ` Rusty Russell
2007-02-09 6:12 ` Zachary Amsden
2007-02-09 6:24 ` Jeremy Fitzhardinge
2007-02-09 6:58 ` Zachary Amsden
2007-02-09 6:44 ` Rusty Russell
2007-02-09 6:57 ` Jeremy Fitzhardinge
2007-02-09 6:59 ` Zachary Amsden
2007-02-09 7:06 ` Jeremy Fitzhardinge
2007-02-09 7:20 ` Rusty Russell
2007-02-09 7:35 ` Andi Kleen
2007-02-09 8:46 ` Rusty Russell
2007-02-09 6:10 ` Jeremy Fitzhardinge
2007-02-09 7:21 ` Andi Kleen
2007-02-09 7:35 ` 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=45CC242B.4010909@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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).