From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@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
Message-ID: <1403098902.6568.17.camel@kazak.uk.xensource.com>
References: <1402912195-24732-1-git-send-email-dave.scott@citrix.com>
	<1402912195-24732-7-git-send-email-dave.scott@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1WxG7n-0002Z2-Ex
	for xen-devel@lists.xenproject.org; Wed, 18 Jun 2014 13:42:03 +0000
In-Reply-To: <1402912195-24732-7-git-send-email-dave.scott@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
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
List-Id: xen-devel@lists.xenproject.org

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.