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: Thu, 19 Nov 2015 15:03:38 +0000 [thread overview]
Message-ID: <20151119150338.GU1495@citrix.com> (raw)
In-Reply-To: <CAHPMNWd+A=6vvUyds+NU9qdtrh+xCAw4kCuzqgMwTyD7QZrXQw@mail.gmail.com>
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.
> 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.
next prev parent reply other threads:[~2015-11-19 15:03 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 [this message]
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=20151119150338.GU1495@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).