Hi all, I will post following three patches for pvSCSI driver. 1.) The cs562 has changed VBD backend''s configuration parameter in drivers/xen/Kconfig. I''m sorry, it was a mistake. This patch revert the modification. 2.) This patch fixes pvSCSI backend''s configuration parameter, module dependency and module type, in drivers/xen/Kconfig. 3.) This patch enables SCSI command emulation framework. (The framework was "#if 0"ed on the source code last posted.) And also, REPORT_LUN command emulation is enabled. As for 3.), we consider another flexible framework is needed which provides hot-plug of arbitrary emulation routines. (Some SCSI command, especially for vendor unique command, may require different emulation logic depends on the environment. This is the reason why we need the new framework.) We would like to continue to discuss about the design of the framework. Best regards, ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jun Kamada
2008-Jun-06 08:47 UTC
Re: [Xen-devel] [PATCH 0/3] some fixes for the pvSCSI driver
Hi all, I''m sorry that I have to post a additional patch for following 3.). The patch adds "emulate.o" to make target on drivers/xen/scsiback/Makefile. Best regards, On Wed, 04 Jun 2008 18:22:52 +0900 Jun Kamada <kama@jp.fujitsu.com> wrote:> Hi all, > > I will post following three patches for pvSCSI driver. > > 1.) The cs562 has changed VBD backend''s configuration parameter in > drivers/xen/Kconfig. I''m sorry, it was a mistake. This patch > revert the modification. > 2.) This patch fixes pvSCSI backend''s configuration parameter, module > dependency and module type, in drivers/xen/Kconfig. > 3.) This patch enables SCSI command emulation framework. > (The framework was "#if 0"ed on the source code last posted.) > And also, REPORT_LUN command emulation is enabled. > > As for 3.), we consider another flexible framework is needed which > provides hot-plug of arbitrary emulation routines. (Some SCSI command, > especially for vendor unique command, may require different emulation > logic depends on the environment. This is the reason why we need the > new framework.) We would like to continue to discuss about the design > of the framework. > > > Best regards, > > ----- > Jun Kamada > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel