On Wed, 2015-04-08 at 11:52 +0200, Michael S. Tsirkin wrote: > On Wed, Apr 08, 2015 at 05:49:42PM +0800, Zhu Guihua wrote: > > Ping... > > It's only been 4 days. We are finalizing 2.3 so pls sit tight.
I agree with Michael, it's time to close 2.3. But I have a question. Is the patch counter correct? I didn't found the patch 1/8 in my mailbox neither in qemu-devel archive. > > > > > On 04/02/2015 05:50 PM, Zhu Guihua wrote: > > >This patchset adds support to hot unplug memory. > > > > > >Memory hot unplug is complicated multi-stage process. Unplug request > > >callback > > >sends remove request. After guest os processes ejection request, OSPM will > > >execute _EJ0 to signal qemu that a device eject will be to occur. Then qemu > > >will call unplug callback to eject the device. > > > > > >v6: > > > -improve documentation of memory hot unplug > > > -add trace event for device deletion > > > -put fix about "Memory device control fields" register in a separate > > > patch > > > > > >v5: > > > -reorganize the patchset > > > -add documentation to understand patch easily > > > -add MEMORY_SLOT_EJECT for initiating device eject > > > -add support to send qmp event to notify mgmt about memory unplug error > > > > > >v4: > > > -reorganize the patchset > > > -drop the new API acpi_send_gpe_event() > > > -update ssdt-mem > > > > > >v3: > > > -commit message changes > > > -reorganize the patchset, squash and separate some patches > > > -update specs about acpi_mem_hotplug > > > -first cleanup external state, then un-map and un-register memory device > > > > > >v2: > > > -do a generic for acpi to send gpe event > > > -unparent object by PC_MACHINE > > > -update description in acpi_mem_hotplug.txt > > > -combine the last two patches in the last version > > > -cleanup external state in acpi_memory_unplug_cb > > > > > >Tang Chen (3): > > > acpi, mem-hotplug: add acpi_memory_slot_status() to get MemStatus > > > acpi, mem-hotplug: add unplug request cb for memory device > > > acpi, mem-hotplug: add unplug cb for memory device > > > > > >Zhu Guihua (5): > > > docs: update documentation for memory hot unplug > > > acpi: extend aml_field() to support UpdateRule > > > acpi: fix "Memory device control fields" register > > > acpi: add hardware implementation for memory hot unplug > > > qmp-event: add event notification for memory hot unplug error > > > > > > docs/memory-hotplug.txt | 23 ++++++++-- > > > docs/qmp/qmp-events.txt | 17 +++++++ > > > docs/specs/acpi_mem_hotplug.txt | 58 +++++++++++++++++++++-- > > > hw/acpi/aml-build.c | 4 +- > > > hw/acpi/ich9.c | 19 ++++++-- > > > hw/acpi/memory_hotplug.c | 96 > > > ++++++++++++++++++++++++++++++++++++--- > > > hw/acpi/piix4.c | 17 +++++-- > > > hw/core/qdev.c | 2 +- > > > hw/i386/acpi-build.c | 25 ++++++++-- > > > hw/i386/acpi-dsdt-mem-hotplug.dsl | 13 +++++- > > > hw/i386/pc.c | 62 +++++++++++++++++++++++-- > > > include/hw/acpi/aml-build.h | 10 +++- > > > include/hw/acpi/memory_hotplug.h | 12 +++++ > > > include/hw/acpi/pc-hotplug.h | 3 ++ > > > include/hw/qdev-core.h | 1 + > > > monitor.c | 1 + > > > qapi/event.json | 14 ++++++ > > > trace-events | 4 ++ > > > 18 files changed, 346 insertions(+), 35 deletions(-) > > > > -- Paulo Ricardo Paz Vital <paulo.vi...@profitbricks.com> ProfitBricks GmbH
