qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Cc: hutao@cn.fujitsu.com, qemu-devel@nongnu.org,
	tangchen@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	pbonzini@redhat.com, guz.fnst@cn.fujitsu.com,
	imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug
Date: Wed, 28 Jan 2015 10:00:45 +0200	[thread overview]
Message-ID: <20150128080045.GB16698@redhat.com> (raw)
In-Reply-To: <cover.1422429010.git.zhugh.fnst@cn.fujitsu.com>

On Wed, Jan 28, 2015 at 03:45:36PM +0800, Zhu Guihua wrote:
> Memory and CPU 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.
> 
> They both need pc-machine, piix4 and ich9 unplug and unplug request cb.
> So this patchset introduces these commom functions as part1, and memory
> and CPU hot-unplug will come soon as part 2 and 3.
> 
> This patch-set is based on QEmu 2.2

Really? Why not on master?

> v2:
> - Commit messages changes
> 
> Tang Chen (5):
>   acpi, pc: Add hotunplug request cb for pc machine.
>   acpi, ich9: Add hotunplug request cb for ich9.
>   acpi, pc: Add unplug cb for pc machine.
>   acpi, ich9: Add unplug cb for ich9.
>   acpi, piix4: Add unplug cb for piix4.
> 
>  hw/acpi/ich9.c         | 14 ++++++++++++++
>  hw/acpi/piix4.c        |  8 ++++++++
>  hw/i386/pc.c           | 16 ++++++++++++++++
>  hw/isa/lpc_ich9.c      | 14 ++++++++++++--
>  include/hw/acpi/ich9.h |  4 ++++
>  5 files changed, 54 insertions(+), 2 deletions(-)
> 
> -- 
> 1.9.3

  parent reply	other threads:[~2015-01-28  8:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  7:45 [Qemu-devel] [PATCH v2 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 1/5] acpi, pc: Add hotunplug request cb for pc machine Zhu Guihua
2015-01-28  8:02   ` Michael S. Tsirkin
2015-01-28  8:33     ` Zhu Guihua
2015-01-28  8:39       ` Michael S. Tsirkin
2015-01-28  8:42         ` Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 2/5] acpi, ich9: Add hotunplug request cb for ich9 Zhu Guihua
2015-01-28  7:59   ` Michael S. Tsirkin
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 3/5] acpi, pc: Add unplug cb for pc machine Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 4/5] acpi, ich9: Add unplug cb for ich9 Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 5/5] acpi, piix4: Add unplug cb for piix4 Zhu Guihua
2015-01-28  8:00 ` Michael S. Tsirkin [this message]
2015-01-28  8:18   ` [Qemu-devel] [PATCH v2 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Zhu Guihua
2015-01-29  3:19 ` Zhu Guihua
2015-02-03  8:39 ` Zhi Yong Wu

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=20150128080045.GB16698@redhat.com \
    --to=mst@redhat.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tangchen@cn.fujitsu.com \
    --cc=zhugh.fnst@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).