WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] console driver - How domain0 processes console messages

To: Richard <judicator3@xxxxxxxxx>
Subject: Re: [Xen-devel] console driver - How domain0 processes console messages ?
From: Andrew Warfield <andrew.warfield@xxxxxxxxx>
Date: Wed, 16 Feb 2005 07:54:22 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 16 Feb 2005 07:55:14 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZVZcSEgKtqZHx9VsM6T/2M8E9Z9LTpOkbPWCGf/1ZHlJNnjdF7pxWiHMBSVTsK7wscKyPFUMtjq3WFtg9d9aZR0OdrPSW08KMQW4dOg8rgAHLWjv/RLYxyRDoS2vmjkSs32byNblLqMlIvakomVRqKHcfZQn6B9ag4MQjVaE51M=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <a146ff9b05021522102e311f77@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <a146ff9b05021522102e311f77@xxxxxxxxxxxxxx>
Reply-to: andrew.warfield@xxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I am trying to undestand how domain0 processes console
> messages  (i.e messages with type CMSG_CONSOLE and subtype
> CMSG_CONSOLE_DATA).

Console messages currently share the same shared memory rings that
control messages use.  As such, ctrl_if_send_message_noblock(), is a
non-blocking send on these rings, and ctrl_if_notify_controller() is
an event channel notification of a control event.  Aside from console
messages, control messages are exactly that -- things like driver
setup and connection.  See xen/include/public/io/domain_controller.h
for a full list.

The control message rings are mapped to user space in dom0 through
calls to libxc, while the notification is delivered to dom0 via
/dev/evtchn.  If you are using stable or testing, these rings are
accessed directly by xend, see tools/python/xen/lowlevel/xu/xu.c
(especially the notifier and port objects therein).  If you are using
the unstable tree, xcs (tools/xcs/xcs.c) demultiplexes the shared
rings/event channels.

In xend, consol messages are eventually handled in
tools/python/xen/xend/server/console.py.

Hope that helps.  We plan to separate the console messages from the
control rings in the very near future, allowing them to have a
separate driver and be throttled independent of control messages. 
This should make the current interface considerably simpler.

hth,
a.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel