linux.git/drivers/block/cciss.c, branch v2.6.16

[PATCH] cciss: softirq handler needs to save interrupt flags

2006-02-07T18:11:19+00:00

The softirq rq completion handler needs to save/restore interrupt flags
appropriately.

Signed-off-by: Jens Axboe 
Signed-off-by: Linus Torvalds

[PATCH] drivers/block: Replace pci_module_init() with pci_register_driver()

2006-01-09T20:13:22+00:00

Replace obsolete pci_module_init() with pci_register_driver().

Signed-off-by: Richard Knutsson 
Signed-off-by: Greg Kroah-Hartman

[BLOCK] CCISS: update for blk softirq completions

2006-01-09T15:04:06+00:00

Signed-off-by: Jens Axboe

[PATCH] cciss: avoid defining useless MAJOR_NR macro

2006-01-09T04:14:09+00:00

This sneaked in with one of the updates.

Signed-off-by: Adrian Bunk 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] drivers/block: Use ARRAY_SIZE macro

2006-01-09T04:14:08+00:00

Use ARRAY_SIZE macro instead of sizeof(x)/sizeof(x[0]) and remove a
duplicate of ARRAY_SIZE. Some trailing whitespaces are also removed.

drivers/block/acsi* has been left out as it's marked BROKEN.

Signed-off-by: Tobias Klauser 
Cc: Jens Axboe 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] cciss: adds MSI and MSI-X support

2006-01-09T04:14:00+00:00

This creates a new function, cciss_interrupt_mode called from
cciss_pci_init.  This function determines what type of interrupt vector to
use, i.e., MSI, MSI-X, or IO-APIC.

One noticeable difference is changing the interrupt field of the controller
struct to an array of 4 unsigned ints.  The Smart Array HW is capable of
generating 4 distinct interrupts depending on the transport method in use
during operation.  These are:

#define DOORBELL_INT 0
Used to notify the contoller of configuration updates. We only use
this feature when in polling mode.

#define PERF_MODE_INT 0
Used when the controller is in Performant Mode.

#define SIMPLE_MODE_INT 2
Used when the controller is in Simple Mode (current Linux implementation).

#define MEMQ_INT_MODE 3
Not used.

When using IO-APIC interrupts these 4 lines are OR'ed together so when any
one fires an interrupt an is generated.  In MSI or MSI-X mode this hardware
OR'ing is ignored.  We must register for our interrupt depending on what
mode the controller is running.  For Linux we use SIMPLE_MODE_INT
exclusively at this time.  Please consider this for inclusion.

Signed-off-by: Mike Miller 
Cc: Jens Axboe 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Add block_device_operations.getgeo block device method

2006-01-09T04:13:54+00:00

HDIO_GETGEO is implemented in most block drivers, and all of them have to
duplicate the code to copy the structure to userspace, as well as getting
the start sector.  This patch moves that to common code [1] and adds a
->getgeo method to fill out the raw kernel hd_geometry structure.  For many
drivers this means ->ioctl can go away now.

[1] the s390 block drivers are odd in this respect.  xpram sets ->start
    to 4 always which seems more than odd, and the dasd driver shifts
    the start offset around, probably because of it's non-standard
    sector size.

Signed-off-by: Christoph Hellwig 
Cc: Jens Axboe 
Cc: 
Cc: Jeff Dike 
Cc: Paolo Giarrusso 
Cc: Bartlomiej Zolnierkiewicz 
Cc: Neil Brown 
Cc: Markus Lidel 
Cc: Russell King 
Cc: David Woodhouse 
Cc: Martin Schwidefsky 
Cc: James Bottomley 
Signed-off-by: Adrian Bunk 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[BLOCK] add @uptodate to end_that_request_last() and @error to rq_end_io_fn()

2006-01-06T08:49:03+00:00

add @uptodate argument to end_that_request_last() and @error
to rq_end_io_fn().  there's no generic way to pass error code
to request completion function, making generic error handling
of non-fs request difficult (rq->errors is driver-specific and
each driver uses it differently).  this patch adds @uptodate
to end_that_request_last() and @error to rq_end_io_fn().

for fs requests, this doesn't really matter, so just using the
same uptodate argument used in the last call to
end_that_request_first() should suffice.  imho, this can also
help the generic command-carrying request jens is working on.

Signed-off-by: tejun heo 
Signed-Off-By: Jens Axboe

[PATCH] cciss: fix for deregister_disk

2005-12-13T06:31:16+00:00

This patch adds setting our drv->queue = NULL back in deregister_disk.  The
drv->queue is part of our controller struct.  blk_cleanup_queue works only
on the queue in the gendisk struct.

Signed-off-by: Mike Miller 
Cc: Jens Axboe 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] cciss: double put_disk()

2005-12-12T16:57:43+00:00

This undoes the put_disk patch I sent in before.

If I had been paying attention I would have seen that we call put_disk
from free_hba during driver unload.  That's the only time we want to
call it.  If it's called from deregister disk we may remove the
controller (cNd0) unintentionally.

Signed-off-by: Mike Miller 
Signed-off-by: Jens Axboe 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds