|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0 |
|
| #
031beb4e |
| 16-Aug-2023 |
Warner Losh <[email protected]> |
sys: Remove $FreeBSD$: one-line sh pattern
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0 |
|
| #
c76e96ed |
| 04-Oct-2019 |
Conrad Meyer <[email protected]> |
nvdimm(4): Fix Clang build after r353110
Clang spuriously warns about some well-defined C99 static initializers. Mute it.
X-MFC-With: r353110
|
| #
cbd974b4 |
| 04-Oct-2019 |
Conrad Meyer <[email protected]> |
nvdimm(4): Add nvdimm_e820 pseudo-bus
nvdimm_e820 is a newbus pseudo driver that looks for "legacy" e820 PRAM spans and creates ordinary-looking SPA devfs nodes for them (/dev/nvdimm_spaN).
As thes
nvdimm(4): Add nvdimm_e820 pseudo-bus
nvdimm_e820 is a newbus pseudo driver that looks for "legacy" e820 PRAM spans and creates ordinary-looking SPA devfs nodes for them (/dev/nvdimm_spaN).
As these legacy regions lack real NFIT SPA regions and namespace definitions, they must be administratively sliced up externally using device.hints. This is similar in purpose to the Linux memmap= mechanism.
It is assumed that systems with working NFIT tables will not have any use for this driver, and that that will be the prevailing style going forward, so if there are no explicit hints provided, this driver does not automatically create any devices.
Reviewed by: kib (previous version) Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D21885
show more ...
|
| #
963c89ff |
| 27-Sep-2019 |
Conrad Meyer <[email protected]> |
nvdimm(4): Extract ACPI root bus driver
No functional change intended.
The intent is to add a "legacy" e820 pmem newbus bus for nvdimm device in a subsequent revision, and it's a little more clear
nvdimm(4): Extract ACPI root bus driver
No functional change intended.
The intent is to add a "legacy" e820 pmem newbus bus for nvdimm device in a subsequent revision, and it's a little more clear if the parent buses get independent source files.
Quite a lot of ACPI-specific logic is left in nvdimm.c; disentangling that is a much larger change (and probably not especially useful).
Reviewed by: kib Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D21813
show more ...
|
|
Revision tags: release/11.3.0 |
|
| #
dac21b8d |
| 28-Mar-2019 |
Li-Wen Hsu <[email protected]> |
Fix `make` in sys/modules
Sponsored by: The FreeBSD Foundation
|
| #
8ebb6ddd |
| 22-Feb-2019 |
Ben Widawsky <[email protected]> |
nvdimm: Simple namespace support
Add support for simple NVDIMM v1.2 namespaces from the UEFI version 2.7 specification. The combination of NVDIMM regions and labels can lead to a wide variety of nam
nvdimm: Simple namespace support
Add support for simple NVDIMM v1.2 namespaces from the UEFI version 2.7 specification. The combination of NVDIMM regions and labels can lead to a wide variety of namespace layouts. Here we support a simple subset of namespaces where each NVDIMM SPA range is composed of a single region per member dimm.
Submitted by: D Scott Phillips <[email protected]> Discussed with: kib MFC after: 1 week Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D18736
show more ...
|
| #
7674dce0 |
| 31-Jan-2019 |
Konstantin Belousov <[email protected]> |
nvdimm: only enumerate present nvdimm devices
Not all child devices of the NVDIMM root device represent DIMM devices which are present in the system. The spec says (ACPI 6.2, sec 9.20.2):
For e
nvdimm: only enumerate present nvdimm devices
Not all child devices of the NVDIMM root device represent DIMM devices which are present in the system. The spec says (ACPI 6.2, sec 9.20.2):
For each NVDIMM present or intended to be supported by platform, platform firmware also exposes an NVDIMM device ... under the NVDIMM root device.
Present NVDIMM devices are found by walking all of the NFIT table's SPA ranges, then walking the NVDIMM regions mentioned by those SPA ranges.
A set of NFIT walking helper functions are introduced to avoid the need to splat the enumeration logic across several disparate callbacks.
Submitted by: D Scott Phillips <[email protected]> Sponsored by: Intel Corporation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D18439
show more ...
|
|
Revision tags: release/12.0.0 |
|
| #
ab00aff0 |
| 18-Oct-2018 |
Bjoern A. Zeeb <[email protected]> |
Fix modules/nvdimm build issues after r339391 by adding a dependency to the SRC list. Sort the list while changing the line.
Reported by: ci.f.o, make -j24 buildkernel Approved by: re (gjb)
|
| #
6db7f8e5 |
| 16-Oct-2018 |
Konstantin Belousov <[email protected]> |
Add initial driver for ACPI NFIT-enumerated NVDIMMs.
Driver enumerates NVDIMMs. Besides, for each found System Physical Address (SPA) range, spaN geom provider is created, which allows formatting a
Add initial driver for ACPI NFIT-enumerated NVDIMMs.
Driver enumerates NVDIMMs. Besides, for each found System Physical Address (SPA) range, spaN geom provider is created, which allows formatting and mounting the region as the normal volume. Also, /dev/nvdimm_spaN node is created, which can be read/written/mapped by userspace, the mapping is zero-copy.
No support for block access methods implemented, labels are not parsed. No management interfaces are provided.
Tested by: Intel, NetApp Sponsored by: The FreeBSD Foundation Approved by: re (gjb) MFC after: 2 weeks
show more ...
|