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] Doamin controller guidelines

To: "Mark Williamson" <mark.williamson@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Doamin controller guidelines
From: "Aggarwal, Vikas \(OFT\)" <Vikas.Aggarwal@xxxxxxxxxxxxxxx>
Date: Tue, 3 May 2005 10:01:02 -0400
Delivery-date: Tue, 03 May 2005 14:00:42 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVOpCKNl8pkAz9pSuOGsYiauV9ePQBQxMkA
Thread-topic: [Xen-devel] Doamin controller guidelines
We have a kernel debugging driver, controlled via IOCTL. We need to port
our tool to Xen so that we can trace the guest kernels, control our
tracer and collect trace data from the host kernel in domain 0.

1- Send control command to our tracer : control data from domain0 to the
kernel of domain1 for example start/stop tracing.

2 Send the trace data generated by the guest kernel to the host
kernel.(shared ring ? , I am using 2.0.5)

Right  now I am adding support into python XEND, I already have some
basic frame work in place for my FE/BE.
I am unfamiliar with python but more than that the logic in XEND. I
created my own trace_debug.py  based on blkif.py.  

But I don't understand what to do corresponding to Blkctl.py.  I am
really not sure what to put into my trace_debug_ctl.py corresponding to
Blkctl.py. I believe its because I don't understand what is expected
inside XEND.  Please pour some light on this area.

Thanks
-vikas 
 
-----Original Message-----
From: maw48@xxxxxxxxxxxxxxxx [mailto:maw48@xxxxxxxxxxxxxxxx] On Behalf
Of Mark Williamson
Sent: Sunday, May 01, 2005 8:16 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Aggarwal, Vikas (OFT)
Subject: Re: [Xen-devel] Doamin controller guidelines

>   Kindly provide me some basic informnation on how to enahnce
>   the XEN domain controller code for my newly ported
front-end/back-end
> driver. I trying to dig into mailing lists but could not find
something for
> domain controller enhancement (2.0.5 XEN) .  Though i found doc/misc/
very
> helpful for FE/BE  but nothing there to help in domain controller.

Look in: tools/python/xen/xend/server/{blk,net}if.py

These implement the domain-controller end of the protocol.  Other
relevant 
code is in controller.py and channel.py (also in that directory).
Currently 
this code uses the Deferred objects in the Twisted Matrix framework to 
implement this in a non-blocking way.  If you ever look at supporting 
unstable / 3.0, you should be aware a Xend rewrite is in progress for
the 
unstable tree that will eliminate use of Twisted and use language level 
threads - allowing you to block instead of using Deferreds.

If you need configuration details in the domain config file, you'll also
need 
to modify the xm tool and various other parts of Xend.  You might find 
tracing through how block or net configuration works a helpful exercise
is 
this case.

I'm personally curious what your front / back end is ;-)  Will we get to
see 
it some time?

HTH,
Mark

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>