From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] qemu/hw pckbd.c
Date: Thu, 19 Apr 2007 10:43:32 +0200 [thread overview]
Message-ID: <1176972212.6333.101.camel@rapid> (raw)
In-Reply-To: <200704181708.22450.paul@codesourcery.com>
On Wed, 2007-04-18 at 17:08 +0100, Paul Brook wrote:
> > > If you're interressed in such a feature, you may take a look of what
> > > I've done in hw/ppc405_uc.c. There are some device sharing the same
> > > memory page on those microcontrollers so I introduced a fake device
> > > called mmio that allow to register multiple devices into a single page
> > > in Qemu. I do use the serial_mm_init with the ioregister parameter set
> > > to 0 for those designs.
> > > This code may not be as generic as it would be if we want to make it a
> > > standard Qemu function, but this may give a basis or ideas for it.
> >
> > On Sparc32 there are several devices that would benefit from sub-page
> > granularity, so I vote for making this generic.
>
> While you're fixing this, it would be good to fix overlapping devices as
> well ;-) Currently if you (temporarily) have overlapping regions then remove
> one of them you end up with unmapped memory.
What is the correct behavior in such a case ? What device would you
actually see ? May be it different to one architecture to another ?
I think there are busses and/or architectures where this is not
possible, you would only get a fault on the bus in such a case. So it
seems to me not to be easy to find a generic and appropriate way to fix
this behavior, don't you think ?
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-04-19 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 22:47 [Qemu-devel] qemu/hw pckbd.c Thiemo Seufer
2007-04-18 9:29 ` J. Mayer
2007-04-18 13:06 ` Thiemo Seufer
2007-04-18 14:20 ` Jocelyn Mayer
2007-04-18 15:37 ` Blue Swirl
2007-04-18 16:08 ` Paul Brook
2007-04-19 8:43 ` J. Mayer [this message]
2007-04-19 14:44 ` Paul Brook
2007-04-19 18:15 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2008-02-10 13:39 Andrzej Zaborowski
2007-10-20 20:48 Thiemo Seufer
2007-02-18 0:08 Thiemo Seufer
2005-01-27 22:32 Fabrice Bellard
2005-01-17 22:31 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=1176972212.6333.101.camel@rapid \
--to=l_indien@magic.fr \
--cc=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).