| History log of /src/sys/arch/aarch64/include/vmparam.h |
| Revision | | Date | Author | Comments |
| 1.21 |
| 30-Jun-2024 |
jmcneill | aarch64: Bump VM_PHYSSEG_MAX to match DRAM_BANKS / FDT_MEMORY_RANGES.
On aarch64 there is a single free list, so VM_PHYSSEG_MAX needs to be
the same as FDT_MEMORY_RANGES (which needs to be the same as DRAM_BANKS).
Future cleanup should be done to fold these into a single define.
|
| 1.20 |
| 16-Apr-2023 |
skrll | branches: 1.20.6;
Rename VM_KERNEL_IO_ADDRESS to VM_KERNEL_IO_BASE to match RISC-V
It's less letters, matches other similar variables and will help with
sharing code between the two architectures.
NFCI.
|
| 1.19 |
| 02-Apr-2022 |
skrll | branches: 1.19.4;
Update to support EFI runtime outside the kernel virtual address space
by creating an EFI RT pmap that can be activated / deactivated when
required.
Adds support for EFI RT to ARM_MMU_EXTENDED (ASID) 32-bit Arm machines.
On Arm64 the usage of pmapboot_enter is reduced and the mappings are
created much later in the boot process -- now in cpu_startup_hook.
Backward compatiblity for KVA mapped RT from old bootaa64.efi is
maintained.
Adding support to other platforms should be easier as a result.
|
| 1.18 |
| 21-Mar-2021 |
skrll | Adjust the kernel virtual address space so that KASAN will map the kernel
seperately from managed kernel virtual memory and not map the unused space
between the two.
|
| 1.17 |
| 10-Nov-2020 |
skrll | branches: 1.17.2;
AA64 is not MIPS.
Change all KSEG references to directmap
|
| 1.16 |
| 06-Oct-2020 |
christos | branches: 1.16.2;
GC unused MAXTSIZ32
|
| 1.15 |
| 23-Sep-2020 |
skrll | Readability of a comment
|
| 1.14 |
| 19-Sep-2020 |
skrll | Define VM_KERNEL_VM_{BASE,SIZE} for aarch64 and remove an #ifdef in
fdt/platform.h
NFCI
|
| 1.13 |
| 16-Sep-2020 |
skrll | G/C AARCH64_KMEMORY_BASE
|
| 1.12 |
| 08-Jul-2020 |
skrll | Fix a comment
|
| 1.11 |
| 04-Mar-2020 |
ryo | change kernel vm base address to use more than 256GB of memory. (up to 64TB)
also enlarge KSEG(direct map) region from 512GB to 64TB.
KASAN works ok.
Note: -fasan-shadow-offset=
KASAN_SHADOW_START - (CANONICAL_BASE >> 3) =
0xFFFF400000000000 - (0xFFFF000000000000 >> 3) =
0xDFFF600000000000
|
| 1.10 |
| 22-Jan-2020 |
ad | Bump UBC defaults on sparc64 & aarch64, which already have a large pager_map.
|
| 1.9 |
| 21-Jan-2020 |
jmcneill | Switch aarch64 to use a single freelist.
|
| 1.8 |
| 28-Oct-2018 |
jmcneill | branches: 1.8.6;
Document the VA range reserved for EFI runtime services.
|
| 1.7 |
| 12-Oct-2018 |
ryo | add initial support of COMPAT_NETBSD32 on AArch64.
arm ELF32 EABI binaries could be execute in AArch32 state on AArch64. A32 THUMB mode is not supported yet.
|
| 1.6 |
| 14-Sep-2018 |
ryo | define VM_KERNEL_IO_SIZE for clarity
|
| 1.5 |
| 07-Sep-2018 |
jmcneill | Increase VM_PHYSSEG_MAX to 64
|
| 1.4 |
| 12-May-2018 |
jmcneill | branches: 1.4.2;
Increase PAGER_MAP_DEFAULT_SIZE to 512MB (from 16MB)
|
| 1.3 |
| 01-Apr-2018 |
ryo | Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)
- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)
|
| 1.2 |
| 11-Aug-2014 |
matt | branches: 1.2.2; 1.2.20;
Add some definitions for building RUMP libraries with MKCOMPAT.
|
| 1.1 |
| 10-Aug-2014 |
matt | Preliminary files for AARCH64 (64-bit ARM) support.
Enough for a distribution build.
|
| 1.2.20.5 |
| 26-Nov-2018 |
pgoyette | Sync with HEAD, resolve a couple of conflicts
|
| 1.2.20.4 |
| 20-Oct-2018 |
pgoyette | Sync with head
|
| 1.2.20.3 |
| 30-Sep-2018 |
pgoyette | Ssync with HEAD
|
| 1.2.20.2 |
| 21-May-2018 |
pgoyette | Sync with HEAD
|
| 1.2.20.1 |
| 07-Apr-2018 |
pgoyette | Sync with HEAD. 77 conflicts resolved - all of them $NetBSD$
|
| 1.2.2.3 |
| 03-Dec-2017 |
jdolecek | update from HEAD
|
| 1.2.2.2 |
| 20-Aug-2014 |
tls | Rebase to HEAD as of a few days ago.
|
| 1.2.2.1 |
| 11-Aug-2014 |
tls | file vmparam.h was added on branch tls-maxphys on 2014-08-20 00:02:39 +0000
|
| 1.4.2.2 |
| 08-Apr-2020 |
martin | Merge changes from current as of 20200406
|
| 1.4.2.1 |
| 10-Jun-2019 |
christos | Sync with HEAD
|
| 1.8.6.1 |
| 25-Jan-2020 |
ad | Sync with head.
|
| 1.16.2.2 |
| 03-Apr-2021 |
thorpej | Sync with HEAD.
|
| 1.16.2.1 |
| 14-Dec-2020 |
thorpej | Sync w/ HEAD.
|
| 1.17.2.1 |
| 03-Apr-2021 |
thorpej | Sync with HEAD.
|
| 1.19.4.1 |
| 03-Jul-2024 |
martin | Pull up following revision(s) (requested by jmcneill in ticket #735):
sys/dev/pci/pci_resource.c: revision 1.5
sys/arch/arm/pci/pci_msi_machdep.c: revision 1.10
sys/arch/aarch64/include/vmparam.h: revision 1.21
sys/dev/acpi/acpi_resource.c: revision 1.43
pci_resource: Make unexpected bus numbers in bridges non-fatal.
Firmware bugs happen. Log a warning and continue instead of panicing.
acpi: Ignore producer/consumer bit for fixed memory resources.
The requirement to honour the producer/consumer bit in fixed memory
resource descriptors was dropped at some point in a revision to the ACPI
2.0 specification because too many firmware implementations got it wrong.
aarch64: Bump VM_PHYSSEG_MAX to match DRAM_BANKS / FDT_MEMORY_RANGES.
On aarch64 there is a single free list, so VM_PHYSSEG_MAX needs to be
the same as FDT_MEMORY_RANGES (which needs to be the same as DRAM_BANKS).
Future cleanup should be done to fold these into a single define.
arm: pci: Fix ITS ID lookup for MSIs.
pci_get_frameid expects a BDF requestor ID as input, not a Device ID.
Fixes MSI/MSI-X support on Ampere Altra systems.
|
| 1.20.6.1 |
| 01-Jul-2024 |
perseant | Sync with HEAD.
|
