Revision tags: release/14.1.0 |
|
#
945c3ce4 |
| 19-Mar-2024 |
Chandrakanth patil <chandrakanth.patil@broadcom.com> |
mpi3mr: copyright year update to 2024
Reviewed by: imp Approved by: imp Differential revision: https://reviews.freebsd.org/D44429
|
Revision tags: release/13.3.0 |
|
#
2f2da217 |
| 20-Jan-2024 |
Chuck Silvers <chs@FreeBSD.org> |
mpi3mr: add missing terminator entry to mpi3mr_identifiers array
Reported by: KASAN Sponsored by: Netflix Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D43519
|
#
489eee0d |
| 29-Nov-2023 |
Alexander Motin <mav@FreeBSD.org> |
mpi3mr: Use template for main busdma tag.
Use the simpler template code for the parent busdma tag for all I/O to this card.
Reviewed by: mav, jhb, imp Differential Revision: https://reviews.freebs
mpi3mr: Use template for main busdma tag.
Use the simpler template code for the parent busdma tag for all I/O to this card.
Reviewed by: mav, jhb, imp Differential Revision: https://reviews.freebsd.org/D42607
show more ...
|
#
28a27434 |
| 29-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
mpi3mr: Add firmware version
Publish the firmware version on the card like we do for mps/mpr.
Sponsored by: Netflix Reviewed by: mav Differential Revision: https://reviews.freebsd.org/D42588
|
#
ee7c431c |
| 29-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
mpi3mr: Trivial trailing white space reduction
Sponsored by: Netflix
|
#
91d96135 |
| 29-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
mpi3mr: Honor the dma mask from IOCFacts
The number of signficant bits that are decoded are returned in the flags field of the IOCFacts structure from the device. Rather than assume the worst with
mpi3mr: Honor the dma mask from IOCFacts
The number of signficant bits that are decoded are returned in the flags field of the IOCFacts structure from the device. Rather than assume the worst with a pessimal 32-bit maximum, look at this value and pass it along to all the dma map creation requests.
A lof of those creations are repetitive and could just inherit from the base tag if we moved to the templated interface. This is called out as desireable future work not done at this time.
In addition, due to a chicken and an egg problem, we have to allocate some of the maps with a 32-bit loaddr. These are the ones we need to read iocfacts. And they are fine to be so restricted: they are little used after startup, and when they are used, bouncing is fine.
Sponsored by: Netflix Reviewed by: mav Differential Revision: https://reviews.freebsd.org/D42559
show more ...
|
#
7c491309 |
| 29-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
mpi3mr: Reduce the scope of the reset_mutext
Reduce the scope of reset_mutext to protect the msleep in the watch dog thread as well as the MPI3MR_FLAGS_SHUTDOWN bit. Use it to protect the wakeup in
mpi3mr: Reduce the scope of the reset_mutext
Reduce the scope of reset_mutext to protect the msleep in the watch dog thread as well as the MPI3MR_FLAGS_SHUTDOWN bit. Use it to protect the wakeup in mpi3mr_detach so this thread can exit sooner when we're trying to do an orderly shutdown. Optimize the flow to check the sleep and other conditions before going to sleep.
It's an open question if this should protect sc->unrecoverable, and if we should wakeup the watchdog thread when we set it. We might also want to move too booleans for the three flags that we have now in mpi3mr_flags. There are a number of U8s that should really be bools and we might want to also group them together to pack softc better.
Sponsored by: Netflix Reviewed by: mav Differential Revision: https://reviews.freebsd.org/D42539
show more ...
|
Revision tags: release/14.0.0 |
|
#
7e02c707 |
| 19-Oct-2023 |
Sumit Saxena <sumit@FreeBSD.org> |
mpi3mr: Move creation of watchdog to interupt config hook
Move creation of watchdog process from just before we configure the interrupt config hook to into the config hook itself. This prevents it f
mpi3mr: Move creation of watchdog to interupt config hook
Move creation of watchdog process from just before we configure the interrupt config hook to into the config hook itself. This prevents it from racing the config intr hook and doing an extra reset of the card. This extra reset is usually harmless, but sometimes it can prevent discovery of devices if done at just the wrong time. This can lead to no disks being registered in a box full of disks, for example. Starting it later eliminates this race, making discovery reliable.
Reviewed by: imp
show more ...
|
#
2d1d418e |
| 15-Jun-2023 |
Sumit Saxena <sumit.saxena@broadcom.com> |
mpi3mr: 3rd Generation Tri-Mode NVMe/SAS/SATA MegaRaid / eHBA
This is Broadcom's mpi3mr driver for FreeBSD version 8.6.0.2.0. The mpi3mr driver supports Broadcom SAS4116-based cards in the 9600 seri
mpi3mr: 3rd Generation Tri-Mode NVMe/SAS/SATA MegaRaid / eHBA
This is Broadcom's mpi3mr driver for FreeBSD version 8.6.0.2.0. The mpi3mr driver supports Broadcom SAS4116-based cards in the 9600 series: 9670W-16i, 9670-24i, 9660-16i, 9620-16i, 9600-24i, 9600-16i, 9600W-16e, 9600-16e, 9600-8i8e.
Initially only available as a module and on amd64/arm64, since that's how it has been tested to date. Future commits will add it to the kernel build and may expand the architectures it is supported on.
Co-authored-by: Chandrakanth Patil <chandrakanth.patil@broadcom.com> Feedback-by: ken (prior versions) Reviewed-by: imp RelNotes: yes Differential-Revision: https://reviews.freebsd.org/D36771 Differential-Revision: https://reviews.freebsd.org/D36772
show more ...
|