From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: 9p file system for xen Date: Mon, 23 Nov 2015 16:05:58 +0000 Message-ID: <20151123160558.GA9807@citrix.com> References: <564A10E1.4070607@jma3.com> <20151116173559.GC25764@citrix.com> <564A98CB.9090506@jma3.com> <564B8505.3060302@jma3.com> <20151118095627.GJ1495@citrix.com> <20151119150338.GU1495@citrix.com> <564DF774.70602@jma3.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Neil Sikka Cc: Julien Grall , xen-devel@lists.xen.org, Wei Liu , Linda List-Id: xen-devel@lists.xenproject.org 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 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