For handy reference, here are the main EL2 system registers that pKVM refers to, in the Armv8-A docs: Liu Y (2009) Fast multipole boundary element method: theory and applications in engineering. Cambridge University Press, Cambridge We have a separate note, notes19-2020-06-26-pkvm-build, based on notes from Will and Andrew S., explaining how to get, build, and run the pKVM code. 1.1 Questions table at:0x00008000fe02f000 level:0x00000000 entry at:0x00008000fe02f000 raw:0x000000013e030003 EK_TABLE

Uplift loads have been increased for earthquake or wind loading with no further increase allowed. Reduce where other loads govern. MAIR_EL2 Memory Attribute Indirection Register (EL2). Provides the memory attribute encodings corresponding to the possible AttrIndx values in a Long-descriptor format translation table entry for stage 1 translations at EL2. https://developer.arm.com/docs/ddi0595/i/aarch64-system-registers/mair_el2 and the interface to this gets stored (by hyp_early_alloc_init) into struct kvm_pgtable_mm_ops hyp_early_alloc_mm_ops; 1.6.5 Buddy allocator Not sure I understand the question. S2 only applies to EL1/0, and is directly maintained by the hypervisor, so lives in a separate register.

Reduced installation time and consistent performance for valley truss assemblies.

Will: Arm added a new instruction, TTL hint - would love to know what happens if you get that wrong. Telling TLB invalidation what level you're operating at. 2.10 Section structure and linker script wrangling This is largely a rephrasing of the setup code in arm64/kvm/hyp/nvhe/setup.c. It takes memory from the early allocator pool, but we no longer care about the internal invariant of that after this point. At EL2 the __do_hyp_init (defined in hyp-init.S) vector entry we installed above does a comparison against KVM_HOST_SMCCC_FUNC(__kvm_hyp_init). As far as I can tell, this __kvm_hyp_init is therefore just a string, not to be confused with the confusingly identically named symbol for the vector table in arch/arm64/kvm/hyp/nvhe/hyp-init.S A. After that comparison (I think to pass through some stub calls), __do_hyp_init calls ____kvm_hyp_init (also in hyp-init.S). When attached directly to the supporting framing with either screws or nails, the allowable uplift for pitches less than 4/12 is 240 lb. (DF/SP) and 205 lb. (SPF/HF). For pitches 4/12 to 12/12, use the tabulated uplift loads. init_hyp_mode in arch/arm64/kvm/arm.c A"Inits Hyp-mode on all online CPU". It does a bunch of stuff which looks mostly common to vanilla and protected KVM:

FEAT_HAFDBS, Hardware management of the Access flag and dirty state (from v8.1, implementation-defined) - don't know? (guess likely used by guests if present; maybe pKVM doesn't have any use for it?) Quentin writes: David had a script for that. I haven't used it in a while, but it should still work fine: https://android-kvm.googlesource.com/build/+/refs/heads/master/aarch64/ git clone https://android-kvm.googlesource.com/build All drivers and teams competing in the TCR WORLD TOUR events are eligible to score points for the TCR WORLD TOUR and the TCR WORLD RANKING. Those structs are defined in arch/arm64/include/asm/kvm_host.h A 1.6.10 system register save and restoreThe following (long, sorry) list of questions come from reading the Arm Chapter D5 "The AArch64 Virtual Memory System Architecture". We don't necessarily have to nail them all down right now, but I guess many are clear?

VTCT accredits centres to offer our qualifications, but cannot advise which centres are running particular courses at any time.FEAT_PAN,Privileged access never (mandatory in 8.1) and PSTATE.PAN - don't know? How does that even work?