Re: [Qemu-devel] [PATCH v2 00/12] QEmu memory hot unplug support

2015-02-10 Thread Igor Mammedov
On Wed, 4 Feb 2015 10:51:14 +0800 Zhu Guihua wrote: > Memory hot unplug are both asynchronize procedures. > When the unplug operation happens, unplug request cb is called first. > And when ghest OS finished handling unplug, unplug cb will be called > to do the real removal of device. please chec

Re: [Qemu-devel] [PATCH v2 00/12] QEmu memory hot unplug support

2015-02-04 Thread Zhu Guihua
On Wed, 2015-02-04 at 11:28 +0100, Michael S. Tsirkin wrote: > Re: subject - it's really QEMU - not QEmu. > > you have this in code as well, so I'm guessing you didn't > run your patches through checkpatch.pl. Please do > and fix fallout if any. I do it now, and I find warnings about this. I will

Re: [Qemu-devel] [PATCH v2 00/12] QEmu memory hot unplug support

2015-02-04 Thread Michael S. Tsirkin
Re: subject - it's really QEMU - not QEmu. you have this in code as well, so I'm guessing you didn't run your patches through checkpatch.pl. Please do and fix fallout if any. -- MST

[Qemu-devel] [PATCH v2 00/12] QEmu memory hot unplug support

2015-02-03 Thread Zhu Guihua
Memory hot unplug are both asynchronize procedures. When the unplug operation happens, unplug request cb is called first. And when ghest OS finished handling unplug, unplug cb will be called to do the real removal of device. This series depends on the following patchset. [PATCH v2 0/5] Common unpl