On 04/01/2015 04:42 PM, Igor Mammedov wrote:
On Fri, 27 Mar 2015 17:20:33 +0800
Zhu Guihua wrote:
Memory hot unplug are both asynchronous procedures.
When the unplug operation happens, unplug request cb is called first.
And when guest OS finished handling unplug, unplug cb will be called
to d
On Fri, 27 Mar 2015 17:20:33 +0800
Zhu Guihua wrote:
> Memory hot unplug are both asynchronous procedures.
> When the unplug operation happens, unplug request cb is called first.
> And when guest OS finished handling unplug, unplug cb will be called
> to do the real removal of device.
I think ser
On 30/03/2015 04:53, Zhu Guihua wrote:
> Question:
>
> When migrating from old qemu to one with this hot remove feature, I found
> this feature would not work any more in new qemu.
>
> The reason is that DSDT table will not re-generate in new qemu when
> migration.
> So the hot remove will not
Question:
When migrating from old qemu to one with this hot remove feature, I found
this feature would not work any more in new qemu.
The reason is that DSDT table will not re-generate in new qemu when
migration.
So the hot remove will not work in the new qemu even though qemu
has this feature
Memory hot unplug are both asynchronous procedures.
When the unplug operation happens, unplug request cb is called first.
And when guest OS finished handling unplug, unplug cb will be called
to do the real removal of device.
v5:
-reorganize the patchset
-add documentation to understand patch eas
