qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Robert Reif <reif@earthlink.net>
Subject: Re: [Qemu-devel] [PATCH] 64 bit I/O support v7
Date: Sat, 2 May 2009 18:23:42 +0300	[thread overview]
Message-ID: <f43fc5580905020823l240871b0wa4d6be2d2be121c@mail.gmail.com> (raw)
In-Reply-To: <200905020057.23902.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On 5/2/09, Paul Brook <paul@codesourcery.com> wrote:
> > Should a new intermediate bus layer also do byte swapping?
>
>
> Yes, though a bus layer isn't actually a necessary prerequisite.
>
>  As I mentioned in the recent "Smarter compilation for target devices"
>  thread[1], having individual devices do byteswapping is bogus. A while ago I
>  reworked the TLB handling, so there should now be spare bits that can be used
>  for things like byteswapping.

This version does the byte swapping and width translation in exec.c.
Sparc32 OpenBIOS/Linux does not use the wrong sized accesses, so that
part may be untested.

Some problems:

- Small writes cause a read-modify-write cycle, but I think that may
happen with real devices too. Another solution is to write zero in
other byte lanes without reading.

- The LE/BE distinction does not seem to be very obvious for devices.
I think the board should give the is_le value to the device.

- There is a small performance hit for the native access case. This
could be avoided by extending io_mem_opaque to cover all sizes.

[-- Attachment #2: Emulate_non_native_widths.patch --]
[-- Type: application/mbox, Size: 22862 bytes --]

[-- Attachment #3: Use_new_registration_functions.patch --]
[-- Type: application/mbox, Size: 4761 bytes --]

  reply	other threads:[~2009-05-02 15:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 11:42 [Qemu-devel] [PATCH] 64 bit I/O support v7 Robert Reif
2009-05-01 12:03 ` Paul Brook
2009-05-01 13:46   ` Robert Reif
2009-05-01 14:14     ` Paul Brook
2009-05-01 14:39       ` Robert Reif
2009-05-01 14:52         ` Paul Brook
2009-05-01 15:19           ` Robert Reif
2009-05-01 15:33             ` Paul Brook
2009-05-01 15:51               ` Blue Swirl
2009-05-01 16:36                 ` Edgar E. Iglesias
2009-05-01 17:29                 ` Robert Reif
2009-05-02  0:02               ` Robert Reif
2009-05-02  0:40                 ` Paul Brook
2009-05-01 23:42             ` Robert Reif
2009-05-01 23:57               ` Paul Brook
2009-05-02 15:23                 ` Blue Swirl [this message]
2009-05-02 19:35                   ` Paul Brook
2009-05-05  1:59                   ` Jamie Lokier
2009-05-05  6:05                     ` Edgar E. Iglesias
2009-05-01 14:25   ` Robert Reif
2009-05-01 14:39     ` Paul Brook

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=f43fc5580905020823l240871b0wa4d6be2d2be121c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=reif@earthlink.net \
    /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).