From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RFC] 64 bit i/o
Date: Wed, 2 Jan 2008 20:17:42 +0200 [thread overview]
Message-ID: <f43fc5580801021017k416451f7hc459b29945196c9b@mail.gmail.com> (raw)
In-Reply-To: <477BADB1.30400@charter.net>
On 1/2/08, Brian Johnson <bjj4@charter.net> wrote:
> Robert Reif wrote:
> > Paul Brook wrote:
> >>
> >> Couldn't you just latch the value when one half is accessed?
> >>
> > 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.
>
> Agreed. Some non-PC hardware has 64-bit registers which need to be
> accessed as 64-bit quantities, in order to read or write all fields at
> once. Qemu should support 64-bit I/O.
On Sparc64 many registers can only be handled using 64 bit accesses,
other methods should raise an exception.
prev parent reply other threads:[~2008-01-02 18:17 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
2008-01-02 15:28 ` [Qemu-devel] " Brian Johnson
2008-01-02 18:17 ` Blue Swirl [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=f43fc5580801021017k416451f7hc459b29945196c9b@mail.gmail.com \
--to=blauwirbel@gmail.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).