user/sven/linux.git/drivers/block/cciss.c, branch v3.0.26

block: add and use scsi_blk_cmd_ioctl

2012-01-26T01:24:54Z

commit 577ebb374c78314ac4617242f509e2f5e7156649 upstream. Introduce a wrapper around scsi_cmd_ioctl that takes a block device. The function will then be enhanced to detect partition block devices and, in that case, subject the ioctls to whitelisting. Cc: linux-scsi@vger.kernel.org Cc: Jens Axboe Cc: James Bottomley Signed-off-by: Paolo Bonzini Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman

cciss: add small delay when using PCI Power Management to reset for kump

2011-11-11T17:36:58Z

commit ab5dbebe33e0c353e8545f09c34553ac3351dad6 upstream. The P600 requires a small delay when changing states. Otherwise we may think the board did not reset and we bail. This for kdump only and is particular to the P600. Signed-off-by: Jens Axboe Signed-off-by: Greg Kroah-Hartman

cciss: fix compile issue

2011-05-06T14:27:00Z

drivers/block/cciss.c: In function ‘cciss_send_reset’: drivers/block/cciss.c:2515:2: error: implicit declaration of function ‘fill_cmd’ drivers/block/cciss.c: At top level: drivers/block/cciss.c:2531:12: error: conflicting types for ‘fill_cmd’ drivers/block/cciss.c:2534:1: note: an argument type that has a default promotion can’t match an empty parameter name list declaration drivers/block/cciss.c:2515:18: note: previous implicit declaration of ‘fill_cmd’ was here make[1]: *** [drivers/block/cciss.o] Error 1 make: *** [drivers/block/cciss.o] Error 2 Move fill_cmd() to above where it is first used. Signed-off-by: Jens Axboe

cciss: add cciss_tape_cmds module paramter

2011-05-06T14:23:59Z

This is to allow number of commands reserved for use by SCSI tape drives and medium changers to be adjusted at driver load time via the kernel parameter cciss_tape_cmds, with a default value of 6, and a range of 2 - 16 inclusive. Previously, the driver limited the number of commands which could be queued to the SCSI half of the the driver to only 2. This is to fix the problem that if you had more than two tape drives, you couldn't, for example, erase or rewind them all at the same time. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: do not use bit 2 doorbell reset

2011-05-06T14:23:58Z

It causes NMIs which are undesirable at best, unsurvivable at worst. Prefer the soft reset instead. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: do not attempt PCI power management reset method if we know it won't work.

2011-05-06T14:23:57Z

Just go straight to the soft-reset method instead. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: remove superfluous sleeps around reset code

2011-05-06T14:23:56Z

Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: do soft reset if hard reset is broken

2011-05-06T14:23:56Z

on driver load, if reset_devices is set, and the hard reset attempts fail, try to bring up the controller to the point that a command can be sent, and send it a soft reset command, then after the reset undo whatever driver initialization was done to get it to the point to take a command, and re-do it after the reset. This is to get kdump to work on all the "non-resettable" controllers (except 64xx controllers which can't be reset due to the potentially shared cache module.) Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: use new doorbell-bit-5 reset method

2011-05-06T14:23:55Z

The bit-2-doorbell reset method seemed to cause (survivable) NMIs on some systems and (unsurvivable) IOCK NMIs on some G7 servers. Firmware guys implemented a new doorbell method to alleviate these problems triggered by bit 5 of the doorbell register. We want to use it if it's available. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe

cciss: increase timeouts for post-reset no-ops

2011-05-06T14:23:54Z

Just to reduce the messages about timeouts that appear. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe