qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Robert Reif <reif@earthlink.net>
Subject: Re: [Qemu-devel] [RFC] 64 bit device I/O
Date: Wed, 25 Feb 2009 11:55:57 +0000	[thread overview]
Message-ID: <200902251155.58408.paul@codesourcery.com> (raw)
In-Reply-To: <49A486D1.3000305@earthlink.net>

> > Would it be better to use a structure with four elements with correct
> > types (including uint8/16_t)  instead of the cast? This could also be
> > limited to only cpu_register_io_memory64.
>
> This is what I would prefer and is what the first version of this patch
> that I submitted a year ago did:   http://landley.net/qemu/2008-01-01.html
>
> The problem is that every hardware driver would need to be changed and
> some of them would need to be changed drastically because they use the
> same functions for all three data sizes.

You can always use the same prototype for the first 3 functions. In practice 
there's very little benefit for using types smaller than 32-bit on machines 
capable of runnit qemu.

Paul

      parent reply	other threads:[~2009-02-25 11:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 15:05 [Qemu-devel] [RFC] 64 bit device I/O Robert Reif
2009-02-24 12:50 ` Robert Reif
2009-02-24 20:16   ` Blue Swirl
2009-02-24 23:46     ` Robert Reif
2009-02-25  7:24       ` Avi Kivity
2009-02-25  7:25       ` Avi Kivity
2009-02-25 11:55         ` Robert Reif
2009-02-25 20:02           ` Blue Swirl
2009-02-25 11:55       ` Paul Brook [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=200902251155.58408.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=blauwirbel@gmail.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).