From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, tangchen@cn.fujitsu.com,
isimatu.yasuaki@jp.fujitsu.com,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
chen.fan.fnst@cn.fujitsu.com,
"Jason J. Herne" <jjherne@us.ibm.com>,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 0/5] cpu/acpi: convert cpu hot plug to hotplug_handler API
Date: Thu, 11 Sep 2014 10:53:57 +0800 [thread overview]
Message-ID: <54110EC5.5030603@cn.fujitsu.com> (raw)
In-Reply-To: <20140910161253.718d2b2b@nial.usersys.redhat.com>
Hi Igor,
Thanks very much for your review and suggestion.
On 09/10/2014 10:12 PM, Igor Mammedov wrote:
> On Wed, 3 Sep 2014 17:06:12 +0800
> Gu Zheng <guz.fnst@cn.fujitsu.com> wrote:
>
>>
>> Gu Zheng (5):
>> acpi/cpu: add cpu hotplug callback function to match hotplug_handler
>> API
>> acpi:ich9: convert cpu hotplug handle to hotplug_handler API
>> acpi:piix4: convert cpu hotplug handle to hotplug_handler API
>> pc: add cpu hotplug handler to PC_MACHINE
>> cpu/hotplug: remove the left unused cpu hotplug notifier function
>>
>> hw/acpi/cpu_hotplug.c | 18 ++++++++++++------
>> hw/acpi/ich9.c | 15 +++------------
>> hw/acpi/piix4.c | 16 +++-------------
>> hw/i386/pc.c | 26 +++++++++++++++++++++++++-
>> include/hw/acpi/cpu_hotplug.h | 6 ++++--
>> include/hw/acpi/ich9.h | 1 -
>> qom/cpu.c | 1 -
>> 7 files changed, 47 insertions(+), 36 deletions(-)
>>
>
> Looks like right direction that would allow to drop cpu_added_notifiers
> which is not able to pass/handle errors and switch to unified hotplug handler
> API which allows to pass errors and would allow to cancel device_add in case of
> error.
It seems the key value we can gain from above change, I'll follow your suggestion.
>
> PS:
> Gu Zheng,
>
> Please grep for qemu_register_cpu_added_notifier(), you've missed to convert
> rtc usage of CPU notifier.
Thanks for your reminder.
>
> I'd prefer this to go in before you device_add/add cpu series.
OK, I'll work on this series first.
Best regards,
Gu
> .
>
prev parent reply other threads:[~2014-09-11 3:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 9:06 [Qemu-devel] [PATCH 0/5] cpu/acpi: convert cpu hot plug to hotplug_handler API Gu Zheng
2014-09-03 9:06 ` [Qemu-devel] [PATCH 1/5] acpi/cpu: add cpu hotplug callback function to match " Gu Zheng
2014-09-10 13:28 ` Igor Mammedov
2014-09-11 3:04 ` Gu Zheng
2014-09-11 10:12 ` Igor Mammedov
2014-09-12 1:39 ` Gu Zheng
2014-09-03 9:06 ` [Qemu-devel] [PATCH 2/5] acpi:ich9: convert cpu hotplug handle to " Gu Zheng
2014-09-03 9:06 ` [Qemu-devel] [PATCH 3/5] acpi:piix4: " Gu Zheng
2014-09-03 9:06 ` [Qemu-devel] [PATCH 4/5] pc: add cpu hotplug handler to PC_MACHINE Gu Zheng
2014-09-10 13:55 ` Igor Mammedov
2014-09-12 3:02 ` Gu Zheng
2014-09-12 14:28 ` Igor Mammedov
2014-09-15 3:57 ` Gu Zheng
2014-09-15 8:11 ` Igor Mammedov
2014-09-10 14:02 ` Igor Mammedov
2014-09-03 9:06 ` [Qemu-devel] [PATCH 5/5] cpu/hotplug: remove the left unused cpu hotplug notifier function Gu Zheng
2014-09-10 13:59 ` Igor Mammedov
2014-09-10 14:12 ` [Qemu-devel] [PATCH 0/5] cpu/acpi: convert cpu hot plug to hotplug_handler API Igor Mammedov
2014-09-11 2:53 ` Gu Zheng [this message]
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=54110EC5.5030603@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=afaerber@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jjherne@us.ibm.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).