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

[Xen-devel] getting started with writing block device drivers


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Venkata Sreenivasa Rao Nagineni" <vnagineni@xxxxxxxxx>
  • Date: Thu, 7 Sep 2006 15:51:07 +0530
  • Delivery-date: Thu, 07 Sep 2006 03:22:35 -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=hkIrvZXarfKTDggYYpMM1huCaq5huCwXpOELYYZMkKFlVB9yLibPpXecwCoGUwgYxIMaiznLBgrqwO9BLMGLzxpXTdo314qUmeQHBuYwnNrUjic2VmpifIWipbOYDfjsTAtX75mMpC4jxSrWNgfglPcZHqhXvXxXKx4kMmw+k+o=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

   I am planning to write a sample block device driver (probably ramdisk) on Xen. Basically I want to have an hands-on experience about how the I/O is being transmitted between front end driver and back end driver. And also I want to see how the ioctls that are issued from guest OSs front end driver will be transmitted/serviced by back end drivers.

   Could you please give me interface specifications to write a sample block device driver so that i can see the ioctls and data moving back and forth between front end and backend drivers?

TIA.,
-Venkata Sreenivasa Rao Nagineni
_______________________________________________
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®.