#
286e947f |
| 03-Aug-2005 |
Justin T. Gibbs <gibbs@FreeBSD.org> |
Correct attribution in clause three to address the correct copyright holders. The license that was approved for my changes to this driver originally came from LSI, but the changes to the driver core
Correct attribution in clause three to address the correct copyright holders. The license that was approved for my changes to this driver originally came from LSI, but the changes to the driver core are not owned by LSI.
MFC: 1 day
show more ...
|
#
b0a2fdee |
| 10-Jul-2005 |
Scott Long <scottl@FreeBSD.org> |
Massive overhaul of MPT Fusion driver:
o Add timeout error recovery (from a thread context to avoid the deferral of other critical interrupts). o Properly recover commands across controller reset
Massive overhaul of MPT Fusion driver:
o Add timeout error recovery (from a thread context to avoid the deferral of other critical interrupts). o Properly recover commands across controller reset events. o Update the driver to handle events and status codes that have been added to the MPI spec since the driver was originally written. o Make the driver more modular to improve maintainability and support dynamic "personality" registration (e.g. SCSI Initiator, RAID, SAS, FC, etc). o Shorten and simplify the common I/O path to improve driver performance. o Add RAID volume and RAID member state/settings reporting. o Add periodic volume resynchronization status reporting. o Add support for sysctl tunable resync rate, member write cache enable, and volume transaction queue depth.
Sponsored by ---------------- Avid Technologies Inc: SCSI error recovery, driver re-organization, update of MPI library headers, portions of dynamic personality registration, and misc bug fixes.
Wheel Open Technologies: RAID event notification, RAID member pass-thru support, firmware upload/download support, enhanced RAID resync speed, portions of dynamic personality registration, and misc bug fixes.
Detailed Changes ================ mpt.c mpt_cam.c mpt_raid.c mpt_pci.c: o Add support for personality modules. Each module exports load, and unload module scope methods as well as probe, attach, event, reset, shutdown, and detach per-device instance methods
mpt.c mpt.h mpt_pci.c: o The driver now associates a callback function (via an index) with every transaction submitted to the controller. This allows the main interrupt handler to absolve itself of any knowledge of individual transaction/response types by simply calling the callback function "registered" for the transaction. We use a callback index instead of a callback function pointer in each requests so we can properly handle responses (e.g. event notifications) that are not associated with a transaction. Personality modules dynamically register their callbacks with the driver core to receive the callback index to use for their handlers.
o Move the interrupt handler into mpt.c. The ISR algorithm is bus transport and OS independent and thus had no reason to be in mpt_pci.c.
o Simplify configuration message reply handling by copying reply frame data for the requester and storing completion status in the original request structure.
o Add the mpt_complete_request_chain() helper method and use it to implement reset handlers that must abort transactions.
o Keep track of all pending requests on the new requests_pending_list in the softc.
o Add default handlers to mpt.c to handle generic event notifications and controller reset activities. The event handler code is largely the same as in the original driver. The reset handler is new and terminates any pending transactions with a status code indicating the controller needs to be re-initialized.
o Add some endian support to the driver. A complete audit is still required for this driver to have any hope of operating in a big-endian environment.
o Use inttypes.h and __inline. Come closer to being style(9) compliant.
o Remove extraneous use of typedefs.
o Convert request state from a strict enumeration to a series of flags. This allows us to, for example, tag transactions that have timed-out while retaining the state that the transaction is still in-flight on the controller.
o Add mpt_wait_req() which allows a caller to poll or sleep for the completion of a request. Use this to simplify and factor code out from many initialization routines. We also use this to sleep for task management request completions in our CAM timeout handler.
mpt.c: o Correct a bug in the event handler where request structures were freed even if the request reply was marked as a continuation reply. Continuation replies indicate that the controller still owns the request and freeing these replies prematurely corrupted controller state.
o Implement firmware upload and download. On controllers that do not have dedicated NVRAM (as in the Sun v20/v40z), the firmware image is downloaded to the controller by the system BIOS. This image occupies precious controller RAM space until the host driver fetches the image, reducing the number of concurrent I/Os the controller can processes. The uploaded image is used to re-program the controller during hard reset events since the controller cannot fetch the firmware on its own. Implementing this feature allows much higher queue depths when RAID volumes are configured.
o Changed configuration page accessors to allow threads to sleep rather than busy wait for completion.
o Removed hard coded data transfer sizes from configuration page routines so that RAID configuration page processing is possible.
mpt_reg.h: o Move controller register definitions into a separate file.
mpt.h: o Re-arrange includes to allow inlined functions to be defined in mpt.h.
o Add reply, event, and reset handler definitions.
o Add softc fields for handling timeout and controller reset recovery.
mpt_cam.c: o Move mpt_freebsd.c to mpt_cam.c. Move all core functionality, such as event handling, into mpt.c leaving only CAM SCSI support here.
o Revamp completion handler to provide correct CAM status for all currently defined SCSI MPI message result codes.
o Register event and reset handlers with the MPT core. Modify the event handler to notify CAM of bus reset events. The controller reset handler will abort any transactions that have timed out. All other pending CAM transactions are correctly aborted by the core driver's reset handler.
o Allocate a single request up front to perform task management operations. This guarantees that we can always perform a TMF operation even when the controller is saturated with other operations. The single request also serves as a perfect mechanism of guaranteeing that only a single TMF is in flight at a time - something that is required according to the MPT Fusion documentation.
o Add a helper function for issuing task management requests to the controller. This is used to abort individual requests or perform a bus reset.
o Modify the CAM XPT_BUS_RESET ccb handler to wait for and properly handle the status of the bus reset task management frame used to reset the bus. The previous code assumed that the reset request would always succeed.
o Add timeout recovery support. When a timeout occurs, the timed-out request is added to a queue to be processed by our recovery thread and the thread is woken up. The recovery thread processes timed-out command serially, attempting first to abort them and then falling back to a bus reset if an abort fails.
o Add calls to mpt_reset() to reset the controller if any handshake command, bus reset attempt or abort attempt fails due to a timeout.
o Export a secondary "bus" to CAM that exposes all volume drive members as pass-thru devices, allowing CAM to perform proper speed negotiation to hidden devices.
o Add a CAM async event handler tracking the AC_FOUND_DEVICE event. Use this to trigger calls to set the per-volume queue depth once the volume is fully registered with CAM. This is required to avoid hitting firmware limits on volume queue depth. Exceeding the limit causes the firmware to hang.
mpt_cam.h: o Add several helper functions for interfacing to CAM and performing timeout recovery.
mpt_pci.c: o Disable interrupts on the controller before registering and enabling interrupt delivery to the OS. Otherwise we risk receiving interrupts before the driver is ready to receive them.
o Make use of compatibility macros that allow the driver to be compiled under 4.x and 5.x.
mpt_raid.c: o Add a per-controller instance RAID thread to perform settings changes and query status (minimizes CPU busy wait loops).
o Use a shutdown handler to disable "Member Write Cache Enable" (MWCE) setting for RAID arrays set to enable MWCE During Rebuild.
o Change reply handler function signature to allow handlers to defer the deletion of reply frames. Use this to allow the event reply handler to queue up events that need to be acked if no resources are available to immediately ack an event. Queued events are processed in mpt_free_request() where resources are freed. This avoids a panic on resource shortage.
o Parse and print out RAID controller capabilities during driver probe.
o Define, allocate, and maintain RAID data structures for volumes, hidden member physical disks and spare disks.
o Add dynamic sysctls for per-instance setting of the log level, array resync rate, array member cache enable, and volume queue depth.
mpt_debug.c: o Add mpt_lprt and mpt_lprtc for printing diagnostics conditioned on a particular log level to aid in tracking down driver issues.
o Add mpt_decode_value() which parses the bits in an integer value based on a parsing table (mask, value, name string, tuples).
mpilib/*: o Update mpi library header files to latest distribution from LSI.
Submitted by: gibbs Approved by: re
show more ...
|
#
d4fcf3cb |
| 29-May-2005 |
Yoshihiro Takahashi <nyan@FreeBSD.org> |
Remove bus_{mem,p}io.h and related code for a micro-optimization on i386 and amd64. The optimization is a trivial on recent machines.
Reviewed by: -arch (imp, marcel, dfr)
|
Revision tags: release/5.4.0_cvs, release/5.4.0 |
|
#
6b9907e7 |
| 05-Mar-2005 |
Warner Losh <imp@FreeBSD.org> |
Use BUS_PROBE_DEFAULT for pci probe return value
|
Revision tags: release/4.11.0_cvs, release/4.11.0 |
|
#
d579f3e4 |
| 18-Dec-2004 |
Maxim Sobolev <sobomax@FreeBSD.org> |
Add support for FC929X, which apparently is just a PCI-X version of FC929.
MFC after: 3 days
|
Revision tags: release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0 |
|
#
5f96beb9 |
| 17-Mar-2004 |
Nate Lawson <njl@FreeBSD.org> |
Convert callers to the new bus_alloc_resource_any(9) API.
Submitted by: Mark Santcroos <marks@ripe.net> Reviewed by: imp, dfr, bde
|
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0 |
|
#
a89ec05e |
| 23-Dec-2003 |
Peter Wemm <peter@FreeBSD.org> |
Catch a few places where NULL (pointer) was used where 0 (integer) was expected.
|
Revision tags: release/4.9.0_cvs, release/4.9.0 |
|
#
e27951b2 |
| 02-Sep-2003 |
John Baldwin <jhb@FreeBSD.org> |
Use PCIR_BAR(x) instead of PCIR_MAPS.
Glanced over by: imp, gibbs Tested by: i386 LINT
|
#
aad970f1 |
| 24-Aug-2003 |
David E. O'Brien <obrien@FreeBSD.org> |
Use __FBSDID(). Also some minor style cleanups.
|
#
38d8c994 |
| 22-Aug-2003 |
Warner Losh <imp@FreeBSD.org> |
Prefer new location of pci include files (which have only been in the tree for two or more years now), except in a few places where there's code to be compatible with older versions of FreeBSD.
|
#
f6b1c44d |
| 01-Jul-2003 |
Scott Long <scottl@FreeBSD.org> |
Mega busdma API commit.
Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma.
Mega busdma API commit.
Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma. At the moment, this is used for the asynchronous busdma_swi and callback mechanism. Two lockfunc implementations are provided: busdma_lock_mutex() performs standard mutex operations on the mutex that is specified from lockfuncarg. dftl_lock() is a panic implementation and is defaulted to when NULL, NULL are passed to bus_dma_tag_create(). The only time that NULL, NULL should ever be used is when the driver ensures that bus_dmamap_load() will not be deferred. Drivers that do not provide their own locking can pass busdma_lock_mutex,&Giant args in order to preserve the former behaviour.
sparc64 and powerpc do not provide real busdma_swi functions, so this is largely a noop on those platforms. The busdma_swi on is64 is not properly locked yet, so warnings will be emitted on this platform when busdma callback deferrals happen.
If anyone gets panics or warnings from dflt_lock() being called, please let me know right away.
Reviewed by: tmm, gibbs
show more ...
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0 |
|
#
cc2f8c60 |
| 23-Feb-2003 |
David E. O'Brien <obrien@FreeBSD.org> |
PAGE_SIZE is unsigned on all our platforms, and is a long on some. So cast to u_long before printing out and use a matching specifier.
Tested on: sparc64
|
#
a163d034 |
| 19-Feb-2003 |
Warner Losh <imp@FreeBSD.org> |
Back out M_* changes, per decision of the TRB.
Approved by: trb
|
#
44956c98 |
| 21-Jan-2003 |
Alfred Perlstein <alfred@FreeBSD.org> |
Remove M_TRYWAIT/M_WAITOK/M_WAIT. Callers should use 0. Merge M_NOWAIT/M_DONTWAIT into a single flag M_NOWAIT.
|
Revision tags: release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
301472c2 |
| 24-Sep-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Code cleanup: use mpt_prt instead of device_printf.
|
#
7dec90bc |
| 23-Sep-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Parameterize MPT_MAX_REQUESTS based upon device type (FC has Global Credits of 1024- Ultra4 256). Rename 'requests' tag to 'request_pool' for clarity. Make sure we do correct xpt_freeze_simq/CAM_RELE
Parameterize MPT_MAX_REQUESTS based upon device type (FC has Global Credits of 1024- Ultra4 256). Rename 'requests' tag to 'request_pool' for clarity. Make sure we do correct xpt_freeze_simq/CAM_RELEASE_SIMQ if we run out of chip resources.
MFC after: 6 days
show more ...
|
#
aca01e38 |
| 23-Sep-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Recognize the single channel 2Gb card (FC919)- thanks to LSI Logic for pointing this out.
In mpt_intr, don't try and pop a reply queue element out *unless* the interrupt status says you might have o
Recognize the single channel 2Gb card (FC919)- thanks to LSI Logic for pointing this out.
In mpt_intr, don't try and pop a reply queue element out *unless* the interrupt status says you might have one.
MFC after: 1 week
show more ...
|
#
eae4a35f |
| 30-Aug-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Add 909A PCI id.
MFC after: 2 days
|
#
019717e0 |
| 23-Aug-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Pick a cleaner method (and put in a separate function) for finding the peer device on a dual board.
|
#
7104aeef |
| 21-Aug-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
A chunk of cleanup, both stylistic and substantive.
We now also read configuration information for the SCSI cards- this allows us to try and say what the speed settings now are.
Start, but not yet
A chunk of cleanup, both stylistic and substantive.
We now also read configuration information for the SCSI cards- this allows us to try and say what the speed settings now are.
Start, but not yet complete, the process of reorgs && #defines so that we can backport to RELENG_4 pretty soon.
show more ...
|
Revision tags: release/4.6.2_cvs, release/4.6.2 |
|
#
9b631363 |
| 12-Aug-2002 |
Matt Jacob <mjacob@FreeBSD.org> |
Add support for the LSI-Logic Fusion/MP architecture.
This is an architecture that present a thing message passing interface to the OS. You can query as to how many ports and what kind are attached
Add support for the LSI-Logic Fusion/MP architecture.
This is an architecture that present a thing message passing interface to the OS. You can query as to how many ports and what kind are attached and enable them and so on.
A less grand view is that this is just another way to package SCSI (SPI or FC) and FC-IP into a one-driver interface set.
This driver support the following hardware:
LSI FC909: Single channel, 1Gbps, Fibre Channel (FC-SCSI only) LSI FC929: Dual Channel, 1-2Gbps, Fibre Channel (FC-SCSI only) LSI 53c1020: Single Channel, Ultra4 (320M) (Untested) LSI 53c1030: Dual Channel, Ultra4 (320M)
Currently it's in fair shape, but expect a lot of changes over the next few weeks as it stabilizes.
Credits:
The driver is mostly from some folks from Jeff Roberson's company- I've been slowly migrating it to broader support that I it came to me as.
The hardware used in developing support came from:
FC909: LSI-Logic, Advansys (now Connetix) FC929: LSI-Logic 53c1030: Antares Microsystems (they make a very fine board!)
MFC after: 3 weeks
show more ...
|
#
9199c09a |
| 06-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Merge from head at r201628.
# This hasn't been tested, and there are at least three bad commits # that need to be backed out before the branch will be stable again.
|
#
ef360048 |
| 30-Dec-2009 |
John Baldwin <jhb@FreeBSD.org> |
Use a constant instead of a magic number for the flag that enables decoding of a device ROM.
|
#
11e9b8ba |
| 04-Aug-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC @196061
|
#
52c9ce25 |
| 10-Jul-2009 |
Scott Long <scottl@FreeBSD.org> |
Separate the parallel scsi knowledge out of the core of the XPT, and modularize it so that new transports can be created.
Add a transport for SATA
Add a periph+protocol layer for ATA
Add a driver
Separate the parallel scsi knowledge out of the core of the XPT, and modularize it so that new transports can be created.
Add a transport for SATA
Add a periph+protocol layer for ATA
Add a driver for AHCI-compliant hardware.
Add a maxio field to CAM so that drivers can advertise their max I/O capability. Modify various drivers so that they are insulated from the value of MAXPHYS.
The new ATA/SATA code supports AHCI-compliant hardware, and will override the classic ATA driver if it is loaded as a module at boot time or compiled into the kernel. The stack now support NCQ (tagged queueing) for increased performance on modern SATA drives. It also supports port multipliers.
ATA drives are accessed via 'ada' device nodes. ATAPI drives are accessed via 'cd' device nodes. They can all be enumerated and manipulated via camcontrol, just like SCSI drives. SCSI commands are not translated to their ATA equivalents; ATA native commands are used throughout the entire stack, including camcontrol. See the camcontrol manpage for further details. Testing this code may require that you update your fstab, and possibly modify your BIOS to enable AHCI functionality, if available.
This code is very experimental at the moment. The userland ABI/API has changed, so applications will need to be recompiled. It may change further in the near future. The 'ada' device name may also change as more infrastructure is completed in this project. The goal is to eventually put all CAM busses and devices until newbus, allowing for interesting topology and management options.
Few functional changes will be seen with existing SCSI/SAS/FC drivers, though the userland ABI has still changed. In the future, transports specific modules for SAS and FC may appear in order to better support the topologies and capabilities of these technologies.
The modularization of CAM and the addition of the ATA/SATA modules is meant to break CAM out of the mold of being specific to SCSI, letting it grow to be a framework for arbitrary transports and protocols. It also allows drivers to be written to support discrete hardware without jeopardizing the stability of non-related hardware. While only an AHCI driver is provided now, a Silicon Image driver is also in the works. Drivers for ICH1-4, ICH5-6, PIIX, classic IDE, and any other hardware is possible and encouraged. Help with new transports is also encouraged.
Submitted by: scottl, mav Approved by: re
show more ...
|