Hi Youngin, In older kernels (4.x), pointer authentication instructions were incorrectly trapped for EL2. That is why there are `xpaclri` instructions. I assume that you are using a linux kernel version 4.14.0 from https://www.gem5.org/documentation/general_docs/fullsystem/building_arm_kernel. The kernel was patched in version 4.14.95, which can correctly trap those aforementioned instructions. Either you can use an updated kernel or disable SECURITY and FEAT_PAuth extensions to solve this problem. You may find this gerrit change helpful for building/reading about other arm64 kernels: https://gem5-review.googlesource.com/c/public/gem5-resources/+/59293
Thanks, Kaustav Goswami. On Thu, Aug 11, 2022 at 12:05 AM Youngin Kim <yiw...@yonsei.ac.kr> wrote: > Hi all, > > Linux kernel (build as described in > https://www.gem5.org/documentation/general_docs/fullsystem/building_arm_kernel) > cannot be booted on gem5 v22.0.0.2. > > I've read the question about the same issue here > https://www.mail-archive.com/gem5-users@gem5.org/msg20813.html. > > As Giacomo Travaglini > <https://www.mail-archive.com/search?l=gem5-users@gem5.org&q=from:%22Giacomo+Travaglini%22> > suggested, > I used gdb to find the cause, and it was XPACLRI instruction. > Linux kernel 4.18 provided as guest binaries is not calling this function > and booted well on gem5 v22.0.0.2. > XPACLRI instruction calls stripPAC function in > src/arch/arm/pauth_helpers.cc:863, and hypervisor trap is caused there. > > Can you give me some advice to solve this issue? > > Best > Youngin Kim > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
