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

[Xen-users] What modifications are required for my device driver to work with xen.


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Sweekar Pinto" <sweekarpinto@xxxxxxxxx>
  • Date: Fri, 18 Aug 2006 12:32:01 +0530
  • Delivery-date: Fri, 18 Aug 2006 00:05:57 -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; b=C2hMCFDOA0GqKW0eSr+IhdOyUusHGiv/RR/gHB2CgPCeCmC30C2rfpD2uApOg4T1kzYAVffAkMRcuTz3U74jX4RuMZmo8nw1YqTqYad3h9hpRDxwfAV1PZhSt4NFA5LBN6CfGA/2iBTRQTGAGetsb8AoxWmllbsiIZGDIndMcVU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,
Firstly, I apologise for the naivity of my quiestion.
I'm still unclear about the split-driver architecture of xen.
I'm developing a software raid driver, and would like to know the changes required for it to work with xen. (guest).
As I have understood, the Native driver remains unchanged in Dom0. This driver communicates talks with the backend driver and the hardware(or is this the backend driver itself?)
The frontend driver (from the unprivilaged domain) talks to the backend driver to access hardware.
Is my understanding of the concept correct? if yes, then how do I go about writing the frontend driver? if I'm wrong (which is very highly possible :P), please enlighten me :)
Thanks in Advance,
Sweekar.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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