[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] ioport: qemu-system-sparc64 currently broken
From: |
Mark Cave-Ayland |
Subject: |
[Qemu-devel] ioport: qemu-system-sparc64 currently broken |
Date: |
Fri, 26 Jul 2013 23:21:22 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
Hi Jan/Paolo,
I've just updated my local QEMU repository to git master for OpenBIOS
testing and it seems that the ioport changes break SPARC64. git bisect
points to this commit:
commit b40acf99bef69fa8ab0f9092ff162fde945eec12
Author: Jan Kiszka <address@hidden>
Date: Mon Jun 24 10:45:09 2013 +0200
ioport: Switch dispatching to memory core layer
The current ioport dispatcher is a complex beast, mostly due to the
need to deal with old portio interface users. But we can overcome it
without converting all portio users by embedding the required base
address of a MemoryRegionPortio access into that data structure. That
removes the need to have the additional MemoryRegionIORange structure
in the loop on every access.
To handle old portio memory ops, we simply install dispatching handlers
for portio memory regions when registering them with the memory core.
This removes the need for the old_portio field.
We can drop the additional aliasing of ioport regions and also the
special address space listener. cpu_in and cpu_out now simply call
address_space_read/write. And we can concentrate portio handling in a
single source file.
Signed-off-by: Jan Kiszka <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
I suspect that there may be multiple breakages here (as HEAD blows up
differently with a trap failure), but this is definitely the start of
the chain.
Reproducing the bug is easy - simply run qemu-system-sparc64 without any
parameters.
Many thanks,
Mark.
- [Qemu-devel] ioport: qemu-system-sparc64 currently broken,
Mark Cave-Ayland <=