From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] 64 bit i/o
Date: Wed, 02 Jan 2008 09:54:35 -0500 [thread overview]
Message-ID: <477BA5AB.6030406@earthlink.net> (raw)
In-Reply-To: <200801021401.13611.paul@codesourcery.com>
Paul Brook wrote:
>On Wednesday 02 January 2008, Robert Reif wrote:
>
>
>>Sparc32 has a 64 bit counter that should be read and written as 64
>>bits but that isn't supported in QEMU. I did a quick hack to add
>>64 bit i/o and converted sparc32 to use it and it seems to work.
>>I'm suppling the sparc changes to get comments on if this is worth
>>pursuing.
>>
>>
>
>Couldn't you just latch the value when one half is accessed?
>
>Paul
>
>
>
>
>
In this one specific case you could do that but this is not the only
case in sparc32
(TOD, MXCC, ...) and other architectures with 64 bit hardware have similar
requirements.
This is a generic solution that fills a hole in the qemu implementation.
next prev parent reply other threads:[~2008-01-02 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 3:29 [Qemu-devel] [RFC] 64 bit i/o Robert Reif
2008-01-02 14:01 ` Paul Brook
2008-01-02 14:54 ` Robert Reif [this message]
2008-01-02 15:28 ` [Qemu-devel] " Brian Johnson
2008-01-02 18:17 ` Blue Swirl
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=477BA5AB.6030406@earthlink.net \
--to=reif@earthlink.net \
--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).