arm/arm64: Use 'max' cpu and gic types
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest0 of 2 patches 1 replyIn review
- v12 patches 0 repliesSuperseded
Changes in v2 from the cover letter
- Forgot to test with efi on v1 and testing now found an issue. Add a patch to allow '-cpu max', which has LPA2, to work with efi.
Patches in v2 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Nikos Nikoleris | Eric Auger |
|---|---|---|
| Series | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [kvm-unit-tests PATCH v2 0/2] arm/arm64: Use 'max' cpu and gic types
The arm64 'max' CPU type enables all features, so it makes sense to use it for testing to ensure we're testing the latest models. The 'max' GIC is used to pick the latest GIC model by default which is better than defaulting to gicv2 since it tests a later model and, when more than 8 CPUs are configured, it'll actually work. We don't need to convert 'max' to 'host' with KVM/HVF since 'max' is an alias for 'host' when those accelerators are enabled.
v2:
- Forgot to test with efi on v1 and testing now found an issue. Add a patch to allow '-cpu max', which has LPA2, to work with efi.
Andrew Jones (3):
arm64: Prepare for LPA2
arm/arm64: Use 'max' gic type
arm64: Use 'max' cpu type
arm/run | 8 +------ configure | 2 +- lib/arm64/asm/processor.h | 49 +++++++++++++++++++++------------------ 3 files changed, 29 insertions(+), 30 deletions(-)
Signature · 1 line
2.44.0