n this issue with do_boot_cpu as well. The short story is I
> had to use multiple event queues and set the “sim_quantum” of the Root
> object to 1e8: https://gem5-review.googlesource.com/c/public/gem5/+/65131.
> Note that 1e8 is different from the 1e9 value used elsewhere in gem5.
> Based on a test of doi
>>
>>
>>
>>
>> -Matt
>>
>>
>>
>> From: Bobby Bruce via gem5-dev
>> Sent: Monday, November 14, 2022 10:37 AM
>> To: gem5-dev@gem5.org
>> Cc: Bobby Bruce
>> Subject: [gem5-dev] Re: Build failed in Jenkins: nightly
;
>
> -Matt
>
>
>
> *From:* Bobby Bruce via gem5-dev
> *Sent:* Monday, November 14, 2022 10:37 AM
> *To:* gem5-dev@gem5.org
> *Cc:* Bobby Bruce
> *Subject:* [gem5-dev] Re: Build failed in Jenkins: nightly #413
>
>
>
> *Caution:* This message originated from a
e
Subject: [gem5-dev] Re: Build failed in Jenkins: nightly #413
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
Hey all,
I've submitted the following patch to Gerrit which should fix the timeout
issues we
Hey all,
I've submitted the following patch to Gerrit which should fix the timeout
issues we're seeing with the Jenkin's nightly build:
https://gem5-review.googlesource.com/c/public/gem5/+/65492.
The high level summary of the problem is as follows:
- Up until recently we were using "m5
It turns out this patch:
https://gem5-review.googlesource.com/c/public/gem5/+/64831 is greatly
increasing the Linux boot times and therefore causing the timeouts to
occur. I'll try to find a solution for this. Unfortunately reverting the
patch isn't an option, changing the CPUID is necessary to
