From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: [Qemu-devel] [PATCH] KVM: i8254: Clean up limit constant
Date: Mon, 11 Jun 2012 12:29:49 +0200 [thread overview]
Message-ID: <4FD5C89D.2010408@siemens.com> (raw)
In-Reply-To: <4FD5C352.4000004@redhat.com>
On 2012-06-11 12:07, Avi Kivity wrote:
> On 06/06/2012 05:28 PM, Jan Kiszka wrote:
>> Due to a offset between the clock used to generate the in-kernel
>> count_load_time (CLOCK_MONOTONIC) and the clock used for processing this
>> in userspace (vm_clock), reading back the output of PIT channel 2 via
>> port 0x61 was broken. One use cases that suffered from it was the CPU
>> frequency calibration of SeaBIOS, which also affected IDE/AHCI timeouts.
>>
>> This fixes it by calibrating the offset between both clocks on
>> kvm_pit_get and adjusting the kernel value before saving it in the
>> userspace state. As the calibration only works while the vm_clock is
>> running, we cache the in-kernel state across stopped phases.
>
> Applied, thanks.
>
>> + clock_offset = LLONG_MAX;
>
> INT64_MAX would me more strictly correct, but in practice it makes no
> difference.
Was looking for this, just not long enough. Need to print some cheat
sheet. However, let's clean this up immediately:
---8<---
clock_offset is int64_t.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
hw/kvm/i8254.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/kvm/i8254.c b/hw/kvm/i8254.c
index 04333d8..c5d3711 100644
--- a/hw/kvm/i8254.c
+++ b/hw/kvm/i8254.c
@@ -62,7 +62,7 @@ static void kvm_pit_get(PITCommonState *pit)
* kvm_pit_channel_state::count_load_time, and vm_clock. Take the
* minimum of several samples to filter out scheduling noise.
*/
- clock_offset = LLONG_MAX;
+ clock_offset = INT64_MAX;
for (i = 0; i < CALIBRATION_ROUNDS; i++) {
offset = qemu_get_clock_ns(vm_clock);
clock_gettime(CLOCK_MONOTONIC, &ts);
--
1.7.3.4
next prev parent reply other threads:[~2012-06-11 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 14:28 [Qemu-devel] [PATCH uq/master] kvm: i8254: Fix conversion of in-kernel to userspace state Jan Kiszka
2012-06-11 10:07 ` Avi Kivity
2012-06-11 10:29 ` Jan Kiszka [this message]
2012-06-11 11:18 ` [Qemu-devel] [PATCH] KVM: i8254: Clean up limit constant Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD5C89D.2010408@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).