[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Split Driver States


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: chrisbenninger <chrisbenninger@xxxxxxxxx>
  • Date: Mon, 7 Feb 2011 15:10:34 -0800
  • Delivery-date: Mon, 07 Feb 2011 15:12:56 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=cG7IaETt1tlFQFn+3iq+srJ2o+cAwkrR4zswWXS80uSZQSETmKvTcm6Fx+oEyCk0XH Ow5E4D6ToYjOYJxB2fljzkUZ2CujP3ihBgKCgKNXYI9fDbbip4HFoZkuTc5Mze3RKC2F xsZedqDg/WXLinQJ9qUdMau+a1ggfgXbBWdNs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I was wondering if someone could explain to me the proper minimal sequence of state for the split driver architecture? Or perhaps point me somewhere it is outlined well? 
I looked here: http://wiki.xensource.com/xenwiki/XenSplitDrivers already, but it seems some of my states are not firing when I expect them to, or they are being fired without my knowledge. 

I seem to get kernel panics related to uevent which I have handled in an empty function. All I want is a simple ring setup so I can send info back and forth. I dont really have a need to hook into any actual drivers in dom0.

Thanks.

Chris Benninger
University of Victoria, Computer Science

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.