在2024年6月5日六月 下午1:47，Jiaxun Yang写道：
[...]
> I'll try to upgrade kernel used in this test.
Unfortunately, we don't have kernel build from reliable source
for that test.
I requested Debian project to build kernel for us[1].
[1]: https://salsa.debian.org/kernel-team/linux/-/merge_requests/1074
在2024年6月4日六月 下午1:43，Alex Bennée写道：
[...]
>
> I'm a little uncomfortable about making the success of MTTCG depend on
> the user options passed to the kernel.
Yes, I agree, it sounds awkward.
>
> How come a non-icount run depends on how many instructions are being run
> on each core? Why is
Jiaxun Yang writes:
> MTTCG was disabled in a092a9554771 ("configure: disable MTTCG
> for MIPS guests") due to test case instability.
>
> I was able to reproduce this issue with in latest QEMU and look
> into reason behind that.
>
> What actually happend is kernel's CP0 timer synchronisation
>
在2024年6月3日六月 下午7:15，Pierrick Bouvier写道：
> On 5/11/24 13:26, Jiaxun Yang wrote:
>> MTTCG was disabled in a092a9554771 ("configure: disable MTTCG
>> for MIPS guests") due to test case instability.
>>
>> I was able to reproduce this issue with in latest QEMU and look
>> into reason behind that.
On 5/11/24 13:26, Jiaxun Yang wrote:
MTTCG was disabled in a092a9554771 ("configure: disable MTTCG
for MIPS guests") due to test case instability.
I was able to reproduce this issue with in latest QEMU and look
into reason behind that.
What actually happend is kernel's CP0 timer
+Alex, Pierrick & Anton
On 11/5/24 22:26, Jiaxun Yang wrote:
MTTCG was disabled in a092a9554771 ("configure: disable MTTCG
for MIPS guests") due to test case instability.
I was able to reproduce this issue with in latest QEMU and look
into reason behind that.
What actually happend is kernel's
MTTCG was disabled in a092a9554771 ("configure: disable MTTCG
for MIPS guests") due to test case instability.
I was able to reproduce this issue with in latest QEMU and look
into reason behind that.
What actually happend is kernel's CP0 timer synchronisation
mechanism assumed a consistent
