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

[Xen-devel] question on triggering of _probe()


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "junghwan rhee" <jhrhee@xxxxxxxxx>
  • Date: Fri, 14 Apr 2006 14:24:16 -0400
  • Delivery-date: Fri, 14 Apr 2006 11:24:34 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OJgR7QOzqI6vp48GXdIhbe5IJpJFoTHGDpRcdhOr3/NNzJ0UtgiJG/1SXGNtk1p0Yu2ysONOVd7zPcl5FZo3Sb+5o8sfkb0QVf/tqmzuZ4KGTNLymQLiVUz79xLcxXY2LTloo8DrBqcx9GNvRPQOWGoYiC6Y18Y8FPBieUXQLy8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,
I am planning some experiment that needs
two way communication between hypervisor and guest kernels.
I thought split driver is one way, so tried to use
the code in the BE/FE driver section of XenIntro page.

I am wondering how to trigger the _probe() in xen 3.0.
I saw the Note: that you were working on it, but I thought
there must be some other people who tried similar thing.

I tried to use xenstore-write tool as described, but I couldn't see
the mydevice in the xenstore tree although the module is in the
kernel (_init printk message was printed in booting).

Will be there a similar approach in xen 3.0?
Thanks in advance.

Regards,
J.R.

_______________________________________________
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®.