On 09/11/2012 12:32 PM, liu ping fan wrote: > On Tue, Sep 11, 2012 at 4:32 PM, Avi Kivity <a...@redhat.com> wrote: >> On 09/11/2012 10:51 AM, Liu Ping Fan wrote: >>> From: Liu Ping Fan <pingf...@linux.vnet.ibm.com> >>> >>> DeviceState will be protected by refcnt from disappearing during >>> dispatching. But when refcnt comes down to zero, DeviceState may >>> be still in use by iohandler, timer etc in main loop, we just delay >>> its free untill no reader. >>> >> >> How can this be? We elevate the refcount while dispatching I/O. If we >> have similar problems with the timer, we need to employ a similar solution. >> > Yes, at the next step, plan to covert iohandler, timer etc to use > refcount as memory. Here just a temp solution.
I prefer not to ever introduce it. What we can do is introduce a sub-region for e1000's mmio that will take only the device lock, and let original region use the old dispatch path (and also take the device lock). As we thread the various subsystems e1000 uses, we can expand the sub-region until it covers all of e1000's functions, then fold it back into the main region. To start with the sub-region can only include registers that call no qemu infrastructure code: simple read/writes. -- error compiling committee.c: too many arguments to function
