qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Dmitry Antipov <antipov@mvista.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to get 64-bit MMIO?
Date: Thu, 18 Feb 2010 23:39:52 +0200	[thread overview]
Message-ID: <f43fc5581002181339w252ef8e6q1e93a7a5b50a21a@mail.gmail.com> (raw)
In-Reply-To: <4B7D51A2.8080704@mvista.com>

On Thu, Feb 18, 2010 at 4:41 PM, Dmitry Antipov <antipov@mvista.com> wrote:
> Hello all,
>
> is there any support for 64-bit MMIO?

No, though there has been some discussion about it before which you
can find in the archives. 64 bit MMIO would be useful for Sparc32,
Sparc64 and Alpha.

> I'm trying to emulate 16750-like UART by adopting current 16550A emulation.
> The problem is that my (MIPS) hardware is 64-bit, and native software
> issues 64-bit load/stores (LD/SD) to talk with all hardware registers,
> which are all 64-bit too (for UART case, only 8 lower bits are used, BTW).
> As I can see, qemu splits 64-bit access into two 32-bit back-to-back ones,
> but this gives catastrophic results if host and guest has different
> byte order - i.e. write 0x0000000000000001 to 0x100 gives write 0x00000000
> to 0x100 and 0x10000000 to 0x104 because 64-bit quantities are swapped
> within
> 32-bit halves.

The numbers don't look correct. Anyway, I'd suspect the device should
do some byte swapping. Without code it's hard to tell.

      reply	other threads:[~2010-02-18 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 14:41 [Qemu-devel] How to get 64-bit MMIO? Dmitry Antipov
2010-02-18 21:39 ` 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=f43fc5581002181339w252ef8e6q1e93a7a5b50a21a@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=antipov@mvista.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).