mailing list
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
> (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
> Date: Wednesday, 3 August 2022 at 00:17
> To: The gem5 U
g list
<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,
, have a look at system.release in
config.ini
The entry will contain a list of architectural extensions)
Giacomo
From: Thomas, Samuel
Date: Wednesday, 3 August 2022 at 00:17
To: The gem5 Users mailing list
Subject: [gem5-users] Re: gem5 Linux Version 4.18
Hi Giacomo,
There is no output. We are
> From: Thomas, Samuel
> Date: Tuesday, 2 August 2022 at 14:57
> To: The gem5 Users mailing list
> 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 recompil
Date: Tuesday, 2 August 2022 at 14:57
To: The gem5 Users mailing list
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
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. W
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 Regard
