qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org, imammedo@redhat.com, mst@redhat.com,
	pbonzini@redhat.com
Cc: guz.fnst@cn.fujitsu.com, hutao@cn.fujitsu.com,
	isimatu.yasuaki@jp.fujitsu.com, tangchen@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v4 0/7] QEMU memory hot unplug support
Date: Fri, 13 Mar 2015 14:05:08 +0800	[thread overview]
Message-ID: <55027E14.6090703@cn.fujitsu.com> (raw)
In-Reply-To: <cover.1425379856.git.zhugh.fnst@cn.fujitsu.com>

ping...

On 03/04/2015 02:01 PM, 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.
>
> This series is rebased on mst pci branch.
> http://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
>
> v4:
>   -reorganize the patchset
>   -fix all about 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 (6):
>    acpi, mem-hotplug: Add acpi_memory_slot_status() to get MemStatus
>    acpi: Add acpi_send_gpe_event() to rise sci for hotplug
>    acpi, mem-hotplug: Add unplug request cb for memory device
>    pc-dimm: Add memory hot unplug request support for pc-dimm
>    acpi, mem-hotplug: Add unplug cb for memory device
>    pc-dimm: Add memory hot unplug support for pc-dimm
>
> Zhu Guihua (1):
>    acpi: Add hardware implementation for memory hot unplug
>
>   docs/specs/acpi_mem_hotplug.txt   | 11 +++++-
>   hw/acpi/core.c                    |  7 ++++
>   hw/acpi/cpu_hotplug.c             |  3 +-
>   hw/acpi/ich9.c                    | 19 +++++++--
>   hw/acpi/memory_hotplug.c          | 81 +++++++++++++++++++++++++++++++++------
>   hw/acpi/pcihp.c                   |  7 +---
>   hw/acpi/piix4.c                   | 16 ++++++--
>   hw/core/qdev.c                    |  2 +-
>   hw/i386/acpi-build.c              |  9 +++++
>   hw/i386/acpi-dsdt-mem-hotplug.dsl | 10 +++++
>   hw/i386/pc.c                      | 54 ++++++++++++++++++++++++--
>   include/hw/acpi/acpi.h            | 10 +++++
>   include/hw/acpi/memory_hotplug.h  |  8 +++-
>   include/hw/acpi/pc-hotplug.h      |  3 +-
>   include/hw/qdev-core.h            |  1 +
>   trace-events                      |  1 +
>   16 files changed, 207 insertions(+), 35 deletions(-)
>

       reply	other threads:[~2015-03-13  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1425379856.git.zhugh.fnst@cn.fujitsu.com>
2015-03-13  6:05 ` Zhu Guihua [this message]
2015-03-13 11:07   ` [Qemu-devel] [PATCH v4 0/7] QEMU memory hot unplug support Igor Mammedov
2015-03-16  0:59     ` Zhu Guihua

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=55027E14.6090703@cn.fujitsu.com \
    --to=zhugh.fnst@cn.fujitsu.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=mst@redhat.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).