On Tue, Jan 20, 2015 at 11:03:02AM +0100, Igor Mammedov wrote:
On Mon, 19 Jan 2015 23:29:37 +0200
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Jan 07, 2015 at 02:49:40PM +0800, Tang Chen wrote:
Memory and CPU hot unplug are both asynchronize procedures.
When the unplug operation
On Mon, 19 Jan 2015 23:29:37 +0200
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Jan 07, 2015 at 02:49:40PM +0800, Tang Chen wrote:
Memory and CPU hot unplug are both asynchronize procedures.
When the unplug operation happens, unplug request cb is called first.
And when ghest OS
On Wed, 7 Jan 2015 14:49:40 +0800
Tang Chen tangc...@cn.fujitsu.com wrote:
Memory and CPU 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
On Wed, Jan 07, 2015 at 02:49:40PM +0800, Tang Chen wrote:
Memory and CPU 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.
Memory and CPU 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.
They both need pc-machine, piix4 and ich9 unplug and unplug
