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