qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org, imammedo@redhat.com, afaerber@suse.de
Cc: chen.fan.fnst@cn.fujitsu.com, anshul.makkar@profitbricks.com,
	isimatu.yasuaki@jp.fujitsu.com,
	Gu Zheng <guz.fnst@cn.fujitsu.com>,
	tangchen@cn.fujitsu.com
Subject: [Qemu-devel] [RFC V2 05/10] i386: add cpu device_del support
Date: Thu, 28 Aug 2014 11:36:37 +0800	[thread overview]
Message-ID: <1409197002-9498-6-git-send-email-guz.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1409197002-9498-1-git-send-email-guz.fnst@cn.fujitsu.com>

In order to add cpu(i386) device_del support, introduce the cpu hot
unplug hanlde(x86_cpu_unplug) which will trigger the unrealize routine,
and just register it to the cpu class unplug handle.

Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Signed-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>
---
 target-i386/cpu.c |   22 ++++++++++++++++++++++
 1 files changed, 22 insertions(+), 0 deletions(-)

diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 72a94a6..dc5153e 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -2993,6 +2993,27 @@ static Property x86_cpu_properties[] = {
     DEFINE_PROP_END_OF_LIST()
 };
 
+static int x86_cpu_unplug(DeviceState *dev)
+{
+    CPUState *cpu = CPU(dev);
+    X86CPUClass *xcc;
+    Error *err = NULL;
+
+    if (cpu == first_cpu) {
+        error_report("Can not remove the first cpu!\n");
+        return -1;
+    }
+
+    xcc = X86_CPU_GET_CLASS(DEVICE(cpu));
+    xcc->parent_unrealize(DEVICE(cpu), &err);
+    if (err != NULL) {
+        error_report("%s", error_get_pretty(err));
+        error_free(err);
+        return -1;
+    }
+    return 0;
+}
+
 static void x86_cpu_common_class_init(ObjectClass *oc, void *data)
 {
     X86CPUClass *xcc = X86_CPU_CLASS(oc);
@@ -3005,6 +3026,7 @@ static void x86_cpu_common_class_init(ObjectClass *oc, void *data)
     dc->unrealize = x86_cpu_unrealizefn;
     dc->bus_type = TYPE_ICC_BUS;
     dc->props = x86_cpu_properties;
+    dc->unplug = x86_cpu_unplug;
 
     xcc->parent_reset = cc->reset;
     cc->reset = x86_cpu_reset;
-- 
1.7.7

  parent reply	other threads:[~2014-08-28  3:58 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  3:36 [Qemu-devel] [RFC V2 00/10] cpu: add device_add foo-x86_64-cpu and i386 cpu hot remove support Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 01/10] cpu: introduce CpuTopoInfo structure for argument simplification Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 02/10] qom/cpu: move register_vmstate to common CPUClass.realizefn Gu Zheng
2014-09-09 12:17   ` Igor Mammedov
2014-09-10  2:38     ` Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 03/10] cpu: add device_add foo-x86_64-cpu support Gu Zheng
2014-09-09 12:44   ` Igor Mammedov
2014-09-10  3:37     ` Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 04/10] x86: add x86_cpu_unrealizefn() for cpu apic remove Gu Zheng
2014-09-09 13:58   ` Igor Mammedov
2014-09-11  3:06     ` Gu Zheng
2014-08-28  3:36 ` Gu Zheng [this message]
2014-09-09 14:11   ` [Qemu-devel] [RFC V2 05/10] i386: add cpu device_del support Igor Mammedov
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 06/10] qom cpu: rename variable 'cpu_added_notifier' to 'cpu_hotplug_notifier' Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 07/10] qom cpu: add UNPLUG cpu notify support Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 08/10] i386: implement pc interface cpu_common_unrealizefn() in qom/cpu.c Gu Zheng
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 09/10] cpu hotplug: implement function cpu_status_write() for vcpu ejection Gu Zheng
2014-09-09 14:28   ` Igor Mammedov
2014-08-28  3:36 ` [Qemu-devel] [RFC V2 10/10] cpus: reclaim allocated vCPU objects Gu Zheng
2014-09-09 14:40   ` Igor Mammedov
2014-09-10  3:54     ` Gu Zheng
2014-09-11  9:35   ` Bharata B Rao
2014-09-11  9:49     ` Gu Zheng
2014-09-11  9:53     ` Gu Zheng
2014-09-11 12:37       ` Bharata B Rao
2014-09-12  1:24         ` Gu Zheng
2014-09-12  8:09           ` Bharata B Rao
2014-09-12  9:53             ` Gu Zheng
2014-09-12 10:30               ` Bharata B Rao
2014-09-12 10:53               ` Anshul Makkar
2014-09-12 13:52                 ` Bharata B Rao
2014-09-12 15:34                   ` Anshul Makkar
2014-09-15  6:39                   ` Gu Zheng
2014-09-15 10:09                     ` Bharata B Rao
2014-09-15 10:33                       ` Anshul Makkar
2014-09-15 13:53                         ` Bharata B Rao
2014-09-15 14:29                           ` Anshul Makkar
2014-09-11 10:03     ` Anshul Makkar
2014-09-12 14:15   ` Igor Mammedov
2014-09-15  5:03     ` Gu Zheng
2014-12-08  9:16   ` Bharata B Rao
2014-12-08  9:26     ` Peter Maydell
2014-12-08 10:28       ` Gu Zheng
2014-12-08 10:50         ` Peter Maydell
2014-12-08 15:38           ` Igor Mammedov
2014-12-08 16:38             ` Peter Maydell
2014-12-09  0:58               ` Gu Zheng
2014-12-08 10:12     ` Gu Zheng
2014-11-12  1:46 ` [Qemu-devel] [RFC V2 00/10] cpu: add device_add foo-x86_64-cpu and i386 cpu hot remove support Gu Zheng
2014-11-12  1:46 ` Gu Zheng
2014-11-12  7:57   ` 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=1409197002-9498-6-git-send-email-guz.fnst@cn.fujitsu.com \
    --to=guz.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=anshul.makkar@profitbricks.com \
    --cc=chen.fan.fnst@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.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).