Peter Maydell writes:
> On Wed, 16 Jun 2021 at 13:53, Alex Bennée wrote:
>>
>> Mark Cave-Ayland writes:
>> > diff --git a/exec.c b/exec.c
>> > index 67e520d18e..7f4074f95e 100644
>> > --- a/exec.c
>> > +++ b/exec.c
>> > @@ -1019,14 +1019,13 @@ void tb_invalidate_phys_addr(AddressSpace *as,
>> >
Mark Cave-Ayland writes:
> On 16/06/2021 02:58, Richard Henderson wrote:
>
>> 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 d
On Wed, 16 Jun 2021 at 13:53, Alex Bennée wrote:
>
> Mark Cave-Ayland writes:
> > diff --git a/exec.c b/exec.c
> > index 67e520d18e..7f4074f95e 100644
> > --- a/exec.c
> > +++ b/exec.c
> > @@ -1019,14 +1019,13 @@ void tb_invalidate_phys_addr(AddressSpace *as,
> > hwaddr addr, MemTxAttrs attrs)
>
Mark Cave-Ayland writes:
> On 16/06/2021 02:58, Richard Henderson wrote:
>
>> 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 d
> On Jun 15, 2021, at 9:58 PM, Richard Henderson
> wrote:
>
> 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 wond
On 16/06/2021 02:58, Richard Henderson wrote:
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 t
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
> On Jun 14, 2021, at 10:37 AM, Alex Bennée wrote:
>
> Mark Cave-Ayland writes:
>
>> On 11/06/2021 19:22, Alex Bennée wrote:
>>
>> (added Gitlab on CC)
>>
>>> Paolo Bonzini writes:
>>>
On 11/06/21 17:01, Programmingkid wrote:
> Hello Alex,
> The good news is the source code
ro.org ->
patchew/20210614083800.1166166-1-richard.hender...@linaro.org
Switched to a new branch 'test'
0c48784 tb_flush() calls causing long Windows XP boot times
=== OUTPUT BEGIN ===
ERROR: Missing Signed-off-by: line(s)
total: 1 errors, 0 warnings, 8 lines checked
Commit 0c48784df7c
Mark Cave-Ayland writes:
> On 11/06/2021 19:22, Alex Bennée wrote:
>
> (added Gitlab on CC)
>
>> Paolo Bonzini writes:
>>
>>> On 11/06/21 17:01, Programmingkid wrote:
Hello Alex,
The good news is the source code to Windows XP is available
online:https://github.com/cryptoAlgorithm
On 11/06/2021 19:22, Alex Bennée wrote:
(added Gitlab on CC)
Paolo Bonzini writes:
On 11/06/21 17:01, Programmingkid wrote:
Hello Alex,
The good news is the source code to Windows XP is available
online:https://github.com/cryptoAlgorithm/nt5src
It's leaked, so I doubt anybody who's paid t
Paolo Bonzini writes:
> On 11/06/21 17:01, Programmingkid wrote:
>> Hello Alex,
>> The good news is the source code to Windows XP is available
>> online:https://github.com/cryptoAlgorithm/nt5src
>
> It's leaked, so I doubt anybody who's paid to work on Linux or QEMU
> would touch that with a te
On 11/06/21 17:01, Programmingkid wrote:
Hello Alex,
The good news is the source code to Windows XP is available
online:https://github.com/cryptoAlgorithm/nt5src
It's leaked, so I doubt anybody who's paid to work on Linux or QEMU
would touch that with a ten-foot pole.
Paolo
> On Jun 11, 2021, at 7:24 AM, Alex Bennée wrote:
>
>
> Mark Cave-Ayland writes:
>
>> On 10/06/2021 14:14, Peter Maydell wrote:
>>
>>> On Thu, 10 Jun 2021 at 14:02, Programmingkid
>>> wrote:
Hi Richard,
There is a function called breakpoint_invalidate() in cpu.c tha
Mark Cave-Ayland writes:
> On 10/06/2021 14:14, Peter Maydell wrote:
>
>> On Thu, 10 Jun 2021 at 14:02, Programmingkid
>> wrote:
>>>
>>> Hi Richard,
>>>
>>> There is a function called breakpoint_invalidate() in cpu.c that
>>> calls a function called tb_flush(). I have determined that this
>>>
> On Jun 10, 2021, at 9:14 AM, Peter Maydell wrote:
>
> On Thu, 10 Jun 2021 at 14:02, Programmingkid
> wrote:
>>
>> Hi Richard,
>>
>> There is a function called breakpoint_invalidate() in cpu.c that calls a
>> function called tb_flush(). I have determined that this call is being made
>>
On 10/06/2021 14:14, Peter Maydell wrote:
On Thu, 10 Jun 2021 at 14:02, Programmingkid wrote:
Hi Richard,
There is a function called breakpoint_invalidate() in cpu.c that calls a
function called tb_flush(). I have determined that this call is being made over
200,000 times when Windows XP b
On Thu, 10 Jun 2021 at 14:02, Programmingkid wrote:
>
> Hi Richard,
>
> There is a function called breakpoint_invalidate() in cpu.c that calls a
> function called tb_flush(). I have determined that this call is being made
> over 200,000 times when Windows XP boots. Disabling this function makes
Hi Richard,
There is a function called breakpoint_invalidate() in cpu.c that calls a
function called tb_flush(). I have determined that this call is being made over
200,000 times when Windows XP boots. Disabling this function makes Windows XP
boot way faster than before. The time went down from
19 matches
Mail list logo
