On 10/11/2011 11:18 AM, Daniel P. Berrange wrote:
>
> The rep/ins implementation is still slow, optimizing it can help.
>
> What does 'perf top' say when running this workload?
To ensure it only recorded the LinuxBoot code, I created a 100 MB
kernel image which takes approx 30 seconds to copy.
On Tue, Oct 11, 2011 at 11:08:33AM +0200, Avi Kivity wrote:
> On 10/10/2011 09:01 PM, Alexander Graf wrote:
> >>> For example, one execution of QEMU produced the following log:
> >>>
> >>>$ stap qemu-timing.stp
> >>>0.000 Start
> >>>0.036 Run
> >>>0.038 BIOS post
> >>>0.180 BIO
On 10/10/2011 09:01 PM, Alexander Graf wrote:
>> For example, one execution of QEMU produced the following log:
>>
>>$ stap qemu-timing.stp
>>0.000 Start
>>0.036 Run
>>0.038 BIOS post
>>0.180 BIOS int 19
>>0.181 BIOS boot OS
>>0.181 LinuxBoot copy kernel
>>1.371 L
On Mon, Oct 10, 2011 at 06:08:03PM +0100, Daniel P. Berrange wrote:
> I've been investigating where time disappears to when booting Linux guests.
>
> Initially I enabled DEBUG_BIOS in QEMU's hw/pc.c, and then hacked it so
> that it could print a timestamp before each new line of debug output. The
On 10.10.2011, at 20:53, Anthony Liguori wrote:
> On 10/10/2011 12:08 PM, Daniel P. Berrange wrote:
>> I've been investigating where time disappears to when booting Linux guests.
>>
>> Initially I enabled DEBUG_BIOS in QEMU's hw/pc.c, and then hacked it so
>> that it could print a timestamp befo
On 10/10/2011 12:08 PM, Daniel P. Berrange wrote:
I've been investigating where time disappears to when booting Linux guests.
Initially I enabled DEBUG_BIOS in QEMU's hw/pc.c, and then hacked it so
that it could print a timestamp before each new line of debug output. The
problem with that is tha
I've been investigating where time disappears to when booting Linux guests.
Initially I enabled DEBUG_BIOS in QEMU's hw/pc.c, and then hacked it so
that it could print a timestamp before each new line of debug output. The
problem with that is that it slowed down startup, so the timings I was
exami
