From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: ian.jackson@eu.citrix.com, cyliu@suse.com, jbeulich@suse.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] doc: document pvusb Xenstore paths
Date: Fri, 1 Apr 2016 10:49:46 -0400 [thread overview]
Message-ID: <20160401144946.GB22004@char.us.oracle.com> (raw)
In-Reply-To: <1459424812-6952-3-git-send-email-jgross@suse.com>
On Thu, Mar 31, 2016 at 01:46:52PM +0200, Juergen Gross wrote:
> The patches adding Xen tools support for paravirtualized USB devices
> (pvUSB) omitted documenting the introduced Xenstore paths.
>
> Add the paths to docs/misc/xenstore-paths.markdown
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
> docs/misc/xenstore-paths.markdown | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/docs/misc/xenstore-paths.markdown b/docs/misc/xenstore-paths.markdown
> index ce00afe..087e239 100644
> --- a/docs/misc/xenstore-paths.markdown
> +++ b/docs/misc/xenstore-paths.markdown
> @@ -270,6 +270,11 @@ A virtual network device frontend. Described by
> A virtual scsi device frontend. Described by
> [xen/include/public/io/vscsiif.h][SCSIIF]
>
> +#### ~/device/vusb/$DEVID/* []
> +
> +A virtual usb device frontend. Described by
> +[xen/include/public/io/usbif.h][USBIF]
> +
> #### ~/console/* []
>
> The primary PV console device. Described in [console.txt](console.txt)
> @@ -344,6 +349,11 @@ A virtual network device backend. Described by
>
> A PV SCSI backend.
>
> +#### ~/backend/vusb/$DOMID/$DEVID/* []
> +
> +A PV USB backend. Described by
> +[xen/include/public/io/usbif.h][USBIF]
> +
> #### ~/backend/console/$DOMID/$DEVID/* []
>
> A PV console backend. Described in [console.txt](console.txt)
> @@ -536,5 +546,6 @@ domain instead of a daemon in dom0.
> [NETIF]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,netif.h.html
> [SCSIIF]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,vscsiif.h.html
> [SI]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,xen.h.html#Struct_start_info
> +[USBIF]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,usbif.h.html
> [VCPU]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,vcpu.h.html
> [XSWIRE]: http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,xs_wire.h.html
> --
> 2.6.2
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-01 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 11:46 [PATCH 0/2] doc: Update docs/misc/xenstore-paths.markdown Juergen Gross
2016-03-31 11:46 ` [PATCH 1/2] doc: correct hyperlinks in docs/misc/xenstore-paths.markdown Juergen Gross
2016-04-01 14:47 ` Konrad Rzeszutek Wilk
2016-03-31 11:46 ` [PATCH 2/2] doc: document pvusb Xenstore paths Juergen Gross
2016-04-01 14:49 ` Konrad Rzeszutek Wilk [this message]
2016-04-01 14:53 ` [PATCH 0/2] doc: Update docs/misc/xenstore-paths.markdown Ian Jackson
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=20160401144946.GB22004@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=cyliu@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.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).