From: "Blue Swirl" <blauwirbel@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu cpu-all.h exec.c
Date: Wed, 2 Jan 2008 19:31:43 +0200 [thread overview]
Message-ID: <f43fc5580801020931v6166c8a2q2d6526bec4e91e73@mail.gmail.com> (raw)
In-Reply-To: <200801021718.06316.paul@codesourcery.com>
On 1/2/08, Paul Brook <paul@codesourcery.com> wrote:
> > Also the opaque parameter may need to be different for each function,
> > it just didn't matter for the unassigned memory case.
>
> Do you really have systems where independent devices need to respond to
> different sized accesses to the same address?
I don't think so. But one day unassigned or even normal RAM memory
access may need an opaque parameter, so passing the device's opaque to
unassigned memory handler is wrong.
next prev parent reply other threads:[~2008-01-02 17:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 16:57 [Qemu-devel] qemu cpu-all.h exec.c Blue Swirl
2008-01-01 21:42 ` Fabrice Bellard
2008-01-02 16:42 ` Blue Swirl
2008-01-02 17:18 ` Paul Brook
2008-01-02 17:31 ` Blue Swirl [this message]
2008-01-03 1:18 ` Paul Brook
2008-01-03 15:57 ` Blue Swirl
2008-01-03 16:12 ` Paul Brook
2008-01-03 16:53 ` Fabrice Bellard
2008-01-03 19:44 ` Blue Swirl
2008-01-03 20:16 ` Paul Brook
2008-01-04 20:36 ` Blue Swirl
2008-01-04 22:43 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2007-05-26 17:36 Blue Swirl
2007-04-04 7:55 Jocelyn Mayer
2005-10-30 20:48 Fabrice Bellard
2005-02-10 21:56 Fabrice Bellard
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=f43fc5580801020931v6166c8a2q2d6526bec4e91e73@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=paul@codesourcery.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).