qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH V9 0/8] memory: unify ioport registration


From: Julien Grall
Subject: Re: [Qemu-devel] [PATCH V9 0/8] memory: unify ioport registration
Date: Tue, 11 Sep 2012 12:27:05 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120726 Icedove/3.0.11

On 09/11/2012 10:25 AM, Avi Kivity wrote:
On 09/11/2012 12:15 PM, Avi Kivity wrote:
On 09/04/2012 06:13 PM, Julien Grall wrote:
This is the nineth version of patch series about ioport registration.

Some part of QEMU still use register_ioport* functions to register ioport.
These functions doesn't allow to use Memory Listener on it.
Thanks, applied all (w/ updated patch 4), will push shortly.


Aborts with the command line

   qemu-system-x86_64 -device isa-debugcon,iobase=0x402,chardev=stdio -chardev 
stdio,id=stdio



I have bisected and found the problem with bochs_bios_init in hw/pc.c.
Bosch already register the iport 0x402. I'm not sure that it's a bug.
In fact register_ioport_read/write check if the current ioport is used
with the opaque variable.
Before my patch, bochs_bios_init registered it's ioport with opaque
NULL, so if someone (like debugcon) wants to use the ioport there is
no problem. But now, I used portio_list_init to register bochs ioport,
so the opaque is not NULL.
I don't really know how to resolve this problem. Perhaps we could
just improve the debug message.

--
Julien Grall



reply via email to

[Prev in Thread] Current Thread [Next in Thread]