On Thu, Jan 17, 2013 at 01:07:21PM -0800, Nicholas A. Bellinger wrote: > Hi MST & Co, > > On Thu, 2013-01-17 at 18:43 +0200, Michael S. Tsirkin wrote: > > On Fri, Sep 07, 2012 at 06:48:14AM +0000, Nicholas A. Bellinger wrote: > > > From: Nicholas Bellinger <nab@xxxxxxxxxxxxxxx> > > > > > > Hello Anthony & Co, > > > > > > This is the fourth installment to add host virtualized target support for > > > the mainline tcm_vhost fabric driver using Linux v3.6-rc into QEMU 1.3.0-rc. > > > > > > The series is available directly from the following git branch: > > > > > > git://git.kernel.org/pub/scm/virt/kvm/nab/qemu-kvm.git vhost-scsi-for-1.3 > > > > > > Note the code is cut against yesterday's QEMU head, and dispite the name > > > of the tree is based upon mainline qemu.org git code + has thus far been > > > running overnight with > 100K IOPs small block 4k workloads using v3.6-rc2+ > > > based target code with RAMDISK_DR backstores. > > > > > > Other than some minor fuzz between jumping from QEMU 1.2.0 -> 1.2.50, this > > > series is functionally identical to what's been posted for vhost-scsi RFC-v3 > > > to qemu-devel. > > > > > > Please consider applying these patches for an initial vhost-scsi merge into > > > QEMU 1.3.0-rc code, or let us know what else you'd like to see addressed for > > > this series to in order to merge. > > > > > > Thank you! > > > > > > --nab > > > > OK what's the status here? > > We missed 1.3 but let's try not to miss 1.4? > > > > Unfortunately, I've not been able to get back to the conversion > requested by Paolo for a standalone vhost-scsi PCI device. It doesn't have to be a standalone device. A vhost=on frontend option is also OK I think. Paolo, any objections? > At this point my hands are still full with iSER-target for-3.9 kernel > code over the next weeks. > > What's the v1.4 feature cut-off looking like at this point..? > > --nab Not sure but soon. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html