mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Joshua LeVasseur <jtl@ira.uka.de>
Cc: hch@infradead.org, zach@vmware.com, arjan@infradead.org,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
	dhecht@vmware.com, arai@vmware.com, anne@vmware.com,
	pratap@vmware.com, chrisl@vmware.com, chrisw@osdl.org,
	riel@redhat.com, jreddy@vmware.com, jlo@vmware.com,
	kmacy@fsmware.com, jbeulich@novell.com, ksrinivasan@novell.com,
	wim.coekaerts@oracle.com, leendert@watson.ibm.com
Subject: Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
Date: Wed, 15 Mar 2006 12:02:57 -0800	[thread overview]
Message-ID: <20060315120257.28c18344.akpm@osdl.org> (raw)
In-Reply-To: <F032F3F4-00DB-43AF-A67B-E82673883303@ira.uka.de>

Joshua LeVasseur <jtl@ira.uka.de> wrote:
>
> As part of our pre-virtualization work, we developed a virtualization  
> solution similar to VMI.  We support Xen v2 and v3 with high  
> performance.  We added support for the first generation of VMI to our  
> project, and are currently adding support for the latest VMI patch.   
> Our work is open source.  We'll announce when we finish the VMI updates.

Who is "we" and what product are you referring to?

(I think an important part of this discussion is getting an understanding
of which virtualisation products (current or planned) could use a VMI).

Thanks.

  reply	other threads:[~2006-03-15 20:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 17:58 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 [this message]
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
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
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=20060315120257.28c18344.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=anne@vmware.com \
    --cc=arai@vmware.com \
    --cc=arjan@infradead.org \
    --cc=chrisl@vmware.com \
    --cc=chrisw@osdl.org \
    --cc=dhecht@vmware.com \
    --cc=hch@infradead.org \
    --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 \
    --cc=zach@vmware.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

all inboxes | Powered by JetHome®