From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Scott <dave.scott@citrix.com>
Cc: xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v2 6/6] Add a general description of the channel mechanism to docs/misc/
Date: Wed, 18 Jun 2014 14:41:42 +0100 [thread overview]
Message-ID: <1403098902.6568.17.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <1402912195-24732-7-git-send-email-dave.scott@citrix.com>
On Mon, 2014-06-16 at 10:49 +0100, David Scott wrote:
> + type = (NONE | FILE | PTY | SOCKET | ... )
Are these the literal xenstore key values, shouty caps and all?
Is this stuff all forward compatible with the existing xenconsoled etc?
What stops it trying to manage these guys?
> + path = <some path>
> +
> +In the default implementation where the backend is run in the toolstack
> +domain, the qemu "chardev" mechanism is used. This implementation
> +interprets the configuration as follows:
> +
> + type = NONE: the backend will be connected to /dev/null
> + type = FILE: the channel will be read the the output appended
"the the".
> + to the file given by 'path'
> + type = PTY: the backend will connect to a PTY like a regular console
> + type = SOCKET: the backend will accept a connection on the Unix
> + domain socket given by 'path' and proxy data to and from the device.
> +
> +If the implementation is in another domain (for example via a Mirage
> +console backend) then the behaviour will be defined by this other domain.
next prev parent reply other threads:[~2014-06-18 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 9:49 [PATCH v2] implement libvirt-like 'channels' via PV consoles David Scott
2014-06-16 9:49 ` [PATCH v2 1/6] libxl: add a list of abstract 'channels' to the domain config David Scott
2014-06-18 13:27 ` Ian Campbell
2014-06-18 14:05 ` Dave Scott
2014-06-18 14:38 ` Ian Campbell
2014-06-16 9:49 ` [PATCH v2 2/6] xl: add support for channels David Scott
2014-06-16 9:49 ` [PATCH v2 3/6] libxl: implement channels via PV console rings David Scott
2014-06-18 13:31 ` Ian Campbell
2014-06-16 9:49 ` [PATCH v2 4/6] libxl: spawn a qemu to implement channels David Scott
2014-06-18 13:32 ` Ian Campbell
2014-06-16 9:49 ` [PATCH v2 5/6] Add a section in xl.cfg(5) describing 'channels' David Scott
2014-06-18 13:38 ` Ian Campbell
2014-06-16 9:49 ` [PATCH v2 6/6] Add a general description of the channel mechanism to docs/misc/ David Scott
2014-06-18 13:41 ` Ian Campbell [this message]
2014-06-18 14:37 ` Dave Scott
2014-06-18 14:43 ` Ian Campbell
2014-06-18 15:00 ` Dave Scott
2014-06-16 13:34 ` [PATCH v2] implement libvirt-like 'channels' via PV consoles Konrad Rzeszutek Wilk
2014-06-16 13:49 ` Dave Scott
2014-06-16 13:52 ` Konrad Rzeszutek Wilk
2014-06-18 13:43 ` Ian Campbell
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=1403098902.6568.17.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=dave.scott@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.