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

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Sun, 2013-03-31 at 12:47 +0100, akshay st wrote:
> 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.

For networking backend you would put the virtual device (the vif) and a
physical device on a standard Linux bridge, or you can use routing/nat
like you would in a non-virtualised router.

For disk backend the blkback driver opens the block device and forwards
requests.

>  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?. 

There is currently no PV MTD device (unless the Xen PV ARM port contains
one, I've no idea).

You could potentially use mtdblock and blkback in the normal way, or you
could perhaps investigate passthrough, or maybe some higher level
service would be appropriate, it really depends what your use case is.

Ian.



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