Hi Giacomo, Here is the ArmRelease:
[system.release] type=ArmRelease eventq_index=0 extensions=LPAE VIRTUALIZATION SECURITY FEAT_LSE FEAT_PAN FEAT_HPDS FEAT_VMID16 FEAT_RDM FEAT_UAO FEAT_LVA FEAT_LPA FEAT_SVE FEAT_FCMA FEAT_JSCVT FEAT_PAuth FEAT_SEL2 And yes, when running with the Faults debug flag enabled we see that there is a hypervisor trap thrown: ``` Global frequency set at 1000000000000 ticks per second gem5 Simulator System. https://www.gem5.org gem5 is copyrighted software; use the --copyright option for details. gem5 version 22.0.0.2 gem5 compiled Aug 2 2022 14:54:21 gem5 started Aug 3 2022 09:53:57 gem5 executing on <my machine>, pid <pid> command line: /path/to/gem5-workspace/gem5v22/gem5/build/ARM/gem5.opt --debug-flags=Faults -d /path/to/gem5-workspace/gem5v22/gem5/results/benchmark /path/to/gem5-workspace/gem5v22/gem5/configs/example/fs.py --disk-image /path/to/gem5-workspace/gem5v22/gem5/dist/disks/ubuntu.img --kernel /path/to/gem5-workspace/gem5v22/gem5/dist/binaries/vmlinux-4.14.arm64 --ruby --caches --l2cache --l1d_size=32kB --l2_size=256kB --cpu-type AtomicSimpleCPU --mem-size 8GB --script=/path/to/gem5-workspace/gem5v22/gem5/bootscripts/benchmark.rcS --checkpoint-at-end **** REAL SIMULATION **** 227203000: Hypervisor Trap: Invoking Fault (AArch64 target EL):Hypervisor Trap cpsr:0x3c9 PC:0xffffff80089a4cb4 elr:0xffffff80089a4cb4 newVec: 0x8008b400 inst: 0xd50320ff 227208000: Hypervisor Trap: Invoking Fault (AArch64 target EL):Hypervisor Trap cpsr:0x600003c9 PC:0xffffff80089a4cb4 elr:0xffffff80089a4cb4 newVec: 0x8008b400 inst: 0xd50320ff 227213000: Hypervisor Trap: Invoking Fault (AArch64 target EL):Hypervisor Trap cpsr:0x600003c9 PC:0xffffff80089a4cb4 elr:0xffffff80089a4cb4 newVec: 0x8008b400 inst: 0xd50320ff 227218000: Hypervisor Trap: Invoking Fault (AArch64 target EL):Hypervisor Trap cpsr:0x600003c9 PC:0xffffff80089a4cb4 elr:0xffffff80089a4cb4 newVec: 0x8008b400 inst: 0xd50320ff ... (repeats many thousands of times every 5000 ticks) ``` I can run with Exec as well if it is helpful, but there are hundreds of thousands of lines of output and I feel bad for whichever server out there that has to store that output. Again, thank you for your help! Best, Sam On Wed, Aug 3, 2022 at 8:00 AM Giacomo Travaglini <giacomo.travagl...@arm.com> wrote: > > > On 8/3/22 10:21, Giacomo Travaglini wrote: > > Hi Sam, > > > > If nothing gets printed, I am wondering whether you are encountering an > exception while booting. > > Would you mind running with –debug-flags=Exec,Faults and see what is going on? > > > > Exec = print the instruction trace > > Fault = print the exception trace > > > *Faults > > > > > (To check the ArmRelease you are using, have a look at system.release in > config.ini > > The entry will contain a list of architectural extensions) > > > > Giacomo > > > > From: Thomas, Samuel <samuel_tho...@brown.edu> > Date: Wednesday, 3 August 2022 at 00:17 > To: The gem5 Users mailing list <gem5-users@gem5.org> > Subject: [gem5-users] Re: gem5 Linux Version 4.18 > > Hi Giacomo, > > There is no output. We are also using a pristine v22.0.0.2 and let the > simulator run for ~1 day and there is no output. > > I'm not sure what you mean by which ArmRelease we are using -- > however, our run script is as follows: > > ``` > #!/bin/sh > > export CURR_DIR=$(pwd) > export M5_PATH=$CURR_DIR/dist > # export KERNEL_PATH=$M5_PATH/binaries/vmlinux.arm64 # out of box from > gem5 guest binaries -- boots and runs (~10 minutes) > export KERNEL_PATH=$M5_PATH/binaries/vmlinux-4.14.arm64 # compiled > locally -- (no output for ~1 day) > export DISK_PATH=$M5_PATH/disks/ubuntu.img > export SCRIPT_PATH=$CURR_DIR/bootscripts/$1.rcS > > rm -r $CURR_DIR/results/$1/ > > $CURR_DIR/build/ARM/gem5.opt -d $CURR_DIR/results/$1 > $CURR_DIR/configs/example/fs.py \ > --disk-image $DISK_PATH --kernel $KERNEL_PATH --ruby \ > --caches --l2cache --l1d_size=32kB --l2_size=256kB --cpu-type > AtomicSimpleCPU --mem-size 8GB \ > --script=$SCRIPT_PATH --checkpoint-at-end > > $CURR_DIR/build/ARM/gem5.opt -d $CURR_DIR/results/$1 > $CURR_DIR/configs/example/fs.py \ > --disk-image $DISK_PATH --kernel $KERNEL_PATH --ruby \ > --caches --l2cache --l1d_size=32kB --l2_size=256kB --cpu-type > DerivO3CPU --mem-size 8GB \ > --script=$SCRIPT_PATH --checkpoint-restore=1 --maxinsts 500000000 > ``` > > Should we be specifying the ARM specific CPU models as opposed to the > basic ones? > > Again, thank you for your help! > > Best, > Sam > > > On Tue, Aug 2, 2022 at 5:20 PM Giacomo Travaglini > <giacomo.travagl...@arm.com> wrote: > > > > Hi Sam, > > > > > > > > I have to say I successfully managed to boot Linux 4.14 with a pristine > > v22.0.0.2. > > > > What’s the content of m5out/system.terminal? Also, could you provide me the > > ArmRelease you are using? This should be a list of enabled Armv8.X > > extensions. > > > > > > > > Kind Regards > > > > > > > > Giacomo > > > > > > > > From: Thomas, Samuel <samuel_tho...@brown.edu> > > Date: Tuesday, 2 August 2022 at 14:57 > > To: The gem5 Users mailing list <gem5-users@gem5.org> > > Subject: [gem5-users] Re: gem5 Linux Version 4.18 > > > > Hi Giacomo, > > > > > > > > Thank you for your reply. Yes, I am using v22.0.0.2, and I have ensured > > that the recompiled bootloader binaries are in the M5_PATH. > > > > > > > > If that issue is resolved, then perhaps this shows that there is a similar > > issue that isn't necessarily a FEAT_PAuth problem, but has a similar > > output. What can I do to verify if FEAT_PAuth is enabled? If not, what else > > should I do to isolate the issue? > > > > > > > > Again, thank you for your help! > > > > > > > > Best, > > > > Sam > > > > > > > > On Tue, Aug 2, 2022 at 4:54 AM Giacomo Travaglini > > <giacomo.travagl...@arm.com> wrote: > > > > Hi Sam, > > > > > > > > 1. Are you using v22.0.0.2 or simply v22.0.0.0? (The FEAT_PAuth > > problem has been resolved in v22.0.0.2 so it is not really an open issue) > > > > 2. If using the v22.0.0.2, could you make sure you rebuild the > > bootloader and make M5_PATH point to it? > > > > Let me know if this works > > > > > > > > Kind Regards > > > > > > > > Giacomo > > > > > > > > From: Thomas, Samuel <samuel_tho...@brown.edu> > > Date: Monday, 1 August 2022 at 22:16 > > To: gem5 users mailing list <gem5-users@gem5.org> > > Subject: [gem5-users] gem5 Linux Version 4.18 > > > > Hi all, > > > > > > > > We recently upgraded our gem5 project to be compatible with gem5 version > > 22, and are working with a modified version of Linux. We had been working > > from kernel version 4.14 (following the instructions from > > https://www.gem5.org/documentation/general_docs/fullsystem/building_arm_kernel). > > > > > > > > When we use this kernel version with the most recent changes to gem5, the > > simulator cannot fully boot, and it seems as though this might be due to > > the "FEAT_PAuth" being utilized (cited as an open issue in the v22.0.0.2 > > release notes). When we use the out of the box Linux kernel binary that > > comes with the guest binaries (from > > https://www.gem5.org/documentation/general_docs/fullsystem/guest_binaries), > > the simulator works well and the system boots. > > > > > > > > Is the source for the Linux version 4.18 that comes with the guest binaries > > available? Are there any patches that we can apply to the Linux v4.18 > > commit? > > > > > > > > Thank you in advance for your help! > > > > > > > > Best, > > > > Sam > > > > IMPORTANT NOTICE: The contents of this email and any attachments are > > confidential and may also be privileged. If you are not the intended > > recipient, please notify the sender immediately and do not disclose the > > contents to any other person, use it for any purpose, or store or copy the > > information in any medium. Thank you. > > > > _______________________________________________ > > gem5-users mailing list -- gem5-users@gem5.org > > To unsubscribe send an email to gem5-users-le...@gem5.org > > > > IMPORTANT NOTICE: The contents of this email and any attachments are > > confidential and may also be privileged. If you are not the intended > > recipient, please notify the sender immediately and do not disclose the > > contents to any other person, use it for any purpose, or store or copy the > > information in any medium. Thank you. > > _______________________________________________ > > 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 > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ > 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
