xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Neil Sikka <neilsikka@gmail.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
	Linda <lindaj@jma3.com>
Subject: Re: 9p file system for xen
Date: Mon, 23 Nov 2015 16:05:58 +0000	[thread overview]
Message-ID: <20151123160558.GA9807@citrix.com> (raw)
In-Reply-To: <CAHPMNWcmCLuxM9Q-b1BZSHFmAiBAiOomJcZV=CRP18Lf+wE1+Q@mail.gmail.com>

On Mon, Nov 23, 2015 at 10:51:04AM -0500, Neil Sikka wrote:
> Wei, based on our discussions, you will review as much as possible before
> leaving for vacation, and have started last Wednesday. Could you please
> share what you are reviewing so I (and anyone else interested) can also
> assist in reviewing it?
> 

What I meant was "when patches are posted to xen-devel I will try to
review as much as possible". There is no patch on xen-devel so I haven't
actually reviewed anything, nor can anyone else who is interested in
getting it work review anything.

What I started last Wednesday was refactoring some QEMU code (only
renaming files and making QEMU build), so that QEMU 9pfs doesn't just
assume it is using virtio transport. I didn't mean I started review
anything.

Further discussion should go to xen-devel. There is definitely a need to
get input from wider community to better coordinate this work.

Wei.

> As you said, the front/back end negotiation protocols need to be designed
> and agreed upon, and we can start that now in parallel with the code review.
> 
> On Thu, Nov 19, 2015 at 11:23 AM, Linda <lindaj@jma3.com> wrote:
> 
> > Hi Wei,
> >
> > On 11/19/2015 8:03 AM, Wei Liu wrote:
> >
> >> On Thu, Nov 19, 2015 at 09:55:00AM -0500, Neil Sikka wrote:
> >>
> >>> Is there any documentation about planned interfaces and API contracts for
> >>> people building around the virtio/9pfs layers? For example, while this is
> >>>
> >> I assume that you're interested in getting 9pfs to work but don't care
> >> much about how it is made to work? I ask because I'm a bit confused by
> >> the notion of "virtio/9pfs" because what Linda did wasn't based on
> >> virtio transport.
> >>
> > A clarification:  If you mean the virtio 9pfs transport, my code is based
> > on that, and sits on top of it.
> >
> >
> >> still getting debugged/checked in, in order to build DomU support for
> >>> these
> >>> devices, the expected API contracts/interfaces would need to be known.
> >>>
> >>> I'm not sure I get your question. What do you mean by "build DomU
> >> support"? What kind of DomU support needs insider knowledge of how 9pfs
> >> is setup? Are you talking about your own management stack that starts
> >> VM?
> >>
> >> Wei.
> >>
> >>
> >
> 
> 
> -- 
> My Blog: http://www.neilscomputerblog.blogspot.com/
> Twitter: @neilsikka

  reply	other threads:[~2015-11-23 16:05 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
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 [this message]
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=20151123160558.GA9807@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).