TS
Thomas, Samuel
Mon, Aug 1, 2022 9:13 PM
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
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
GT
Giacomo Travaglini
Tue, Aug 2, 2022 8:52 AM
Hi Sam,
- 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)
- 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_thomas@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.
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_thomas@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.
TS
Thomas, Samuel
Tue, Aug 2, 2022 1:54 PM
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.Travaglini@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_thomas@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-leave@gem5.org
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.Travaglini@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_thomas@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-leave@gem5.org
>
GT
Giacomo Travaglini
Tue, Aug 2, 2022 9:19 PM
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_thomas@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.Travaglini@arm.commailto:Giacomo.Travaglini@arm.com> wrote:
Hi Sam,
-
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)
-
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_thomas@brown.edumailto:samuel_thomas@brown.edu>
Date: Monday, 1 August 2022 at 22:16
To: gem5 users mailing list <gem5-users@gem5.orgmailto: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.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@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.
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_thomas@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.Travaglini@arm.com<mailto:Giacomo.Travaglini@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_thomas@brown.edu<mailto:samuel_thomas@brown.edu>>
Date: Monday, 1 August 2022 at 22:16
To: gem5 users mailing list <gem5-users@gem5.org<mailto: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<mailto:gem5-users@gem5.org>
To unsubscribe send an email to gem5-users-leave@gem5.org<mailto:gem5-users-leave@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.
TS
Thomas, Samuel
Tue, Aug 2, 2022 11:14 PM
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.Travaglini@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_thomas@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.Travaglini@arm.com wrote:
Hi Sam,
-
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)
-
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_thomas@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-leave@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-leave@gem5.org
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.Travaglini@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_thomas@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.Travaglini@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_thomas@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-leave@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-leave@gem5.org
GT
Giacomo Travaglini
Wed, Aug 3, 2022 9:21 AM
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
(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_thomas@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.Travaglini@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_thomas@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.Travaglini@arm.com wrote:
Hi Sam,
-
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)
-
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_thomas@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-leave@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-leave@gem5.org
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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.
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
(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_thomas@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.Travaglini@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_thomas@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.Travaglini@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_thomas@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-leave@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-leave@gem5.org
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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.
GT
Giacomo Travaglini
Wed, Aug 3, 2022 11:59 AM
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_thomas@brown.edumailto:samuel_thomas@brown.edu
Date: Wednesday, 3 August 2022 at 00:17
To: The gem5 Users mailing list gem5-users@gem5.orgmailto: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.Travaglini@arm.commailto:Giacomo.Travaglini@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_thomas@brown.edumailto:samuel_thomas@brown.edu
Date: Tuesday, 2 August 2022 at 14:57
To: The gem5 Users mailing list gem5-users@gem5.orgmailto: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.Travaglini@arm.commailto:Giacomo.Travaglini@arm.com wrote:
Hi Sam,
-
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)
-
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_thomas@brown.edumailto:samuel_thomas@brown.edu
Date: Monday, 1 August 2022 at 22:16
To: gem5 users mailing list gem5-users@gem5.orgmailto: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.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@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.orgmailto:gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.orgmailto:gem5-users-leave@gem5.org
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_thomas@brown.edu><mailto:samuel_thomas@brown.edu>
Date: Wednesday, 3 August 2022 at 00:17
To: The gem5 Users mailing list <gem5-users@gem5.org><mailto: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.Travaglini@arm.com><mailto:Giacomo.Travaglini@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_thomas@brown.edu><mailto:samuel_thomas@brown.edu>
> Date: Tuesday, 2 August 2022 at 14:57
> To: The gem5 Users mailing list <gem5-users@gem5.org><mailto: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.Travaglini@arm.com><mailto:Giacomo.Travaglini@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_thomas@brown.edu><mailto:samuel_thomas@brown.edu>
> Date: Monday, 1 August 2022 at 22:16
> To: gem5 users mailing list <gem5-users@gem5.org><mailto: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<mailto:gem5-users@gem5.org>
> To unsubscribe send an email to gem5-users-leave@gem5.org<mailto:gem5-users-leave@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<mailto:gem5-users@gem5.org>
> To unsubscribe send an email to gem5-users-leave@gem5.org<mailto:gem5-users-leave@gem5.org>
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org<mailto:gem5-users@gem5.org>
To unsubscribe send an email to gem5-users-leave@gem5.org<mailto:gem5-users-leave@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<mailto:gem5-users@gem5.org>
To unsubscribe send an email to gem5-users-leave@gem5.org<mailto:gem5-users-leave@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.
TS
Thomas, Samuel
Wed, Aug 3, 2022 2:04 PM
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.travaglini@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_thomas@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.Travaglini@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_thomas@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.Travaglini@arm.com wrote:
Hi Sam,
-
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)
-
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_thomas@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-leave@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-leave@gem5.org
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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-leave@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-leave@gem5.org
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.travaglini@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_thomas@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.Travaglini@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_thomas@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.Travaglini@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_thomas@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-leave@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-leave@gem5.org
> _______________________________________________
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-leave@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-leave@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-leave@gem5.org
GT
Giacomo Travaglini
Wed, Aug 3, 2022 2:22 PM
I see.
I suggest you to run gem5.debug with gdb and set up a breakpoint in the Hypervisor Trap constructor.
This will tell you what is triggering the fault.
Should be relatively easy to fix
Kind Regards
Giacomo
From: Thomas, Samuel samuel_thomas@brown.edu
Date: Wednesday, 3 August 2022 at 15:07
To: The gem5 Users mailing list gem5-users@gem5.org
Subject: [gem5-users] Re: gem5 Linux Version 4.18
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.travaglini@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_thomas@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.Travaglini@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_thomas@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.Travaglini@arm.com wrote:
Hi Sam,
-
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)
-
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_thomas@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-leave@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-leave@gem5.org
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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-leave@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-leave@gem5.org
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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.
I see.
I suggest you to run gem5.debug with gdb and set up a breakpoint in the Hypervisor Trap constructor.
This will tell you what is triggering the fault.
Should be relatively easy to fix
Kind Regards
Giacomo
From: Thomas, Samuel <samuel_thomas@brown.edu>
Date: Wednesday, 3 August 2022 at 15:07
To: The gem5 Users mailing list <gem5-users@gem5.org>
Subject: [gem5-users] Re: gem5 Linux Version 4.18
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.travaglini@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_thomas@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.Travaglini@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_thomas@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.Travaglini@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_thomas@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-leave@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-leave@gem5.org
> _______________________________________________
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-leave@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-leave@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-leave@gem5.org
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@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.
KG
Kaustav Goswami
Wed, Aug 3, 2022 6:48 PM
Hi Samuel,
It looks like there are FEAT_PAuth instructions, which is preventing Linux
from booting up. I am using 22.0.0.2 (stable). I freshly compiled Linux
4.14 using the gem5_defconfig
from https://gem5.googlesource.com/arm/linux/
and tried to boot the Ubuntu
18.04 disk image from guest binaries. There is no output. When I debugged
it, it seems like it is caught in this loop:
17010010000: board.processor.cores0.core: A0 T0 : 0xffffff80089a4b8c
@map_kernel_segment+128 : xpaclri x30 : IntAlu :
flags=(IsInteger)
17010011000: board.processor.cores0.core: A0 T0 : 0x80089c00
@kernel_init.__hyp_stub_vectors+1024 : b
<kernel_init.__hyp_stub_vectors+2048> : IntAlu :
flags=(IsControl|IsDirectControl|IsUncondControl)
17010012000: board.processor.cores0.core: A0 T0 : 0x8008a000
@kernel_init.__hyp_stub_vectors+2048 : subs x0, #0 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010013000: board.processor.cores0.core: A0 T0 : 0x8008a004
@kernel_init.__hyp_stub_vectors+2052 : b.ne <vprintk_emit+224> :
IntAlu : flags=(IsControl|IsDirectControl|IsCondControl)
17010014000: board.processor.cores0.core: A0 T0 : 0x8008a010
@kernel_init.__hyp_stub_vectors+2064 : subs x0, #1 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010015000: board.processor.cores0.core: A0 T0 : 0x8008a014
@kernel_init.__hyp_stub_vectors+2068 : b.ne
<log_make_free_space+180> : IntAlu :
flags=(IsControl|IsDirectControl|IsCondControl)
17010016000: board.processor.cores0.core: A0 T0 : 0x8008a02c
@kernel_init.__hyp_stub_vectors+2092 : subs x0, #2 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010017000: board.processor.cores0.core: A0 T0 : 0x8008a030
@kernel_init.__hyp_stub_vectors+2096 : b.eq
<kernel_init.__inval_dcache_area+64> : IntAlu :
flags=(IsControl|IsDirectControl|IsCondControl)
17010018000: board.processor.cores0.core: A0 T0 : 0x8008a034
@kernel_init.__hyp_stub_vectors+2100 : ldr w0, #2148049024 :
MemRead : D=0x000000000badca11 A=0x8008a080 flags=(IsInteger|IsLoad)
17010019000: board.processor.cores0.core: A0 T0 : 0x8008a038
@kernel_init.__hyp_stub_vectors+2104 : eret :
IntAlu : D=0x0000000000000001
flags=(IsControl|IsSerializeAfter|IsNonSpeculative|IsSquashAfter)
A quick fix would be to drop the FEAT_PAuth
extension from your
ArmSystem. You may find either configs/example/arm/fs.py
or
configs/example/gem5_library/arm-ubuntu-boot-exit.py
instead of
configs/example/fs.py
easier for configuring your ArmSystem. Another
solution would be to use a different kernel version with all the default
EXTENSIONs enabled. I have tested with the following kernel version:
4.14.134
4.19.83
4.4.186
4.9.186
5.4.49
You can find the Kconfig for each of these aforementioned kernels here:
https://gem5-review.googlesource.com/c/public/gem5-resources/+/59293
If you are looking specifically for kernel 4.18.0 config, then you can get
from the same Ubuntu disk image that you're using. Once you drop into the
shell, just execute zcat /proc/config.gz
to look into the source.
Thanks,
Kasutav Goswami.
On Wed, Aug 3, 2022 at 7:24 AM Giacomo Travaglini <
Giacomo.Travaglini@arm.com> wrote:
I see.
I suggest you to run gem5.debug with gdb and set up a breakpoint in the Hypervisor
Trap constructor.
This will tell you what is triggering the fault.
Should be relatively easy to fix
Kind Regards
Giacomo
*From: *Thomas, Samuel samuel_thomas@brown.edu
*Date: *Wednesday, 3 August 2022 at 15:07
*To: *The gem5 Users mailing list gem5-users@gem5.org
*Subject: *[gem5-users] Re: gem5 Linux Version 4.18
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.travaglini@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
Would you mind running with –debug-flags=Exec,Faults and see what is
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
The entry will contain a list of architectural extensions)
Giacomo
From: Thomas, Samuel samuel_thomas@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.Travaglini@arm.com wrote:
Hi Sam,
I have to say I successfully managed to boot Linux 4.14 with a
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_thomas@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 <
Hi Sam,
-
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)
-
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_thomas@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
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.
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.
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.
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-leave@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-leave@gem5.org
Hi Samuel,
It looks like there are FEAT_PAuth instructions, which is preventing Linux
from booting up. I am using 22.0.0.2 (stable). I freshly compiled Linux
4.14 using the `gem5_defconfig` from `
https://gem5.googlesource.com/arm/linux/` and tried to boot the Ubuntu
18.04 disk image from guest binaries. There is no output. When I debugged
it, it seems like it is caught in this loop:
17010010000: board.processor.cores0.core: A0 T0 : 0xffffff80089a4b8c
@map_kernel_segment+128 : xpaclri x30 : IntAlu :
flags=(IsInteger)
17010011000: board.processor.cores0.core: A0 T0 : 0x80089c00
@kernel_init.__hyp_stub_vectors+1024 : b
<kernel_init.__hyp_stub_vectors+2048> : IntAlu :
flags=(IsControl|IsDirectControl|IsUncondControl)
17010012000: board.processor.cores0.core: A0 T0 : 0x8008a000
@kernel_init.__hyp_stub_vectors+2048 : subs x0, #0 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010013000: board.processor.cores0.core: A0 T0 : 0x8008a004
@kernel_init.__hyp_stub_vectors+2052 : b.ne <vprintk_emit+224> :
IntAlu : flags=(IsControl|IsDirectControl|IsCondControl)
17010014000: board.processor.cores0.core: A0 T0 : 0x8008a010
@kernel_init.__hyp_stub_vectors+2064 : subs x0, #1 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010015000: board.processor.cores0.core: A0 T0 : 0x8008a014
@kernel_init.__hyp_stub_vectors+2068 : b.ne
<log_make_free_space+180> : IntAlu :
flags=(IsControl|IsDirectControl|IsCondControl)
17010016000: board.processor.cores0.core: A0 T0 : 0x8008a02c
@kernel_init.__hyp_stub_vectors+2092 : subs x0, #2 :
IntAlu : D=0x0000000000000001 flags=(IsInteger)
17010017000: board.processor.cores0.core: A0 T0 : 0x8008a030
@kernel_init.__hyp_stub_vectors+2096 : b.eq
<kernel_init.__inval_dcache_area+64> : IntAlu :
flags=(IsControl|IsDirectControl|IsCondControl)
17010018000: board.processor.cores0.core: A0 T0 : 0x8008a034
@kernel_init.__hyp_stub_vectors+2100 : ldr w0, #2148049024 :
MemRead : D=0x000000000badca11 A=0x8008a080 flags=(IsInteger|IsLoad)
17010019000: board.processor.cores0.core: A0 T0 : 0x8008a038
@kernel_init.__hyp_stub_vectors+2104 : eret :
IntAlu : D=0x0000000000000001
flags=(IsControl|IsSerializeAfter|IsNonSpeculative|IsSquashAfter)
A quick fix would be to drop the `FEAT_PAuth` extension from your
ArmSystem. You may find either `configs/example/arm/fs.py` or
`configs/example/gem5_library/arm-ubuntu-boot-exit.py` instead of
`configs/example/fs.py` easier for configuring your ArmSystem. Another
solution would be to use a different kernel version with all the default
EXTENSIONs enabled. I have tested with the following kernel version:
4.14.134
4.19.83
4.4.186
4.9.186
5.4.49
You can find the Kconfig for each of these aforementioned kernels here:
https://gem5-review.googlesource.com/c/public/gem5-resources/+/59293
If you are looking specifically for kernel 4.18.0 config, then you can get
from the same Ubuntu disk image that you're using. Once you drop into the
shell, just execute `zcat /proc/config.gz` to look into the source.
Thanks,
Kasutav Goswami.
On Wed, Aug 3, 2022 at 7:24 AM Giacomo Travaglini <
Giacomo.Travaglini@arm.com> wrote:
> I see.
>
>
>
> I suggest you to run gem5.debug with gdb and set up a breakpoint in the Hypervisor
> Trap constructor.
>
> This will tell you what is triggering the fault.
>
>
>
> Should be relatively easy to fix
>
>
>
> Kind Regards
>
>
>
> Giacomo
>
>
>
> *From: *Thomas, Samuel <samuel_thomas@brown.edu>
> *Date: *Wednesday, 3 August 2022 at 15:07
> *To: *The gem5 Users mailing list <gem5-users@gem5.org>
> *Subject: *[gem5-users] Re: gem5 Linux Version 4.18
>
> 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.travaglini@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_thomas@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.Travaglini@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_thomas@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.Travaglini@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_thomas@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-leave@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-leave@gem5.org
> > _______________________________________________
> > gem5-users mailing list -- gem5-users@gem5.org
> > To unsubscribe send an email to gem5-users-leave@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-leave@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-leave@gem5.org
> _______________________________________________
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-leave@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-leave@gem5.org
>