From: Matt Lupfer <mlupfer@ddn.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [PATCH] Don't enable a HPET timer if HPET is disabled
Date: Wed, 26 Mar 2014 14:20:49 -0600 [thread overview]
Message-ID: <533336A1.5060803@ddn.com> (raw)
In-Reply-To: <53086768.7070200@redhat.com>
On 02/22/2014 02:01 AM, Paolo Bonzini wrote:
> Il 22/02/2014 05:37, Matt Lupfer ha scritto:
>> A HPET timer can be started when HPET is not yet
>> enabled. This will not generate an interrupt
>> to the guest, but causes problems when HPET is later
>> enabled.
>>
>> A timer that is created and expires at least once before
>> HPET is enabled will have an initialized comparator based
>> on a hpet_offset of 0 (uninitialized). When HPET is
>> enabled, hpet_set_timer() is called a second time, which
>> modifies the timer expiry to a time based on the
>> difference between current ticks (measured with the
>> newly initialized hpet_offset) and the timer's
>> comparator (which was generated before hpet_offset was
>> initialized). This results in a long period of no HPET
>> timer ticks.
>>
>> When this occurs with a CentOS 5.x guest, the guest
>> may not receive timer interrupts during its narrow
>> timer check window and panic on boot.
>>
>> Signed-off-by: Matt Lupfer <mlupfer@ddn.com>
>> ---
>> hw/timer/hpet.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
>> index 1264dfd..e15d6bc 100644
>> --- a/hw/timer/hpet.c
>> +++ b/hw/timer/hpet.c
>> @@ -506,7 +506,8 @@ static void hpet_ram_write(void *opaque, hwaddr addr,
>> timer->cmp = (uint32_t)timer->cmp;
>> timer->period = (uint32_t)timer->period;
>> }
>> - if (activating_bit(old_val, new_val, HPET_TN_ENABLE)) {
>> + if (activating_bit(old_val, new_val, HPET_TN_ENABLE) &&
>> + hpet_enabled(s)) {
>> hpet_set_timer(timer);
>> } else if (deactivating_bit(old_val, new_val, HPET_TN_ENABLE)) {
>> hpet_del_timer(timer);
>>
>
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Ping? Now that 1.7.1 is out, I hope this small patch will be considered
for the 2.0 release.
http://patchwork.ozlabs.org/patch/323121/
Matt
next prev parent reply other threads:[~2014-03-26 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 4:37 [Qemu-devel] [PATCH] Don't enable a HPET timer if HPET is disabled Matt Lupfer
2014-02-22 9:01 ` Paolo Bonzini
2014-03-26 20:20 ` Matt Lupfer [this message]
2014-03-27 12:17 ` Paolo Bonzini
2014-02-22 9:03 ` Alex Bligh
2014-02-22 10:55 ` Paolo Bonzini
2014-02-22 12:25 ` Alex Bligh
2014-02-22 14:39 ` Paolo Bonzini
2014-03-27 12:19 ` Michael S. Tsirkin
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=533336A1.5060803@ddn.com \
--to=mlupfer@ddn.com \
--cc=alex@alex.org.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).