From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
Alexey Eromenko <aeromenk@redhat.com>,
"Yang, Sheng" <sheng.yang@intel.com>
Subject: Re: KVM: PIT: fix count read and mode 0 handling
Date: Thu, 09 Apr 2009 18:30:08 +0300 [thread overview]
Message-ID: <49DE1480.6000907@redhat.com> (raw)
In-Reply-To: <20090408161419.GA16804@amt.cnet>
Marcelo Tosatti wrote:
> Commit 46ee278652f4cbd51013471b64c7897ba9bcd1b1 causes Solaris 10
> to hang on boot.
>
> Assuming that PIT counter reads should return 0 for an expired timer
> is wrong: when it is active, the counter never stops (see comment on
> __kpit_elapsed).
>
> Also arm a one shot timer for mode 0.
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-04-09 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 13:53 solaris 10 x86 regression due to timer Avi Kivity
2009-04-08 16:14 ` KVM: PIT: fix count read and mode 0 handling Marcelo Tosatti
2009-04-09 15:30 ` Avi Kivity [this message]
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=49DE1480.6000907@redhat.com \
--to=avi@redhat.com \
--cc=aeromenk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng.yang@intel.com \
/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