From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org, reif@earthlink.net
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [RFC] 64 bit device I/O
Date: Wed, 25 Feb 2009 09:24:07 +0200 [thread overview]
Message-ID: <49A4F217.90002@redhat.com> (raw)
In-Reply-To: <49A486D1.3000305@earthlink.net>
Robert Reif wrote:
> Blue Swirl wrote:
>> 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. No one seemed interested in
> this
> approach so I abandoned it.
>
> This approach while uglier requires no changes to the hardware drivers
> unless they need 64 bit support so I hoped it would be better received.
You might try adding a struct-based 4-function interface, and
implementing the array-based 3-function interface on top of that. This
way, no immediate changes would be needed for devices, but we could
change them incrementally from the old interface to the new interface.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-02-25 7:25 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 [this message]
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
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=49A4F217.90002@redhat.com \
--to=avi@redhat.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).