src/sys/dev/ipmi, branch stable/13 FreeBSD source tree change ipmi watchdog to awlays stop when system is halted 2024-02-17T19:22:08+00:00 Andriy Gapon avg@FreeBSD.org 2023-01-03T17:26:45+00:00 9ca7451d86dcf8fb072491028e3b0fb50b2299c5 That is, wd_shutdown_countdown value is ignored when halting. A halted system should remain halted for as long as needed until a power cycle, so the watchdog should not reset the system. (cherry picked from commit 8fdb26160160c4507eb2f644a982a3e05984cdf6) 
That is, wd_shutdown_countdown value is ignored when halting.

A halted system should remain halted for as long as needed until
a power cycle, so the watchdog should not reset the system.

(cherry picked from commit 8fdb26160160c4507eb2f644a982a3e05984cdf6)
fix signature of ipmi_shutdown_event 2024-02-17T19:22:08+00:00 Andriy Gapon avg@FreeBSD.org 2023-01-03T17:22:21+00:00 392953c490da99739feeb51e8917325ba30b802a The function had a signature of watchdog_fn while in fact it is used as shutdown_fn. (cherry picked from commit 90dc7889825d13290955d0eb7e1fb4388c0a0135) 
The function had a signature of watchdog_fn while in fact it is used as
shutdown_fn.

(cherry picked from commit 90dc7889825d13290955d0eb7e1fb4388c0a0135)
pci_cfgreg: Add a PCI domain argument to the low-level register API 2024-01-18T23:27:22+00:00 John Baldwin jhb@FreeBSD.org 2023-11-29T18:31:47+00:00 325e60b1e6527a6bdc9e9bca2c9ad5ff0b4f22fd This commit changes the API of pci_cfgreg(read|write) to add a domain argument (referred to as a segment in ACPI parlance) (note that this is not the same as a NUMA domain, but something PCI-specific). This does not yet enable access to domains other than 0, but updates the API to support domains. Places that use hard-coded bus/slot/function addresses have been updated to hardcode a domain of 0. A few places that have the PCI domain (segment) available such as the acpi_pcib_acpi.c Host-PCI bridge driver pass the PCI domain. The hpt27xx(4) and hptnr(4) drivers fail to attach to a device not on domain 0 since they provide APIs to their binary blobs that only permit bus/slot/function addressing. The x86 non-ACPI PCI bus drivers all hardcode a domain of 0 as they do not support multiple domains. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D42827 (cherry picked from commit 1587a9db92c03c738bb3f0fc5874b43c961e7c99) 
This commit changes the API of pci_cfgreg(read|write) to add a domain
argument (referred to as a segment in ACPI parlance) (note that this
is not the same as a NUMA domain, but something PCI-specific).  This
does not yet enable access to domains other than 0, but updates the
API to support domains.

Places that use hard-coded bus/slot/function addresses have been
updated to hardcode a domain of 0.  A few places that have the PCI
domain (segment) available such as the acpi_pcib_acpi.c Host-PCI
bridge driver pass the PCI domain.

The hpt27xx(4) and hptnr(4) drivers fail to attach to a device not on
domain 0 since they provide APIs to their binary blobs that only
permit bus/slot/function addressing.

The x86 non-ACPI PCI bus drivers all hardcode a domain of 0 as they do
not support multiple domains.

Reviewed by:	imp
Differential Revision:	https://reviews.freebsd.org/D42827

(cherry picked from commit 1587a9db92c03c738bb3f0fc5874b43c961e7c99)
sys: Remove $FreeBSD$: one-line .c pattern 2023-08-23T17:43:25+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:27+00:00 3bc80996974a61a4223eae4c1ccd47b6ee32a48a Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ Similar commit in current: (cherry picked from commit 685dc743dc3b) 
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/

Similar commit in current:
(cherry picked from commit 685dc743dc3b)
sys: Remove $FreeBSD$: two-line .h pattern 2023-08-23T17:43:20+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:02+00:00 f8167e0404dab9ffeaca95853dd237ab7c587f82 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ Similar commit in current: (cherry picked from commit 95ee2897e98f) 
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/

Similar commit in current:
(cherry picked from commit 95ee2897e98f)
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD 2023-07-25T15:13:49+00:00 Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58+00:00 caa41f641755c935b036e17440a3b49329c904ed The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix (cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b) 
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with:		pfg
MFC After:		3 days
Sponsored by:		Netflix

(cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b)
ipmi: add Block Transfer interface support 2023-06-25T18:34:28+00:00 Andrey V. Elsukov ae@FreeBSD.org 2023-06-07T09:30:47+00:00 53380074a162833e2fdca11908e702ea7b7541f2 Reviewed by: ambrisko Obtained from: Yandex LLC Sponsored by: Yandex LLC Differential Revision: https://reviews.freebsd.org/D40421 (cherry picked from commit 1f166509895dd90fcaaa08b557f9bc106e3f7e71) 
Reviewed by:	ambrisko
Obtained from:	Yandex LLC
Sponsored by:	Yandex LLC
Differential Revision:	https://reviews.freebsd.org/D40421

(cherry picked from commit 1f166509895dd90fcaaa08b557f9bc106e3f7e71)
impi(4): Fix two typos in source code comments 2022-09-06T05:39:13+00:00 Gordon Bergling gbe@FreeBSD.org 2022-09-03T12:52:44+00:00 aceb5fff0adb3e0620b2cd7a248305f015f112f1 - s/overriden/overridden/ (cherry picked from commit 05e1ac3cbfedf12e4b7a41729ad2ff6e748983a1) 
- s/overriden/overridden/

(cherry picked from commit 05e1ac3cbfedf12e4b7a41729ad2ff6e748983a1)
ipmi: do not omit lun in BMC addresses 2022-07-11T03:10:23+00:00 Yuri yuri@aetern.org 2022-07-04T06:29:52+00:00 81fe400fb1e2d4df46bfb2240711fee56789d3ea Some systems put sensors on non-0 lun, so we should not omit it. This was the only difference with the Linux driver, where DIMM sensors could be queried, but not on FreeBSD. See this report[1] on the FreeBSD forums: https://forums.freebsd.org/threads/freebsd-cannot-get-dimm-temperature-sensor-value.85166/ Reviewed by: philip Tested by: Andrey Lanin[1] Differential Revision: https://reviews.freebsd.org/D35612 (cherry picked from commit 177f8b3294ef5717060c287fe1206c52ba3ecc53) 
Some systems put sensors on non-0 lun, so we should not omit it.  This
was the only difference with the Linux driver, where DIMM sensors could
be queried, but not on FreeBSD.

See this report[1] on the FreeBSD forums:
https://forums.freebsd.org/threads/freebsd-cannot-get-dimm-temperature-sensor-value.85166/

Reviewed by:	philip
Tested by:	Andrey Lanin[1]
Differential Revision: https://reviews.freebsd.org/D35612

(cherry picked from commit 177f8b3294ef5717060c287fe1206c52ba3ecc53)
ipmi: correctly handle ipmb requests 2022-07-11T03:10:05+00:00 Yuri yuri@aetern.org 2022-07-04T04:55:18+00:00 1549a6172f9d2957e023398d01a675912683afb9 Handle IPMB requests using SEND_MSG (sent as driver request as we do not need to return anything back to userland for this) and GET_MSG (sent as usual request so we can return the data for RECEIVE_MSG ioctl) pair. This fixes fetching complete sensor data from boards (e.g. HP ProLiant DL380 Gen10). Reviewed by: philip Differential Revision: https://reviews.freebsd.org/D35605 (cherry picked from commit 18db96dbfd4a09063a0abcefd51fa8d2aeb115d6) (cherry picked from commit c4995b69db93fdab5fe375eae129aeff1cbca1bb) 
Handle IPMB requests using SEND_MSG (sent as driver request as we do not
need to return anything back to userland for this) and GET_MSG (sent as
usual request so we can return the data for RECEIVE_MSG ioctl) pair.

This fixes fetching complete sensor data from boards (e.g. HP ProLiant
DL380 Gen10).

Reviewed by:	philip
Differential Revision: https://reviews.freebsd.org/D35605

(cherry picked from commit 18db96dbfd4a09063a0abcefd51fa8d2aeb115d6)
(cherry picked from commit c4995b69db93fdab5fe375eae129aeff1cbca1bb)