From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
mst@redhat.com, armbru@redhat.com,
eduardo.otubo@profitbricks.com, zhugh.fnst@cn.fujitsu.com,
eblake@redhat.com
Subject: [Qemu-devel] [PATCH 11/11] pc: cpu: allow device_add to be used with x86 cpu
Date: Thu, 23 Jun 2016 16:54:29 +0200 [thread overview]
Message-ID: <1466693669-139967-12-git-send-email-imammedo@redhat.com> (raw)
In-Reply-To: <1466693669-139967-1-git-send-email-imammedo@redhat.com>
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
---
target-i386/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 8c651f2..a67e551 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -3236,6 +3236,7 @@ static void x86_cpu_common_class_init(ObjectClass *oc, void *data)
cc->cpu_exec_enter = x86_cpu_exec_enter;
cc->cpu_exec_exit = x86_cpu_exec_exit;
+ dc->cannot_instantiate_with_device_add_yet = false;
/*
* Reason: x86_cpu_initfn() calls cpu_exec_init(), which saves the
* object in cpus -> dangling pointer after final object_unref().
--
1.8.3.1
prev parent reply other threads:[~2016-06-23 14:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 14:54 [Qemu-devel] [PATCH 00/11] pc: allow to use -device/device_add for CPUs Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 01/11] target-i386: cpu: use uint32_t for X86CPU.apic_id Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 02/11] pc: add x86_topo_ids_from_apicid() Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 03/11] pc: extract CPU lookup into a separate function Igor Mammedov
2016-06-23 17:32 ` Eduardo Habkost
2016-06-23 17:41 ` Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 04/11] pc: cpu: consolidate apic-id validity checks in pc_cpu_pre_plug() Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 05/11] target-i386: cpu: replace custom apic-id setter/getter with static property Igor Mammedov
2016-06-27 17:55 ` Eduardo Habkost
2016-06-28 6:43 ` Igor Mammedov
2016-06-28 13:35 ` Eduardo Habkost
2016-06-23 14:54 ` [Qemu-devel] [PATCH 06/11] target-i386: add socket/core/thread properties to X86CPU Igor Mammedov
2016-06-23 17:44 ` Eduardo Habkost
2016-06-23 19:18 ` Igor Mammedov
2016-06-23 20:18 ` Eduardo Habkost
2016-06-23 20:46 ` Igor Mammedov
2016-06-23 21:43 ` Eduardo Habkost
2016-06-24 5:23 ` Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 07/11] pc: set APIC ID based on socket/core/thread ids if it's not been set yet Igor Mammedov
2016-06-23 17:19 ` Eduardo Habkost
2016-06-23 17:48 ` Igor Mammedov
2016-06-23 19:27 ` Eduardo Habkost
2016-06-23 20:50 ` Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 08/11] pc: implement query-hotpluggable-cpus callback Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 09/11] pc: register created initial and hotpluged CPUs in one place pc_cpu_plug() Igor Mammedov
2016-06-23 14:54 ` [Qemu-devel] [PATCH 10/11] pc: delay setting number of boot CPUs to machine_done time Igor Mammedov
2016-06-23 14:54 ` Igor Mammedov [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=1466693669-139967-12-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).