On 08/10/2012 09:44 AM, liu ping fan wrote:
In the previous discussion, you have suggest add dev-ref++ in
core_region_add. But I think, if we can move it to higher layer --
memory_region_{add,del}_subregion, so we can avoid to duplicate do
this in other xx_region_add.
Why would other memory
On Thu, Aug 9, 2012 at 4:38 PM, Avi Kivity a...@redhat.com wrote:
On 08/09/2012 10:27 AM, liu ping fan wrote:
On Wed, Aug 8, 2012 at 5:20 PM, Avi Kivity a...@redhat.com wrote:
On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Using refcnt for mr, so
On Wed, Aug 8, 2012 at 5:20 PM, Avi Kivity a...@redhat.com wrote:
On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Using refcnt for mr, so we can separate mr's life cycle management
from refered object.
When mr-ref 0-1, inc the refered object.
On 08/09/2012 10:27 AM, liu ping fan wrote:
On Wed, Aug 8, 2012 at 5:20 PM, Avi Kivity a...@redhat.com wrote:
On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Using refcnt for mr, so we can separate mr's life cycle management
from refered object.
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Using refcnt for mr, so we can separate mr's life cycle management
from refered object.
When mr-ref 0-1, inc the refered object.
When mr-ref 1-0, dec the refered object.
The refered object can be DeviceStae, another mr, or other opaque.
On 08/08/2012 09:25 AM, Liu Ping Fan wrote:
From: Liu Ping Fan pingf...@linux.vnet.ibm.com
Using refcnt for mr, so we can separate mr's life cycle management
from refered object.
When mr-ref 0-1, inc the refered object.
When mr-ref 1-0, dec the refered object.
The refered object can
