From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: zhugh.fnst@cn.fujitsu.com, hutao@cn.fujitsu.com,
qemu-devel@nongnu.org, Tang Chen <tangchen@cn.fujitsu.com>,
isimatu.yasuaki@jp.fujitsu.com, guz.fnst@cn.fujitsu.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RESEND PATCH v1 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug.
Date: Tue, 20 Jan 2015 11:03:02 +0100 [thread overview]
Message-ID: <20150120110302.64dfcde3@nial.brq.redhat.com> (raw)
In-Reply-To: <20150119212937.GA10385@redhat.com>
On Mon, 19 Jan 2015 23:29:37 +0200
"Michael S. Tsirkin" <mst@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 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 patch set 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
>
> OK, Igor - you only have comments for the commit log?
> I take this as implicit ack of the patches?
> If so pls let me know.
Yes, patches themselves are good.
Can fixup commit messages and add author SoBs to them, before
applying or should we wait for respin?
> > 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.8.4.2
next prev parent reply other threads:[~2015-01-20 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 6:49 [Qemu-devel] [RESEND PATCH v1 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Tang Chen
2015-01-07 6:49 ` [Qemu-devel] [RESEND PATCH v1 1/5] acpi, pc: Add hotunplug request cb for pc machine Tang Chen
2015-01-07 6:49 ` [Qemu-devel] [RESEND PATCH v1 2/5] acpi, ich9: Add hotunplug request cb for ich9 Tang Chen
2015-01-19 17:26 ` Igor Mammedov
2015-01-07 6:49 ` [Qemu-devel] [RESEND PATCH v1 3/5] acpi, pc: Add unplug cb for pc machine Tang Chen
2015-01-19 17:29 ` Igor Mammedov
2015-01-07 6:49 ` [Qemu-devel] [RESEND PATCH v1 4/5] acpi, ich9: Add unplug cb for ich9 Tang Chen
2015-01-19 17:34 ` Igor Mammedov
2015-01-07 6:49 ` [Qemu-devel] [RESEND PATCH v1 5/5] acpi, piix4: Add unplug cb for piix4 Tang Chen
2015-01-19 17:37 ` Igor Mammedov
2015-01-19 17:40 ` [Qemu-devel] [RESEND PATCH v1 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Igor Mammedov
2015-01-19 21:29 ` Michael S. Tsirkin
2015-01-20 10:03 ` Igor Mammedov [this message]
2015-01-20 10:40 ` Michael S. Tsirkin
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=20150120110302.64dfcde3@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hutao@cn.fujitsu.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 \
--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).