Okay great!
Thanks,
Farbin.
On Thu, Apr 13, 2023 at 11:41 PM Ayaz Akram wrote:
> Hi Farbin,
>
> I think that change/fix is already merged.
>
> -Ayaz
>
> On Wed, Apr 12, 2023 at 1:47 PM Farbin Fayza wrote:
>
>> Hi everyone, thank you very much for co-operating. The stat file errors
>> were reso
Hi Farbin,
I think that change/fix is already merged.
-Ayaz
On Wed, Apr 12, 2023 at 1:47 PM Farbin Fayza wrote:
> Hi everyone, thank you very much for co-operating. The stat file errors
> were resolved by the change that Humza mentioned. The stat file now
> contains non-zero metrics. Should I
Hi everyone, thank you very much for co-operating. The stat file errors
were resolved by the change that Humza mentioned. The stat file now
contains non-zero metrics. Should I make changes and push them to the repo?
Should it be in the "develop" branch of
https://gem5.googlesource.com/public/gem5?
On 4/7/2023 10:05 PM, Farbin Fayza via gem5-users wrote:
Could you kindly tell me if there's any way to run the gem5 simulation faster using multiple cores?
Is it possible while we run SPEC?
The only way is to run multiple distinct simulations in parallel.
This can be done by directing their ou
Could you kindly tell me if there's any way to run the gem5 simulation
faster using multiple cores? Is it possible while we run SPEC?
Thanks,
Farbin.
On Fri, Apr 7, 2023 at 2:19 PM Farbin Fayza wrote:
> Hi Humza and Ayaz,
> Thank you so much for your help. My simulations are still running. I ca
Hi Humza and Ayaz,
Thank you so much for your help. My simulations are still running. I can
push the change when the simulations end. That way we can be confirmed that
the change worked out.
Thanks again,
Farbin.
On Fri, Apr 7, 2023 at 1:45 PM Ayaz Akram wrote:
> Hi,
>
> @Humza or @Farbin: Can
Hi,
@Humza or @Farbin: Can you please push the spec-2017 change that worked for
you to the mainline gem5 as well?
Thanks,
-Ayaz
On Thu, Apr 6, 2023 at 9:03 PM Ayaz Akram wrote:
> Hi Farbin,
>
> However, now they're taking so much time to run. I'm trying to run
>> perlbench, gcc, bwaves, and mc
Hi Farbin,
However, now they're taking so much time to run. I'm trying to run
> perlbench, gcc, bwaves, and mcf with the "test" size, and they're running
> for more than 10 hours and still, none of them aren't finished. Is this
> normal? Could you tell me how long they usually take?
I would expe
Hi Humza,
Thank you so much for your help. I added the processor.switch() command as
you said and now the simulations are running.
However, now they're taking so much time to run. I'm trying to run
perlbench, gcc, bwaves, and mcf with the "test" size, and they're running
for more than 10 hours and
Hi,
I believe the reason for this is that the "x86-spec-cpu2017-benchmarks.py" file
does not have a "process.switch()" statement and, as such, the processor
remains in "CPUTypes.KVM" mode.
If there is no other error when your script finishes, you could try adding
"processor.switch()" infront o
10 matches
Mail list logo
