On 16.09.21 17:55, Peter Maydell wrote: > On Thu, 16 Sept 2021 at 16:30, Alexander Graf <ag...@csgraf.de> wrote: >> >> On 16.09.21 14:24, Peter Maydell wrote: >>> On Wed, 15 Sept 2021 at 19:10, Alexander Graf <ag...@csgraf.de> wrote: >>>> Now that we have working system register sync, we push more target CPU >>>> properties into the virtual machine. That might be useful in some >>>> situations, but is not the typical case that users want. >>>> >>>> So let's add a -cpu host option that allows them to explicitly pass all >>>> CPU capabilities of their host CPU into the guest. >>>> >>>> Signed-off-by: Alexander Graf <ag...@csgraf.de> >>>> Acked-by: Roman Bolshakov <r.bolsha...@yadro.com> >>>> Reviewed-by: Sergio Lopez <s...@redhat.com> >>>> >>>> + /* >>>> + * A scratch vCPU returns SCTLR 0, so let's fill our default with the >>>> M1 >>>> + * boot SCTLR from https://github.com/AsahiLinux/m1n1/issues/97 > Side note: SCTLR_EL1 is a 64-bit register, do you have anything that > prints the full 64-bits to confirm that [63:32] are indeed all 0?
Yes, m1n1 prints the full 64bit value: https://github.com/AsahiLinux/m1n1/blob/main/src/memory.c#L459 That said, I'm not sure we really have to model the guest's reset SCTLR in EL1 to be identical to the host's reset SCTLR in EL2. I think it's a great start, but as long as there is no spec that indicates what SCTLR should be in EL1, we can make our own rules IMHO. Alex
