From: Eric Blake <eblake@redhat.com>
To: Peng Hao <peng.hao2@zte.com.cn>, mst@redhat.com, pbonzini@redhat.com
Cc: Liu Yi <liu.yi24@zte.com.cn>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V3] rtc: fix a infinite loop in windows vm startup
Date: Mon, 24 Jul 2017 06:54:52 -0500 [thread overview]
Message-ID: <961f88c4-c863-5242-c38a-f86dfa6834ee@redhat.com> (raw)
In-Reply-To: <1500921322-36875-1-git-send-email-peng.hao2@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On 07/24/2017 01:35 PM, 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.
>
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> Signed-off-by: Liu Yi <liu.yi24@zte.com.cn>
> ---
When posting a v3, it's useful to tell us (after the --- separator) what
changed from v2, to help us focus on why a v3 was needed.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-24 11:55 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
2017-07-24 11:54 ` Eric Blake [this message]
-- 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=961f88c4-c863-5242-c38a-f86dfa6834ee@redhat.com \
--to=eblake@redhat.com \
--cc=liu.yi24@zte.com.cn \
--cc=mst@redhat.com \
--cc=pbonzini@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).