search for: scsifront

I''ve been having a look through scsifront again, and I saw this bit: ring_req->timeout_per_command = (sc->timeout_per_command / HZ); ring_req->nr_segments = 0; spin_unlock_irq(host->host_lock); scsifront_do_request(info); wait_event_interruptible(info->shadow[ring_req->rqid].wq_reset, info->shadow[r...

...$(CONFIG_XEN_DEVMEM) += char/ obj-$(CONFIG_XEN_BLKDEV_BACKEND) += blkback/ +obj-$(CONFIG_XEN_SCSI_BACKEND) += scsiback/ obj-$(CONFIG_XEN_NETDEV_BACKEND) += netback/ obj-$(CONFIG_XEN_TPMDEV_BACKEND) += tpmback/ obj-$(CONFIG_XEN_BLKDEV_FRONTEND) += blkfront/ +obj-$(CONFIG_XEN_SCSI_FRONTEND) += scsifront/ obj-$(CONFIG_XEN_NETDEV_FRONTEND) += netfront/ obj-$(CONFIG_XEN_PCIDEV_BACKEND) += pciback/ obj-$(CONFIG_XEN_PCIDEV_FRONTEND) += pcifront/ diff -r ed8d345449c1 -r 7111077b493e xen/include/public/io/scsi.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/xen/include/public/io/scsi.h Wed Aug 02...

Hello, http://pasik.reaktio.net/xen/patches/xen-pvscsi-drivers-linux-2.6.32.27-pvops-v01.diff This is the first version of Xen PVSCSI drivers, both the scsiback backend and scsifront frontend, ported from Novell SLES11SP1 2.6.32 Xenlinux kernel to pvops xen/stable-2.6.32.x branch. At the moment it''s *only* compile-tested with the latest xen/stable-2.6.32.x git kernel as of today (2.6.32.27), on Fedora 14 x86_64. Comments welcome. I''m sure there are still...

...iki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04) there are no scsi device found, and no scsifront found. And this is the sdc in the host. [ 33.590845] sd 4:0:2:0: [sdc] 143374650 512-byte logical blocks: (73.4 GB/68.3 GiB) [ 33.593536] sd 4:0:2:0: [sdc] Write Protect is off [ 33.593641] sd 4:0:2:0: [sdc] Mode Sense: b3 00 10 08 [ 33.596233] sd 4:0:2:0: [sdc] Write cache: enabled, read...

Hi all. We developped a pv-scsi driver that we refered Fujita-san''s scsi-driver and blkback. (see, http://www.xensource.com/files/xensummit_4/Xen_Summit_8_Matsumoto.pdf) The pv-scsi driver''s feature is as follow: * Guest has dedicated SCSI-HBAs of Dom0. * Guest can send scsi_cdb to the HBAs. * Guest recognises the HBAs from hostno of xenstore. Currentlly, We are

pvscsi appears to be missing from the pvops kernel. Is there a specific reason for this or has it just not been done yet? James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I''m trying to compile pvscsi out-of-tree, and I''m getting an error that set_phys_to_machine is not defined when I try to load the module (with the warning to that effect at compile time too). This used to work fine in pvops. It seems that netfront uses that symbol in a module so I''m confused as to why pvscsi can''t... any suggestions? Is it one of the virtues of

This patch is for Makefile and Kconfig file for scsifront and scsiback driver. Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Tsunehisa Doi <Doi.Tsunehisa@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> Signed-off-by: Akira Hayakawa <hayakawa.akira@jp.fujitsu.com> ----- Jun Kamada...

Hi, I am working as a system administrator at an internet platform service provider, and I am currently seeking to re-new our Xen virtualization infrastructure for which I am mostly responsible for. Currently, we run Xen 3.4.2/3.4.3 on RHEL/CentOS 5.x (5.7) as Dom0 with CentOS 5.x pv-guests. Based on my experiments, I am currently looking into Xen 4.1.2 on RHEL/CentOS 6.x (6.2), with a

...aemon before starting domainUs (otherwise Domain0 crashes). /usr/sbin/tgtd -f -d8 The above command runs the daemon in the foreground. So run start VMs with another terminal. If everything goes well, a SCSI host shows up in your VM (DomainU). clematis:/# cat /sys/class/scsi_host/host0/proc_name scsifront And you can see a disk driver: clematis:/# ls /sys/class/scsi_device/0\:0\:0\:0/device/ block:sda iocounterbits queue_depth scsi_level vendor bus iodone_cnt queue_type state delete ioerr_cnt rescan timeout device_blocked iore...

...obj-$(CONFIG_BE2ISCSI) += libiscsi.o be2iscsi/ obj-$(CONFIG_SCSI_ESAS2R) += esas2r/ obj-$(CONFIG_SCSI_PMCRAID) += pmcraid.o +CFLAGS_virtio_scsi.o += -D__CHECK_ENDIAN__ obj-$(CONFIG_SCSI_VIRTIO) += virtio_scsi.o obj-$(CONFIG_VMWARE_PVSCSI) += vmw_pvscsi.o obj-$(CONFIG_XEN_SCSI_FRONTEND) += xen-scsifront.o diff --git a/drivers/vhost/Makefile b/drivers/vhost/Makefile index 6b012b9..619e2cd 100644 --- a/drivers/vhost/Makefile +++ b/drivers/vhost/Makefile @@ -1,3 +1,4 @@ +ccflags-y := -D__CHECK_ENDIAN__ obj-$(CONFIG_VHOST_NET) += vhost_net.o vhost_net-y := net.o diff --git a/drivers/virtio/Makefil...

I run latest sparse from git on virtio drivers (turns out the version I had was rather outdated). This patchset fixes a couple of bugs this uncovered, and adds some annotations to make it sparse-clean. In particular, endian-ness is often tricky, so this patchset enabled endian-ness checks for sparse builds. Michael S. Tsirkin (10): virtio_console: drop unused config fields drm/virtio: fix

I run latest sparse from git on virtio drivers (turns out the version I had was rather outdated). This patchset fixes a couple of bugs this uncovered, and adds some annotations to make it sparse-clean. In particular, endian-ness is often tricky, so this patchset enabled endian-ness checks for sparse builds. Michael S. Tsirkin (10): virtio_console: drop unused config fields drm/virtio: fix

Hello, Jeremy: See the included patch. If it''s OK it''d be nice to get it into xen/stable-2.6.32.x branch. Thanks Nathanael! -- Pasi ----- Forwarded message from Nathanael Rensen <nathanael@polymorpheus.com> ----- From: Nathanael Rensen <nathanael@polymorpheus.com> To: Pasi Kärkkäinen <pasik@iki.fi> Cc: n_iwamatsu@jp.fujitsu.com Date: Mon, 3 Jan 2011

...- drivers/scsi/ufs/ufs_bsg.c | 3 +- drivers/scsi/ufs/ufshcd.c | 8 +- drivers/scsi/virtio_scsi.c | 2 +- drivers/scsi/vmw_pvscsi.c | 3 +- drivers/scsi/wd33c93.c | 2 +- drivers/scsi/xen-scsifront.c | 2 +- drivers/soc/qcom/socinfo.c | 16 +-- drivers/soc/tegra/pmc.c | 3 +- drivers/spi/spi-bcm2835aux.c | 4 +- drivers/spi/spi-fsl-cpm.c | 4 +- drivers/spi/spi-sprd-adi.c...

...- drivers/scsi/ufs/ufs_bsg.c | 3 +- drivers/scsi/ufs/ufshcd.c | 8 +- drivers/scsi/virtio_scsi.c | 2 +- drivers/scsi/vmw_pvscsi.c | 3 +- drivers/scsi/wd33c93.c | 2 +- drivers/scsi/xen-scsifront.c | 2 +- drivers/soc/qcom/socinfo.c | 16 +-- drivers/soc/tegra/pmc.c | 3 +- drivers/spi/spi-bcm2835aux.c | 4 +- drivers/spi/spi-fsl-cpm.c | 4 +- drivers/spi/spi-sprd-adi.c...

...- drivers/scsi/ufs/ufs_bsg.c | 3 +- drivers/scsi/ufs/ufshcd.c | 8 +- drivers/scsi/virtio_scsi.c | 2 +- drivers/scsi/vmw_pvscsi.c | 3 +- drivers/scsi/wd33c93.c | 2 +- drivers/scsi/xen-scsifront.c | 2 +- drivers/soc/qcom/socinfo.c | 16 +-- drivers/soc/tegra/pmc.c | 3 +- drivers/spi/spi-bcm2835aux.c | 4 +- drivers/spi/spi-fsl-cpm.c | 4 +- drivers/spi/spi-sprd-adi.c...

...- drivers/scsi/ufs/ufs_bsg.c | 3 +- drivers/scsi/ufs/ufshcd.c | 8 +- drivers/scsi/virtio_scsi.c | 2 +- drivers/scsi/vmw_pvscsi.c | 3 +- drivers/scsi/wd33c93.c | 2 +- drivers/scsi/xen-scsifront.c | 2 +- drivers/soc/qcom/socinfo.c | 16 +-- drivers/soc/tegra/pmc.c | 3 +- drivers/spi/spi-bcm2835aux.c | 4 +- drivers/spi/spi-fsl-cpm.c | 4 +- drivers/spi/spi-sprd-adi.c...

...- drivers/scsi/ufs/ufs_bsg.c | 3 +- drivers/scsi/ufs/ufshcd.c | 8 +- drivers/scsi/virtio_scsi.c | 2 +- drivers/scsi/vmw_pvscsi.c | 3 +- drivers/scsi/wd33c93.c | 2 +- drivers/scsi/xen-scsifront.c | 2 +- drivers/soc/qcom/socinfo.c | 16 +-- drivers/soc/tegra/pmc.c | 3 +- drivers/spi/spi-bcm2835aux.c | 4 +- drivers/spi/spi-fsl-cpm.c | 4 +- drivers/spi/spi-sprd-adi.c...

...meta data is interpreted by the file system and used to optimize certain journaling operations. These extensions are currently considered rather specialized an probably mandate a separate blk protocol. Another idea that has been mooted is supporting a scsi-level device channel protocol, and hence scsifront/back drivers. This would be useful for controlling more `exotic'' devices that need a richer set of operations than just read/write/barrier, e.g. a tape drive. It does introduce a whole load of fairly pointless scsi command creation and parsing at either end for the normal read/write case,...