All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>,
	Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Subject: [RFC] VMI for Xen?
Date: Tue, 14 Mar 2006 16:01:37 -0600	[thread overview]
Message-ID: <44173D41.2080009@us.ibm.com> (raw)

I'm sure everyone has seen the drop of VMI patches for Linux at this 
point, but just in case, the link is included below.

I've read this version of the VMI spec and have made my way through most 
of the patches.  While I wasn't really that impressed with the first 
spec wrt Xen, the second version seems to be much more palatable.  
Specifically, the code inlining and afterburner-style padding seems like 
a really promising approach to native-speed single kernel images.  Also, 
this version seems much more friendly to p2m.

There are still a few things missing (like guest DMA support) but I 
think the basic ideas are pretty sane.  So what does everyone else 
think?  Is there anything within VMI that would inhibit some of Xen's 
optimizations?  Are there any disadvantages to a VMI-style approach to 
the subarch changes?

How close are we to being able to merge our stuff with mainline?  Have 
we gotten feedback yet on how hard this is going to be?  Would VMI be an 
easier approach to inclusion in mainline?

Just thought it would be prudent to start a discussion here, at least, 
about it...

http://lkml.org/lkml/2006/3/13/140

Regards,

Anthony Liguori

             reply	other threads:[~2006-03-14 22:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 22:01 Anthony Liguori [this message]
2006-03-16 20:08 ` [RFC] VMI for Xen? Anthony Liguori
2006-03-19 15:51   ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2006-03-16 23:11 Ian Pratt
2006-03-16 23:24 ` Anthony Liguori
2006-03-16 23:33 ` Anthony Liguori
2006-03-17 10:42   ` Keir Fraser
2006-03-17 14:39     ` Anthony Liguori
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

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=44173D41.2080009@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.