From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: paulo.vital@profitbricks.com, "Michael S. Tsirkin" <mst@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org,
tangchen@cn.fujitsu.com, izumi.taku@jp.fujitsu.com,
guz.fnst@cn.fujitsu.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/8] QEMU memory hot unplug support
Date: Thu, 9 Apr 2015 09:16:21 +0800 [thread overview]
Message-ID: <5525D2E5.3000407@cn.fujitsu.com> (raw)
In-Reply-To: <1428490058.9667.11.camel@profitbricks.com>
On 04/08/2015 06:47 PM, Paulo Ricardo Paz Vital wrote:
> 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.
My partners have received patch 1/8, but it is not in qemu-devel archive
indeed. I don't
know what happened.
I will resend the series later.
Thanks,
Zhu
>
>>> 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(-)
>>>>
next prev parent reply other threads:[~2015-04-09 1:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 9:50 [Qemu-devel] [PATCH v6 0/8] QEMU memory hot unplug support Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 2/8] acpi, mem-hotplug: add acpi_memory_slot_status() to get MemStatus Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 3/8] acpi, mem-hotplug: add unplug request cb for memory device Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 4/8] acpi, mem-hotplug: add unplug " Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 5/8] acpi: extend aml_field() to support UpdateRule Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 6/8] acpi: fix "Memory device control fields" register Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 7/8] acpi: add hardware implementation for memory hot unplug Zhu Guihua
2015-04-02 9:50 ` [Qemu-devel] [PATCH v6 8/8] qmp-event: add event notification for memory hot unplug error Zhu Guihua
2015-04-10 15:37 ` Eric Blake
2015-04-13 1:56 ` Zhu Guihua
2015-04-13 14:40 ` Eric Blake
2015-04-13 14:43 ` Paolo Bonzini
2015-04-08 9:49 ` [Qemu-devel] [PATCH v6 0/8] QEMU memory hot unplug support Zhu Guihua
2015-04-08 9:52 ` Michael S. Tsirkin
2015-04-08 10:47 ` Paulo Ricardo Paz Vital
2015-04-09 1:16 ` Zhu Guihua [this message]
2015-04-09 8:28 ` Igor Mammedov
2015-04-09 10:01 ` Zhu Guihua
2015-04-10 15:17 ` Igor Mammedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5525D2E5.3000407@cn.fujitsu.com \
--to=zhugh.fnst@cn.fujitsu.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=mst@redhat.com \
--cc=paulo.vital@profitbricks.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tangchen@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).