|
From: | Richard Henderson |
Subject: | Re: tb_flush() calls causing long Windows XP boot times |
Date: | Tue, 15 Jun 2021 18:58:04 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 |
On 6/15/21 6:58 AM, Programmingkid wrote:
Ahh I misread - so those are the addresses of the routines and not where it's sticking the breakpoint? I notice from a bit of googling that there is a boot debugger. I wonder if /nodebug in boot.ini stops this behaviour? https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/switch-options-for-boot-files -- Alex BennéeHi Alex, I tried your suggestion of using /nodebug. It did not stop the tb_flush() function from being called.
We are not expecting zero calls to tb_flush (it is used for other things, including buffer full), but we are hoping that it reduces the frequency of the calls.
I'm guessing you didn't immediately see the slowdown vanish, and so there was no change to the frequency of the calls.
FWIW, if you switch to the qemu console, you can see how many flushes have occurred with "info jit".
r~
[Prev in Thread] | Current Thread | [Next in Thread] |