#
267654 |
|
19-Jun-2014 |
gjb |
Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
264950 |
|
25-Apr-2014 |
marius |
MFC: r260058
- Remove a redundant variable in mpt_pci_attach(). - #if 0 the currently unused paired port linking and unlinking of dual adapters. - Simplify MSI/MSI-X allocation and release. For a single one, we don't need to fiddle with the MSI/MSI-X count and pci_release_msi(9) is smart enough to just do nothing in case of INTx. - Canonicalize actions taken on attach failure and detach. - Remove the remainder of incomplete support for older FreeBSD versions.
|
#
245986 |
|
27-Jan-2013 |
marius |
MFC: r241875
Remove support for using Giant for locking within mpt(4). Finer grained locking has been working fine for ~5.5 years by now.
|
#
245983 |
|
27-Jan-2013 |
marius |
MFC: r241874
After r241858 (MFC'ed to stable/9 in r242286), remove the remainder of FreeBSD ~4 support from mpt(4).
|
#
233721 |
|
30-Mar-2012 |
marius |
MFC: r233403, r233404
- Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So rename the macros not present in mpi_cnfg.h to match the naming scheme in the latter and but suffix them with a _FB in order to not cause conflicts. - Like mpt_set_config_regs(), comment out mpt_read_config_regs() as the content of the registers read isn't actually used and both functions aren't exactly up to date regarding the possible layouts of the BARs (these function might be helpful for debugging though, so don't remove them completely). - Use DEVMETHOD_END. - Use NULL rather than 0 for pointers. - Remove an unusual check for the softc being NULL. - Remove redundant zeroing of the softc. - Remove an overly banal and actually partly incorrect as well as partly outdated comment regarding the allocation of the memory resource.
|
#
231629 |
|
13-Feb-2012 |
marius |
MFC: r231228
Remove extra newlines from panic messages.
|
#
231626 |
|
13-Feb-2012 |
marius |
Forced commit to denote that the commit message of r231623 actually should have read: MFC: r231518
Flesh out support for SAS1078 and SAS1078DE (which are said to actually be the same chip): - The I/O port resource may not be available with these. However, given that we actually only need this resource for some controllers that require their firmware to be up- and downloaded (which excludes the SAS1078{,DE}) just handle failure to allocate this resource gracefully when possible. While at it, generally put non-fatal resource allocation failures under bootverbose. - SAS1078{,DE} use a different hard reset protocol. - Add workarounds for the 36GB physical address limitation of scatter/ gather elements of these controllers.
Tested by: Slawa Olhovchenkov
PR: 149220 (remaining part)
|
#
231623 |
|
13-Feb-2012 |
marius |
MFC: r231518
Remove extra newlines from panic messages.
|
#
225736 |
|
22-Sep-2011 |
kensmith |
Copy head to stable/9 as part of 9.0-RELEASE release cycle.
Approved by: re (implicit)
|
#
224493 |
|
29-Jul-2011 |
marius |
- Staticize functions as appropriate and comment out unused ones. - Sprinkle some const where appropriate. - Consistently use target_id_t for the target parameter of mpt_map_physdisk() and mpt_is_raid_volume(). - Fix some whitespace bugs.
Approved by: re (kib)
|
#
223985 |
|
13-Jul-2011 |
marius |
- For SAS but neither FC nor SPI controllers default to using MSI (still allowing their use to be disabled via device hints though). This matches what the corresponding Linux driver provided by LSI does. Tested with SAS1064. - There's no need to keep track of the RIDs used. - Don't allocate MSI/MSI-X as RF_SHAREABLE. - Remove a comment which no longer applies since r209599. - Assign NULL rather than 0 to pointers.
MFC after: 1 month
|
#
220945 |
|
22-Apr-2011 |
marius |
Correct spelling.
Submitted by: brucec
|
#
215325 |
|
14-Nov-2010 |
marius |
Use the correct variable for determining the verbosity level in mpt_lprtc(). While at it, fix the whitespace of that macro.
PR: 149502 Submitted by: Andrew Boyer MFC after: 1 week
|
#
213147 |
|
24-Sep-2010 |
marius |
Take mpt_req_on_{free,pending}_list() out from under INVARIANTS as these are generally useful and not just for debugging.
|
#
209960 |
|
12-Jul-2010 |
marius |
- Make the maxsize parameter of the data buffer DMA tag match maxio, which was missed in r209599. Reported and tested by: Michael Moll - Declare mpt_dma_buf_alloc() static just like mpt_dma_buf_free(), both are used in mpt.c only.
Reviewed by: ken MFC after: r209599
|
#
209599 |
|
29-Jun-2010 |
ken |
Change the mpt driver to allow larger I/O sizes.
The mpt driver previously didn't report a 'maxio' size to CAM, and so the da(4) driver limited I/O sizes to DFLTPHYS (64K) by default. The number of scatter gather segments allowed, as reported to busdma, was (128K / PAGE_SIZE) + 1, or 33 on architectures with 4K pages.
Change things around so that we wait until we've determined how many segments the adapter can support before creating the busdma tag used for buffers, so we can potentially support more S/G segments and therefore larger I/O sizes.
Also, fix some things that were broken about the module unload path. It still gets hung up inside CAM, though.
mpt.c: Move some busdma initialization calls in here, and call them just after we've gotten the IOCFacts, and know how many S/G segments this adapter can support.
mpt.h: Get rid of MPT_MAXPHYS, it is no longer used.
Add max_cam_seg_cnt, which is used to report our maximum I/O size up to CAM.
mpt_cam.c: Use max_cam_seg_cnt to report our maximum I/O size to CAM.
Fix the locking in mpt_cam_detach().
mpt_pci.c: Pull some busdma initialization and teardown out and put it in mpt.c. We now delay it until we know many scatter gather segments the adapter can support, and therefore how to setup our busdma tags.
mpt_raid.c: Make sure we wake up the right wait channel to get the raid thread to wake up when we're trying to shut it down.
Reviewed by: gibbs, mjacob MFC after: 2 weeks
|
#
207287 |
|
27-Apr-2010 |
marius |
On sparc64 obtain the initiator ID to be used for SPI HBAs from the Open Firmware device tree in order to match what the PROM built-in driver uses. This is especially important when netbooting Fujitsu Siemens PRIMEPOWER250 as in that case the built-in driver isn't used and the port facts PortSCSIID defaults to 0, conflicting with the disk at the same address.
|
#
198262 |
|
20-Oct-2009 |
kan |
Use callout_init_mtx on FreeBSD versions recent enough. This closes the race where interrupt thread can complete the request for which timeout has fired and while mpt_timeout has blocked on mpt_lock.
Do a best effort to keep 4.x ang Giant-locked configurartions compiling still.
Reported by: ups Reviewed by: scottl
|
#
195534 |
|
10-Jul-2009 |
scottl |
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
|
#
186878 |
|
07-Jan-2009 |
marius |
Make the whole initiator mode part of mpt(4) endian-clean, specifically SPI controllers now also work in big-endian machines and some conversions relevant for FC and SAS controllers as well as support for ILP32 machines which all were omitted in previous attempts are now also implemented. The IOCTL-interface is intentionally left (and where needed actually changed) to be completely little-endian as otherwise we would have to add conversion code for every possible configuration page to mpt(4), which didn't seem the right thing to do, neither did converting only half of the user- interface to the native byte order. This change was tested on amd64 (SAS+SPI), i386 (SAS) and sparc64 (SAS+SPI). Due to lack of the necessary hardware the target mode code is still left to be made endian-clean.
Reviewed by: scottl MFC after: 1 month
|
#
178814 |
|
06-May-2008 |
jhb |
Add a new personality to mpt(4) devices to allow userland applications to perform various operations on a controller. Specifically, for each mpt(4) device, create a character device in devfs which accepts ioctl requests for reading and writing configuration pages and performing RAID actions.
MFC after: 1 week Reviewed by: scottl
|
#
178725 |
|
02-May-2008 |
jkim |
Restore multi-release tradition of the driver.
Reviewed by: mjacob
|
#
172842 |
|
21-Oct-2007 |
julian |
fix up some code for older systems changed by accident in the last commit this whole support for systems earlier than 5.0 should probably be removed but I'll at least FIX it before removing it, so that CVS has it right.
|
#
172836 |
|
20-Oct-2007 |
julian |
Rename the kthread_xxx (e.g. kthread_create()) calls to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first.
I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
|
#
171842 |
|
14-Aug-2007 |
scottl |
Move callout initialization to the proper spot. This prevents panics during error recovery.
Approved by: re Found by: kan
|
#
170252 |
|
03-Jun-2007 |
scottl |
mpt.c: mpt.h: Add support for reading extended configuration pages. mpt_cam.c: Do a top level topology scan on the SAS controller. If any SATA device are discovered in this scan, send a passthrough FIS to set the write cache. This is controllable through the following tunable at boot:
hw.mpt.enable_sata_wc: -1 = Do not configure, use the controller default 0 = Disable the write cache 1 = Enable the write cache
The default is -1. This tunable is just a hack and may be deprecated in the future.
Turning on the write cache alleviates the write performance problems with SATA that many people have observed. It is not recommend for those who value data reliability! I cannot stress this strongly enough. However, it is useful in certain circumstances, and it brings the performence in line with what a generic SATA controller running under the FreeBSD ATA driver provides (and the ATA driver has had the WC enabled by default for years).
|
#
169293 |
|
05-May-2007 |
mjacob |
Make this driver MP safe and still be a multi-release driver.
Obtained from: 99% of the work done by Scott Long. MFC after: 3 days
|
#
167426 |
|
10-Mar-2007 |
mjacob |
feedback from RELENG_5 port
|
#
166935 |
|
23-Feb-2007 |
mjacob |
Redo previous newbus related change to be kinder to multi-release support.
|
#
165814 |
|
05-Jan-2007 |
mjacob |
(commented out) multipath fault injection code.
Some code to make diffs with RELENG_6 easier.
|
#
164998 |
|
07-Dec-2006 |
mjacob |
PH! Forgot to do my cross-compile check. Also now rearranged things so the ENDIAN defines are consistent between mpt.h and mpt.c.
|
#
164990 |
|
07-Dec-2006 |
mjacob |
MFP4: principally to reapply tagged command support to FC and SAS cards.
|
#
164838 |
|
02-Dec-2006 |
mjacob |
Forced commit: previous revision just correctly reflected that the number of attached devices is 16 bits wide, not 8 bits wide.
|
#
164837 |
|
02-Dec-2006 |
mjacob |
Fix a debug message which didn't quite get it right about data direction.
Fix things to use the LSI-Logic Fusion Library mask and shift names for offset and sync, no matter how awkward they are, in preference to just plain numbers.
|
#
164416 |
|
19-Nov-2006 |
mjacob |
Play it safe and make MSI and MSI-X an option you have to turn on for MPT.
|
#
164305 |
|
15-Nov-2006 |
jhb |
Add MSI support to em(4), bce(4), and mpt(4). For now, we only support devices that support a maximum of 1 message, and we use that 1 message instead of the INTx rid 0 IRQ with the same interrupt handler, etc.
|
#
162133 |
|
07-Sep-2006 |
mjacob |
Create a 'ready' handler for each personality. The purpose of this handler is to able to be called after *all* attach and enable events are done.
We establish a SYSINIT hook to call this handler. The current usage for it is to add scsi target resources *after* all enables are done. There seems to be some dependencies between different halves of a dual-port with respect to target mode.
Put in more meaningful event messages for some events- in particular QUEUE FULL events so we can see what the queue depth was when the IOC sent us this message.
MFC after: 1 week
|
#
160397 |
|
16-Jul-2006 |
mjacob |
Add sysctl information about things like WWNN/WWPN.
MFC after: 2 weeks
|
#
160391 |
|
15-Jul-2006 |
mjacob |
If the card has target mode enabled, and we hang out ELS buffers but *don't* hang out commands, we hang folks on the SAN because the LSI-Logic f/w apparently sends back BUSY or QFULL or some darn thing.
If we add command buffers, we have to respond to them sensibly even if we don't have any upstream listeners (scsi_targ or scsi_targ_bh), so put in some local command reponse stuff.
MFC after: 2 weeks
|
#
160290 |
|
12-Jul-2006 |
mjacob |
Fix config page writes to not strip out the attributes when you actually go write the config page. This fixes the long standing problem about updating NVRAM on Fibre Channel cards and seems so far to not break SPI config page writes.
Put back role setting into mpt. That is, you can set a desired role for mpt as a hint. On the next reboot, it'll pick that up and redo the NVRAM settings appropriately and warn you that this won't take effect until the next reboot. This saves people the step of having to find a BIOS utilities disk to set target and/or initiator role for the MPT cards.
|
#
159919 |
|
25-Jun-2006 |
mjacob |
Major Fixes:
Don't enable/disable I/O space except for SAS adapters. This fixes a problem with VMware 4.5 Workstation.
Fix an egregious bug introduced to target mode so it actually will not panic when you first enable a lun.
Minor fixes:
Take more infor from port facts and configuration pages.
MFC after: 1 week
|
#
159312 |
|
05-Jun-2006 |
mjacob |
Do some source && comment cleanup.
Clean out the abortive start to homegrown, per-mpt, Domain Validation. This should really be done at a higher level.
Use the PIM_SEQSCAN flag for U320- this seems to correct cases of being unable to consistently negotiate U320 in the cases where I'd seen this before.
Between this and other recent checkins, this driver is pretty close to being ready for MFC.
Reviewed by: scottl, ken, scsi@ MFC after: 1 week
|
#
159179 |
|
02-Jun-2006 |
mjacob |
Make the code able to compile again in RELENG_4.
|
#
159178 |
|
02-Jun-2006 |
mjacob |
More checkpointing on the way toward really (finally) fixing speed negotiation.
Also fix the mpt_execute_req function to actually match mpt_execute_req_a64. This may explain why i386 users were having more grief.
|
#
159052 |
|
29-May-2006 |
mjacob |
Add acknowledgements to LSI-Logic for support
|
#
159049 |
|
29-May-2006 |
mjacob |
Add a MPT_PRT_NEGOTIATION print level.
|
#
158982 |
|
27-May-2006 |
mjacob |
Work in progress toward fixing IM checked in after having lost one set to a peninsula power failure last night. After this, I can see both submembers and the raid volumes again, but speed negotiation is still broken.
Add a mpt_raid_free_mem function to centralize the resource reclaim and fixed a small memory leak.
Remove restriction on number of targets for systems with IM enabled- you can have setups that have both IM volumes as well as other devices.
Fix target id selection for passthru and nonpastrhu cases.
Move complete command dumpt to MPT_PRT_DEBUG1 level so that just setting debug level gets mostly informative albeit less verbose dumping.
|
#
158935 |
|
26-May-2006 |
mjacob |
Get most of the way back to having Integrated Mirroring work again- the addition of target mode support broke it massively.
|
#
158933 |
|
26-May-2006 |
mjacob |
Fix spellings. Prototype mpt_dump_request. Add a 'raid_enabled' tag.
|
#
158651 |
|
16-May-2006 |
phk |
Since DELAY() was moved, most <machine/clock.h> #includes have been unnecessary.
|
#
158278 |
|
04-May-2006 |
mjacob |
Remove MPT_PRT_INVARIANT- it was a silly idea.
|
#
157662 |
|
11-Apr-2006 |
mjacob |
A large set of changes:
+ Add boatloads of KASSERTs and *really* check out more locking issues (to catch recursions when we actually go to real locking in CAM soon). The KASSERTs also caught lots of other issues like using commands that were put back on free lists, etc.
+ Target mode: role setting is derived directly from port capabilities. There is no need to set a role any more. Some target mode resources are allocated early on (ELS), but target command buffer allocation is deferred until the first lun enable.
+ Fix some breakages I introduced with target mode in that some commands are *repeating* commands. That is, the reply shows up but the command isn't really done (we don't free it). We still need to take it off the pending list because when we resubmit it, bad things then happen.
+ Fix more of the way that timed out commands and bus reset is done. The actual TMF response code was being ignored.
+ For SPI, honor BIOS settings. This doesn't quite fix the problems we've seen where we can't seem to (re)negotiate U320 on all drives but avoids it instead by letting us honor the BIOS settings. I'm sure this is not quite right and will have to change again soon.
|
#
157354 |
|
01-Apr-2006 |
mjacob |
Fix some of the previus changes 'better'.
There's something strange going on with async events. They seem to be be treated differently for different Fusion implementations. Some will really tell you when it's okay to free the request that started them. Some won't. Very disconcerting.
This is particularily bad when the chip (FC in this case) tells you in the reply that it's not a continuation reply, which means you can free the request that its associated with. However, if you do that, I've found that additional async event replies come back for that message context after you freed it. Very Bad Things Happen.
Put in a reply register debounce. Warn about out of range context indices. Use more MPILIB defines where possible. Replace bzero with memset. Add tons more KASSERTS. Do a *lot* more request free list auditting and serial number usages. Get rid of the warning about the short IOC Facts Reply. Go back to 16 bits of context index.
Do a lot more target state auditting as well. Make a tag out of not only the ioindex but the request index as well and worry less about keeping a full serial number.
|
#
157117 |
|
25-Mar-2006 |
mjacob |
Some fairly major changes to this driver.
A) Fibre Channel Target Mode support mostly works (SAS/SPI won't be too far behind). I'd say that this probably works just about as well as isp(4) does right now. Still, it and isp(4) and the whole target mode stack need a bit of tightening.
B) The startup sequence has been changed so that after all attaches are done, a set of enable functions are called. The idea here is that the attaches do whatever needs to be done *prior* to a port being enabled and the enables do what need to be done for enabling stuff for a port after it's been enabled.
This means that we also have events handled by their proper handlers as we start up.
C) Conditional code that means that this driver goes back all the way to RELENG_4 in terms of support.
D) Quite a lot of little nitty bug fixes- some discovered by doing RELENG_4 support. We've been living under Giant *waaaayyyyy* too long and it's made some of us (me) sloppy.
E) Some shutdown hook stuff that makes sure we don't blow up during a reboot (like by the arrival of a new command from an initiator).
There's been some testing and LINT checking, but not as complete as would be liked. Regression testing with Fusion RAID instances has not been possible. Caveat Emptor.
Sponsored by: LSI-Logic.
|
#
156400 |
|
07-Mar-2006 |
mjacob |
Add a serial number for requests so we don't just depend on a request pointer to try and do forensics on what has occurred.
|
#
156000 |
|
25-Feb-2006 |
mjacob |
Role a microrev of the MPI Library in preparation for target mode work.
Make my portions of the license clearer.
Thank Chris Ellsworth for his support in getting a bunch of this done.
|
#
155521 |
|
10-Feb-2006 |
mjacob |
Do initial cut of SAS HBA support. These controllers (106X) seem to support automatically both SATA and SAS drives. The async SAS event handling we catch but ignore at present (so automagic attach/detach isn't hooked up yet).
Do 64 bit PCI support- we can now work on systems with > 4GB of memory.
Do large transfer support- we now can support up to reported chain depth, or the length of our request area. We simply allocate additional request elements when we would run out of room for chain lists.
Tested on Ultra320, FC and SAS controllers on AMD64 and i386 platforms. There were no RAID cards available for me to regression test.
The error recovery for this driver still is pretty bad.
|
#
153072 |
|
04-Dec-2005 |
ru |
Fix -Wundef.
|
#
152444 |
|
15-Nov-2005 |
kan |
Keep track of volumes in non-optimal state and expose a simple count of volumes that might need administrator attention through device specific sysctl to simplify device monitoring.
Submitted by: Deomid Ryabkov <myself at rojer dot pp dot ru>
|
#
148679 |
|
03-Aug-2005 |
gibbs |
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
|
#
147883 |
|
10-Jul-2005 |
scottl |
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
|
#
139749 |
|
05-Jan-2005 |
imp |
Start each of the license/copyright comments with /*-, minor shuffle of lines
|
#
115778 |
|
03-Jun-2003 |
mjacob |
Update MPILIB from code received from LSI. Make changes in the rest of the driver based upon some somewhat gratuitous name changes.
|
#
102822 |
|
01-Sep-2002 |
mjacob |
Fix things so that:
a) we don't believe what the board tells us all the time (if the BIOS hasn't run, port page 2 and port page 0 tend to be garbage)
b) add the missing code to set parameters for the SPI cards.
MFC after: 0 days
|
#
102199 |
|
20-Aug-2002 |
mjacob |
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.
|
#
101704 |
|
11-Aug-2002 |
mjacob |
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
|