public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Andrew Morton <akpm@osdl.org>, Dan Hecht <dhecht@vmware.com>,
	Dan Arai <arai@vmware.com>, Anne Holler <anne@vmware.com>,
	Pratap Subrahmanyam <pratap@vmware.com>,
	Christopher Li <chrisl@vmware.com>,
	Joshua LeVasseur <jtl@ira.uka.de>, Chris Wright <chrisw@osdl.org>,
	Rik Van Riel <riel@redhat.com>, Jyothy Reddy <jreddy@vmware.com>,
	Jack Lo <jlo@vmware.com>, Kip Macy <kmacy@fsmware.com>,
	Jan Beulich <jbeulich@novell.com>,
	Ky Srinivasan <ksrinivasan@novell.com>,
	Wim Coekaerts <wim.coekaerts@oracle.com>,
	Leendert van Doorn <leendert@watson.ibm.com>
Subject: Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
Date: Mon, 13 Mar 2006 20:01:23 -0800	[thread overview]
Message-ID: <44164013.1080404@vmware.com> (raw)
In-Reply-To: <441610DE.5060709@us.ibm.com>

Anthony Liguori wrote:
> Zachary Amsden wrote:
>> This is by no means finished work. A few of the areas that need more
>> attention and exploration are (a) 64bit support is still lacking, but we
>> feel a port of VMI to the 64 bit Linux can be done without too much
>> trouble (b) the Xen compatibility layer needs some work to bring it
>> up to the Xen 3.0 interfaces.  Work is underway on this already, and
>> no major issues are expected at this time.   
> Hi Zach,
>
> Can you please post the Xen compatibility layer (even if it is for 
> 2.0.x).  I think it's important to see that code to understand the 
> advantages/disadvantages compared to the existing Xen 
> paravirtualization interface.  Likewise, any Xen performance data 
> would be useful as there has been some discussion about whether VMI 
> would negatively impact Xen performance[1].

About performance - I actually believe that it is possible to implement 
VMI Linux in such a way that it actually has _better_ performance on Xen 
than the current XenoLinux kernels.

I'm working on getting together the older interface pieces now.

Zach

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 17:58 [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal Zachary Amsden
2006-03-13 18:09 ` Arjan van de Ven
2006-03-13 18:22   ` Zachary Amsden
2006-03-13 18:26     ` Arjan van de Ven
2006-03-13 18:30       ` Zachary Amsden
2006-03-13 18:42         ` Arjan van de Ven
2006-03-13 18:48           ` Zachary Amsden
2006-03-13 19:02             ` Chris Wright
2006-03-13 18:56           ` Joshua LeVasseur
2006-03-16 18:52             ` Jan Engelhardt
2006-03-13 18:56         ` Hollis Blanchard
2006-03-13 18:59           ` Zachary Amsden
2006-03-15 10:25     ` Christoph Hellwig
2006-03-15 15:57       ` Zachary Amsden
2006-03-15 17:38       ` Joshua LeVasseur
2006-03-15 20:02         ` Andrew Morton
2006-03-16  0:05           ` Joshua LeVasseur
2006-03-13 20:17 ` Sam Vilain
2006-03-14  0:39 ` Anthony Liguori
2006-03-14  4:01   ` Zachary Amsden [this message]
2006-03-14  4:04     ` Rik van Riel
2006-03-14  4:55       ` Zachary Amsden
2006-03-14  4:13 ` Anthony Liguori
2006-03-14  4:26   ` Zachary Amsden
2006-03-14  4:30     ` Rik van Riel
2006-03-14  5:46       ` Zachary Amsden
2006-03-14 12:44         ` Rik van Riel
2006-03-14 16:22           ` Zachary Amsden
2006-03-16 18:58         ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2006-03-17 15:56 Chuck Ebbert
2006-03-17 17:52 ` Zachary Amsden
2006-03-20 22:03 Anne Holler

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=44164013.1080404@vmware.com \
    --to=zach@vmware.com \
    --cc=akpm@osdl.org \
    --cc=aliguori@us.ibm.com \
    --cc=anne@vmware.com \
    --cc=arai@vmware.com \
    --cc=chrisl@vmware.com \
    --cc=chrisw@osdl.org \
    --cc=dhecht@vmware.com \
    --cc=jbeulich@novell.com \
    --cc=jlo@vmware.com \
    --cc=jreddy@vmware.com \
    --cc=jtl@ira.uka.de \
    --cc=kmacy@fsmware.com \
    --cc=ksrinivasan@novell.com \
    --cc=leendert@watson.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pratap@vmware.com \
    --cc=riel@redhat.com \
    --cc=torvalds@osdl.org \
    --cc=virtualization@lists.osdl.org \
    --cc=wim.coekaerts@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox