xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Linda <lindaj@jma3.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	Neil Sikka <neilsikka@gmail.com>, Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: 9p file system for xen
Date: Wed, 18 Nov 2015 09:56:27 +0000	[thread overview]
Message-ID: <20151118095627.GJ1495@citrix.com> (raw)
In-Reply-To: <564B8505.3060302@jma3.com>

On Tue, Nov 17, 2015 at 12:50:29PM -0700, Linda wrote:
> 
> 
> On 11/17/2015 11:35 AM, Neil Sikka wrote:
> >How does Linda's work relate to Wei's patches available here (I didnt see
> >them in Xen-4.6.0):
> >
> >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-01-xenpv-exec.patch
> >http://downloads.xen.org/Wiki/VirtioOnXen/qemu-02-virtio-for-pv.patch
> I'll let Wei answer this.

That wasn't upstreamed at all. Admittedly that was done when I didn't
know much about Xen. I would have done that project differently
nowadays.

And to clarify things: virtio on Xen is a different project than 9pfs on
Xen. 9pfs is not tied to virtio in any way. Just that there is currently
only virtio-9pfs available.

So to make 9pfs work on Xen, there are at least two ways. One is to make
virtio work on Xen so that we subsequently get virtio-9pfs (along with
all other virtio devices); the other is to implement xen-9pfs (I made up
this name).

I'm not sure whether you're interested in virtio on Xen or just 9pfs.

> >
> >Also, since 9p is being worked on, which is a filesystem that should be
> >implemented in a kernel rather than a hypervisor, are you looking to
> >contribute this driver to the Linux kernel?
> What I did was write new kernel routines and new Qemu routines, as well as

I think Neil was talking about the "new kernel routines". Yes, that
would need to be upstreamed eventually.

Wei.

> modifying a few existing Qemu files.  The initialization is currently done
> manually by modifying xenstore.  This is the only code that properly belongs
> in the hypervisor.
> 
> I hope this clarifies things.
> 
> Linda

  reply	other threads:[~2015-11-18  9:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 17:23 9p file system for xen Linda
2015-11-16 15:16 ` Wei Liu
2015-11-16 16:36   ` Linda
2015-11-16 16:51     ` Wei Liu
2015-11-16 17:22       ` Linda
2015-11-16 17:35         ` Wei Liu
2015-11-17  3:02           ` Linda
2015-11-17 18:35             ` Neil Sikka
2015-11-17 19:50               ` Linda
2015-11-18  9:56                 ` Wei Liu [this message]
2015-11-19 14:55                   ` Neil Sikka
2015-11-19 15:03                     ` Wei Liu
2015-11-19 16:23                       ` Linda
2015-11-23 15:51                         ` Neil Sikka
2015-11-23 16:05                           ` Wei Liu
2015-11-30 17:19                   ` Neil Sikka
2015-12-01 11:47                     ` Wei Liu
2015-12-01 14:37                       ` Linda
2015-12-01 14:46                         ` Wei Liu
2015-12-01 15:27                           ` Linda
2015-12-02 17:40                           ` Linda
2015-11-19 15:05             ` Wei Liu

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=20151118095627.GJ1495@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=lindaj@jma3.com \
    --cc=neilsikka@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).