[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 0/4] PV SCSI driver (scsiback/scsifront)
Thanks for your comment.
Sent: Mon, 16 Jul 2007 13:43:48 +0300
Subject: Re: [Xen-devel] [PATCH 0/4] PV SCSI driver (scsiback/scsifront)
> On Fri, Jul 13, 2007 at 08:26:46PM +0900, Tomonari Horikoshi wrote:
> > Hi all.
> > We developped a first version PV SCSI.
> > (without a FC-SCSI driver by Kamada-san)
> > The change point is the following:
> > * implement python code
> > -> attach, detach, list support.
> > Usage
> > # xm scsihost-attach <Domain> scsi <SCSIHostno>
> > # xm scsihost-detach <Domain> <SCSIHostno>
> > # xm scsihost-list <Domain>
> > <SCSIHostno> = scsi host number on Dom0
> Can you tell more about this patch..
> The whole HBA is mapped to the guest.. Is the access to the devices on that
> HBA exclusive for the guest, or can some of the devices be used on dom0 and
> some on domU ?
> Any plans to write single lun/id mapping code?
> -- Pasi
This driver is not HBA exclusive for the guest.
Therefore, another guest cannot use the device on same HBA.
We will develop the method to allocate to the guest by the unit of targetid.
The Backend driver is issuing SCSI CDB to the Native SCSI as follows,
* It gets "struct scsi_device" by using "scsi_device_lookup()".
At this time, the host_no uses the number of Native of backend domain.
Besides (target_id, channel_id, lun_id), it uses the number sent from
* It map DMA by using granttable.(like a VBD)
* It issues the SCSI command by "blk_execute_rq_nowait()" by using
guest's SCSI CDB.
Xen-devel mailing list