From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [RFC] VMI for Xen?
Date: Thu, 16 Mar 2006 17:33:49 -0600 [thread overview]
Message-ID: <4419F5DD.70100@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4B9D86@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Just some food for thought, I did a simple analysis of the
>> size of Xen Linux patches verses the VMI patches. To make
>> things more fair, I removed everything from the XenoLinux
>> port accept for the i386 xen subarch (so no drivers and no
>> support for other architectures).
>>
>
> Your analysis is still taking all the patches to make dom0 functionality
> work, which accounts for a lot of changes and is totally outside of the
> scope of VMI.
>
> We've been working with a bunch of RH/Novell folks to create a stripped
> down domU-only Xen patch that would be a fairer comparison.
>
> We're currently looking though the new VMI patchset to see whether
> there's anything worth having, in particular, if there's anything that
> should be added to our patch to support what we can deduce that their
> hypervisor probably needs. We've also talking to the VirtualIron team to
> make sure we're inclusive as possible.
>
> The current VMI patchset couldn't support Xen's direct-mode (non shadow)
> MMU virtualization, and hasn't really been thought through properly for
> SMP. I'm sure we'll get something worked out that keeps everyone happy.
>
Actually, the new spec does support non-shadow paging. All page table
updates are done via the VMI ROM. Normally, these are just normal
get/set operations but they could be get/sets with p2m looks. The first
version of the spec definitely didn't support non-shadow paging though.
We'll see whether it's actually implementable when the wedge is released
though. I wouldn't be surprised if they are using shadow paging.
The new spec does actually introduce SMP stuff but yeah, you're probably
right, it may not have been thought through enough... The biggest gaps
that I can find appear to be DMA support and event channels. I think to
properly support event channel you need a bit more pervasive changes. I
think DMA is a pretty simply change (you just have to update the DMA bus
translation functions to do a p2m lookup).
Regards,
Anthony Liguori
> Ian
>
next prev parent reply other threads:[~2006-03-16 23:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 23:11 [RFC] VMI for Xen? Ian Pratt
2006-03-16 23:24 ` Anthony Liguori
2006-03-16 23:33 ` Anthony Liguori [this message]
2006-03-17 10:42 ` Keir Fraser
2006-03-17 14:39 ` Anthony Liguori
2006-03-17 18:19 ` [Xen-devel] " Zachary Amsden
2006-03-17 18:19 ` Zachary Amsden
2006-03-16 23:55 ` Chris Wright
2006-03-17 0:10 ` Anthony Liguori
2006-03-17 8:53 ` Keir Fraser
2006-03-17 8:59 ` Keir Fraser
[not found] <4419F36A.6070906@vmware.com>
2006-03-17 0:09 ` Daniel Arai
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 22:01 Anthony Liguori
2006-03-16 20:08 ` Anthony Liguori
2006-03-19 15:51 ` Anthony Liguori
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=4419F5DD.70100@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.