[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] qemu/hw pckbd.c
From: |
Paul Brook |
Subject: |
Re: [Qemu-devel] qemu/hw pckbd.c |
Date: |
Thu, 19 Apr 2007 15:44:45 +0100 |
User-agent: |
KMail/1.9.5 |
> > 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 ?
I'm more concerned with what happens with devices with configurable address
ranges overlap temporarily, eg. when an OS is re-allocating PCI device memory
regions.
Paul
- [Qemu-devel] qemu/hw pckbd.c, Thiemo Seufer, 2007/04/16
- Re: [Qemu-devel] qemu/hw pckbd.c, J. Mayer, 2007/04/18
- Re: [Qemu-devel] qemu/hw pckbd.c, Thiemo Seufer, 2007/04/18
- Re: [Qemu-devel] qemu/hw pckbd.c, Jocelyn Mayer, 2007/04/18
- Re: [Qemu-devel] qemu/hw pckbd.c, Blue Swirl, 2007/04/18
- Re: [Qemu-devel] qemu/hw pckbd.c, Paul Brook, 2007/04/18
- Re: [Qemu-devel] qemu/hw pckbd.c, J. Mayer, 2007/04/19
- Re: [Qemu-devel] qemu/hw pckbd.c,
Paul Brook <=
- Re: [Qemu-devel] qemu/hw pckbd.c, Blue Swirl, 2007/04/19