From: Beth Kon <eak@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Add HPET emulation to qemu (v4)
Date: Fri, 14 Nov 2008 10:29:46 -0500 [thread overview]
Message-ID: <1226676586.1157.50.camel@beth-laptop> (raw)
In-Reply-To: <20081114031218.GI2055@shareable.org>
On Fri, 2008-11-14 at 03:12 +0000, Jamie Lokier wrote:
> Beth Kon wrote:
> > - enabled 64-bit capability (after discovering that OS is
> > warned in HPET spec about possibility that a 64-bit read may
> > be implemented as two 32-bit reads).
>
> It's in the spec, but are there any real x86_64 machines where 64-bit
> HPET read would be translated into two 32-bit reads? I'm wondering if
> some OSes ssume reading HPET with a 64-bit read on x86_64 is atomic,
> because that might be true. Linux seems to use HPET in 32-bit mode so
> that's safe (I checked Linux 2.6.26).
>
> -- Jamie
>
Hmm, good point. Maybe it would be safer to leave it at 32 bits.
>
--
Elizabeth Kon (Beth)
IBM Linux Technology Center
Open Hypervisor Team
email: eak@us.ibm.com
prev parent reply other threads:[~2008-11-14 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 22:04 [Qemu-devel] [PATCH 1/2] Add HPET emulation to qemu (v4) Beth Kon
2008-11-14 3:12 ` Jamie Lokier
2008-11-14 15:29 ` Beth Kon [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=1226676586.1157.50.camel@beth-laptop \
--to=eak@us.ibm.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).