From: Paolo Bonzini <pbonzini@redhat.com>
To: Peng Hao <peng.hao2@zte.com.cn>, mst@redhat.com
Cc: qemu-devel@nongnu.org, Liu Yi <liu.yi24@zte.com.cn>
Subject: Re: [Qemu-devel] [PATCH V3] rtc: fix a infinite loop in windows vm startup
Date: Mon, 24 Jul 2017 13:53:04 +0200 [thread overview]
Message-ID: <e2d87744-a823-977a-df1f-dc54d664e5e3@redhat.com> (raw)
In-Reply-To: <1500921322-36875-1-git-send-email-peng.hao2@zte.com.cn>
On 24/07/2017 20:35, Peng Hao wrote:
> When a windows vm starts, periodic timer of rtc will stop several times.
> windows kernel will check whether REG_A_UIP is changed. REG_C's interrupt
> flags will not be cleared when periodic timer stops and the update timer
> will switch to alarm timer. So the expiration time of alarm timer is very
> long and REG_A_UIP will not vary.At last windows kernel will repeat to
> check REG_A_UIP all the time.
This should not happen. REG_A_UIP is set and cleared in register A
every second, like this:
case RTC_REG_A:
if (update_in_progress(s)) {
s->cmos_data[s->cmos_index] |= REG_A_UIP;
} else {
s->cmos_data[s->cmos_index] &= ~REG_A_UIP;
}
ret = s->cmos_data[s->cmos_index];
break;
where update_in_progress does:
guest_nsec = get_guest_rtc_ns(s);
/* UIP bit will be set at last 244us of every second. */
if ((guest_nsec % NANOSECONDS_PER_SECOND) >=
(NANOSECONDS_PER_SECOND - UIP_HOLD_LENGTH)) {
return 1;
}
return 0;
This is done even if the timer is not pending.
How can the bug be reproduced?
Paolo
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> Signed-off-by: Liu Yi <liu.yi24@zte.com.cn>
> ---
> hw/timer/mc146818rtc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/hw/timer/mc146818rtc.c b/hw/timer/mc146818rtc.c
> index 1b8d3d7..aa55fae 100644
> --- a/hw/timer/mc146818rtc.c
> +++ b/hw/timer/mc146818rtc.c
> @@ -457,6 +457,8 @@ static void rtc_update_timer(void *opaque)
> if ((new_irqs & s->cmos_data[RTC_REG_B]) != 0) {
> s->cmos_data[RTC_REG_C] |= REG_C_IRQF;
> qemu_irq_raise(s->irq);
> + } else if ((s->cmos_data[RTC_REG_B] & REG_B_UIE) == 0) {
> + s->cmos_data[RTC_REG_C] &= ~REG_C_UF;
> }
> check_update_timer(s);
> }
> @@ -559,7 +561,7 @@ static void cmos_ioport_write(void *opaque, hwaddr addr,
> s->cmos_data[RTC_REG_C] |= REG_C_IRQF;
> qemu_irq_raise(s->irq);
> } else {
> - s->cmos_data[RTC_REG_C] &= ~REG_C_IRQF;
> + s->cmos_data[RTC_REG_C] &= ~(REG_C_UF | REG_C_IRQF);
> qemu_irq_lower(s->irq);
> }
> s->cmos_data[RTC_REG_B] = data;
>
next prev parent reply other threads:[~2017-07-24 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 18:35 [Qemu-devel] [PATCH V3] rtc: fix a infinite loop in windows vm startup Peng Hao
2017-07-24 11:53 ` Paolo Bonzini [this message]
2017-07-24 11:54 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2017-07-25 4:14 peng.hao2
2017-07-25 7:17 ` Paolo Bonzini
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=e2d87744-a823-977a-df1f-dc54d664e5e3@redhat.com \
--to=pbonzini@redhat.com \
--cc=liu.yi24@zte.com.cn \
--cc=mst@redhat.com \
--cc=peng.hao2@zte.com.cn \
--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).