From: Andi Kleen <ak@suse.de>
To: kvm-devel@lists.sourceforge.net
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, lguest@ozlabs.org
Subject: Re: [kvm-devel] [RFC] 9p Virtualization Transports
Date: Fri, 31 Aug 2007 22:22:44 +0200 [thread overview]
Message-ID: <200708312222.44948.ak@suse.de> (raw)
In-Reply-To: <11883271601857-git-send-email-ericvh@gmail.com>
On Tuesday 28 August 2007 20:52:36 Eric Van Hensbergen wrote:
> This patch set contains a set of virtualization transports for the 9p file
> system intended to provide a mechanism for guests to access a portion of the
> hosts name space without having to go through a virtualized network.
It might be useful to convert UML's hostfs to something like this. It's essentially
the same.
-Andi
next prev parent reply other threads:[~2007-08-31 20:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 18:52 [RFC] 9p Virtualization Transports Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: Make transports dynamic Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: add KVM/QEMU pci transport Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: add lguest transport Eric Van Hensbergen
2007-08-28 18:52 ` [REFERENCE ONLY] 9p: add shared memory transport Eric Van Hensbergen
2007-08-28 19:33 ` [RFC] 9p: add KVM/QEMU pci transport Christoph Hellwig
2007-08-28 20:08 ` [kvm-devel] " Arnd Bergmann
2007-08-28 20:41 ` Latchesar Ionkov
2007-08-28 23:59 ` [Lguest] " Dor Laor
2007-08-28 20:56 ` Eric Van Hensbergen
2007-08-29 0:01 ` Dor Laor
2007-08-29 16:29 ` Anthony Liguori
2007-08-29 16:37 ` [V9fs-developer] " Latchesar Ionkov
2007-08-30 4:40 ` [Lguest] [V9fs-developer] [kvm-devel] [RFC] 9p: add KVM/QEMUpci transport Dor Laor
2007-08-31 20:22 ` Andi Kleen [this message]
2007-09-01 21:14 ` [Lguest] [RFC] 9p Virtualization Transports Rusty Russell
2007-09-03 20:19 ` Eric Van Hensbergen
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=200708312222.44948.ak@suse.de \
--to=ak@suse.de \
--cc=ericvh@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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