search for: megasas

Now that we can use SCSI command emulation without using the SCSI disk abstraction we can easily add it to the megasas HBA. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/megasas.c | 88 +++++++++++++++++++++++++++++++++++----------------------- 1 files changed, 53 insertions(+), 35 deletions(-) diff --git a/hw/megasas.c b/hw/megasas.c index a57e8e0..f32b313 100644 --- a/hw/megasas.c +++ b/hw/me...

Now that we can use SCSI command emulation without using the SCSI disk abstraction we can easily add it to the megasas HBA. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/megasas.c | 88 +++++++++++++++++++++++++++++++++++----------------------- 1 files changed, 53 insertions(+), 35 deletions(-) diff --git a/hw/megasas.c b/hw/megasas.c index a57e8e0..f32b313 100644 --- a/hw/megasas.c +++ b/hw/me...

...> > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > > > can be used with unmodified nvme host OS drivers. > > > > > > > > > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > > > > > back using specialized QEMU emulation + eventfd based LIO fabric driver, > > > > > and got it working with Linux + MSFT guests. > > > > > > > > > > Doing something similar for nvme would (potentially) be on par with...

...> > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > > > can be used with unmodified nvme host OS drivers. > > > > > > > > > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > > > > > back using specialized QEMU emulation + eventfd based LIO fabric driver, > > > > > and got it working with Linux + MSFT guests. > > > > > > > > > > Doing something similar for nvme would (potentially) be on par with...

...rnel memory: 592k freed [ 24.450181] Write protecting the kernel read-only data: 4308k Loading, please wait... [ 13.305934] udev: starting version 158 [ 13.684776] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009) [ 14.969875] SCSI subsystem initialized [ 14.971469] megasas: 00.00.04.01 Thu July 24 11:41:51 PST 2008 [ 14.971489] megasas: 0x1000:0x0060:0x1028:0x1f0c: bus 3:slot 0:func 0 [ 14.971509] xen_allocate_pirq: returning irq 15 for gsi 15 [ 14.971514] Already setup the GSI :15 [ 14.971516] megaraid_sas 0000:03:00.0: PCI INT A -> Link[LK00] -> GSI 1...

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

This patch add an emulation for the LSI MegaRAID SAS HBA. It is using SG_IO to forward / pass through SCSI commands to the underlying block driver, so no emulation is done currently. Signed-off-by: Hannes Reinecke <hare at suse.de> --- Makefile.hw | 2 +- hw/megasas.c | 1134 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/pci_ids.h | 2 + 3 files changed, 1137 insertions(+), 1 deletions(-) create mode 100644 hw/megasas.c diff --git a/Makefile.hw b/Makefile.hw index de1db31..cae35f9 100644 --- a/Makefile.hw +++ b/Makefile.hw @@ -33,7 +33,7 @...

This patch add an emulation for the LSI MegaRAID SAS HBA. It is using SG_IO to forward / pass through SCSI commands to the underlying block driver, so no emulation is done currently. Signed-off-by: Hannes Reinecke <hare at suse.de> --- Makefile.hw | 2 +- hw/megasas.c | 1134 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/pci_ids.h | 2 + 3 files changed, 1137 insertions(+), 1 deletions(-) create mode 100644 hw/megasas.c diff --git a/Makefile.hw b/Makefile.hw index de1db31..cae35f9 100644 --- a/Makefile.hw +++ b/Makefile.hw @@ -33,7 +33,7 @...

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

Hello Asterisk community, I'm experiencing some problems with a Digium TE4XXP, the thing is that i'm sharing IRQ with some megasas device: 169: 69917985 0 0 0 0 0 0 0 IO-APIC-level megasas, wct4xxp I've been searching here: http://ubuntuforums.org/showthread.php?t=254623 Should i try in the pass this parameter in the boot Kernel "*pci=routeirq*" jus...

...gt;> virtio-nvme(guest) >> vhost_nvme(host) >> LIO-NVMe-target >> > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using specialized QEMU emulation + eventfd based LIO fabric driver, > and got it working with Linux + MSFT guests. Are the patches already in qemu upstream and LIO upstream? I found you played it in 2010. Is it? [QEMU-KVM]: Megasas + TCM_Loop + SG_IO into Windows XP guest...

...gt;> virtio-nvme(guest) >> vhost_nvme(host) >> LIO-NVMe-target >> > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using specialized QEMU emulation + eventfd based LIO fabric driver, > and got it working with Linux + MSFT guests. Are the patches already in qemu upstream and LIO upstream? I found you played it in 2010. Is it? [QEMU-KVM]: Megasas + TCM_Loop + SG_IO into Windows XP guest...

...; | SATA | | SCSI | | NVMe | | .... | > '------------' '-----------' '------------' '---------------' > > Looks fine. Btw, after chatting with Dr. Hannes this week at SDC here are his original rts-megasas -v6 patches from Feb 2013. Note they are standalone patches that require a sufficiently old enough LIO + QEMU to actually build + function. https://github.com/Datera/rts-megasas/blob/master/rts_megasas-qemu-v6.patch https://github.com/Datera/rts-megasas/blob/master/rts_megasas-fabric-v6.patch Fo...

...is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write through SCSI device sda: 2435317760 512-byte hdwr sectors (1246883 MB) sda: Write Protect is off sda: Mode Sense: 1f 00 00 08 SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sd 0:2:0:0: Attached scsi disk sda megasas: 0x1028:0x0015:0x1028:0x1f01: bus 16:slot 14:func 0 GSI 21 sharing vector 0x62 and IRQ 21 ACPI: PCI Interrupt 0000:10:0e.0[A] -> GSI 18 (level, low) -> IRQ 98 megasas: FW now in Ready state

Hi Alex, I've been playing around with VFIO and megasas (of course). What I did now was switching between VFIO and 'normal' operation, ie emulated access. megasas is happily running under VFIO, but when I do an emergency stop like killing the Qemu session the PCI device is not properly reset. IE when I load 'megaraid_sas' after unbind...

Hi Alex, I've been playing around with VFIO and megasas (of course). What I did now was switching between VFIO and 'normal' operation, ie emulated access. megasas is happily running under VFIO, but when I do an emergency stop like killing the Qemu session the PCI device is not properly reset. IE when I load 'megaraid_sas' after unbind...

...spci(on CentOS HVM). 00:06.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS However the driver is not getting attached properly and fails with the following error ======================================================================================= "dmesg" of HVM CentOS megasas: Failed to init firmware ACPI: PCI interrupt for device 0000:00:06.0 disabled "/var/log/messages" pciback 0000:02:0e.0: seizing device PCI: Enabling device 0000:02:0e.0 (0190 -> 0192) ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 66 (level, low) -> IRQ 25 ACPI: PCI interrupt fo...

Hi all, we got a new test system here and I just also tested btrfs raid6 on that. Write performance is slightly lower than hw-raid (LSI megasas) and md-raid6, but it probably would be much better than any of these two, if it wouldn''t read all the during the writes. Is this a known issue? This is with linux-3.9.2. Thanks, Bernd -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a...

...e to virtio-blk. So it's potentially > a very good choice for a cloud provider that wants to support Windows guests > (together with e.g. a fast SAS emulated controller to replace virtio-scsi, > and emulated igb or ixgbe to replace virtio-net). vhost-nvme patches are learned from rts-megasas, which could possibly be a fast SAS emulated controller. https://github.com/Datera/rts-megasas > > Which features are supported by NVMe and not virtio-blk? Rob (CCed), Would you share whether google uses any NVMe specific feature? Thanks.