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

[XenARM] Questions on Xen Back end and front end drivers


  • To: "xen-arm@xxxxxxxxxxxxx" <xen-arm@xxxxxxxxxxxxx>
  • From: akshay st <akshayts@xxxxxxxxxxx>
  • Date: Sun, 31 Mar 2013 19:47:39 +0800 (SGT)
  • Delivery-date: Sun, 31 Mar 2013 11:48:52 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=eOK/EeGHtvgJ4p2CbWL2FEQSNXzbHGBHzQldSwlJp1pPu7AHLWyQ3b7ldh0ic/n8+3XnxrHFf8lQZw8oiliIIrYvLL9HLKiyXUhv+Bb6VlG4i2lC9A9//pVKFUAKmmO527wZdMH4plFLL1BGmR96k5rEdrYDK0wDQcu6cBYq7uA=;
  • List-id: List for Xen ARM developers and users <xen-arm.lists.xen.org>

Hi,
I read that DOM0 implements and handles all device drivers. All Domu's access device driver through DOM0, For this back end and front end drivers were created?. Just for understanding i was going  through Linux XEN Block back end and front end driver.(xen-blkfront.c), I am not sure but i see that there no real device involved in frontend and backend communication? How does it boil down to Real device. What is the use of XEN Block back end and front end drivers since there communication happens only thru Memory ?.

For example i have a MTD Nand device which DOM0 should implement completely?.
How can other Domains access this MTD Device I guess we have to have a MTD Back end driver for DOM0 and front end drivers for DOM U's?

My understanding is Back end drivers should do hardware specific tasks?. Any good reference to understand backend and front end would be of great help.

Warm Regards,
Akshay
_______________________________________________
Xen-arm mailing list
Xen-arm@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm

 


Rackspace

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