qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip


From: Michael Tokarev
Subject: Re: [Qemu-devel] TSC in qem[-kvm] 1.1+ and in-kernel irqchip
Date: Mon, 13 Aug 2012 17:16:22 +0400
User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.5) Gecko/20120624 Icedove/10.0.5

On 13.08.2012 17:07, Jan Kiszka wrote:
[]
>> The bisecion leads to this commit:
>>
>> commit 17ee47418e65b1593defb30edbab33ccd47fc1f8
>> Merge: 13b0496 5d17c0d
>> Author: Jan Kiszka <address@hidden>
>> Date:   Tue Apr 10 16:26:23 2012 +0200
>>
>>     Merge commit '5d17c0d2df4998598e6002b27b8e47e792899a0f' into 
>> queues/qemu-merge
[]
>> Cc'ing Jan for help.  The short story: tsc timer calibration
>> broke in 1.1+ with in-kernel irqchip (only) for several
>> apps (seabios and grub are two examples), the time is ticking
>> about 100 times faster.  In grub the timer is calibrated
>> using pit.  The above commit is the result of bisection.
> 
> Did the versions you tested include the commit 0cdd3d1444 (kvm: i8254:
> Fix conversion of in-kernel to userspace state)?

While bisecting I didn't have this commit applied, since it were
applied past (qemu)-1.1.  It is included into qemu-kvm 1.1.0
(as 960d355dc60d9), and that version behaves _exactly_ the same -
the time in grub is ticking 100 times faster.  I mentioned in this
thread that the problem persists in current qemu (and qemu-kvm)
git too.

I can repeat the bisection with this commit applied after the
above "bad" commit.  Should I?

Thanks,

/mjt



reply via email to

[Prev in Thread] Current Thread [Next in Thread]