aboutsummaryrefslogtreecommitdiff
path: root/share/man/man9/vcount.9
diff options
context:
space:
mode:
authorMitchell Horne <mhorne@FreeBSD.org>2023-03-15 15:26:57 +0000
committerMitchell Horne <mhorne@FreeBSD.org>2023-03-24 13:12:40 +0000
commit865b5640f8ef3c3a369f13b2c531737b7fb8fec4 (patch)
treecab9cfde02100d4cd17277859c32eb5ccc40ff26 /share/man/man9/vcount.9
parent9521266b82dfaa82ca4ac56276a049aee5f01ad9 (diff)
arm64: limit EFI excluded regions to physical memory types
Consolidate add_efi_map_entry() and exclude_efi_map_entry() into a single function, handle_efi_map_entry(), so that the exact set of entry types handled is the same in the addition or exclusion cases. Before, exclude_efi_map_entry() had a 'default' case that would exclude all entry types that were not listed explicitly in the switch statement. Logically, we do not need to exclude a range that could not possibly be added to physmem, and we do not need to exclude bus ranges that are not physical memory, for example EFI_MD_TYPE_IOMEM. Since physmem's ram0 device will reserve bus memory resources for its owned ranges, this was preventing attachment of the watchdog device on the RPI4B. For some reason its region of memory-mapped I/O appeared in the EFI memory map (with the aforementioned EFI_MD_TYPE_IOMEM type). This change fixes the attachment issue, as we prevent the physmem API from messing with this range of bus space. PR: 270044 Reported by: karels, Mark Millard Reviewed by: andrew, karels, imp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D39003 (cherry picked from commit 8937bd37d07c5c75995e01457aec00fb0a05c462)
Diffstat (limited to 'share/man/man9/vcount.9')
0 files changed, 0 insertions, 0 deletions