qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <gcosta@redhat.com>
To: kvm-devel@lists.sourceforge.net
Cc: marcelo@kvack.org, glommer@gmail.com, qemu-devel@nongnu.org,
	Glauber Costa <gcosta@redhat.com>,
	chrisw@sous-sol.org
Subject: [Qemu-devel] [PATCH 12/15] isolate cpu thread creation in qemu-kvm.c
Date: Tue, 26 Feb 2008 16:56:42 -0300	[thread overview]
Message-ID: <1204055805-32349-13-git-send-email-gcosta@redhat.com> (raw)
In-Reply-To: <1204055805-32349-12-git-send-email-gcosta@redhat.com>

Signed-off-by: Glauber Costa <gcosta@redhat.com>
---
 qemu/qemu-kvm.c |    9 +++++++--
 qemu/qemu-kvm.h |    1 +
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
index ffc59d5..59fe9df 100644
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -351,6 +351,11 @@ static void kvm_add_signal(struct qemu_k
     sigdelset(&sigtab->negsigset, signum);
 }
 
+void kvm_init_new_ap(int cpu, CPUState *env)
+{
+    pthread_create(&vcpu_info[cpu].thread, NULL, ap_main_loop, env);
+}
+
 int kvm_init_ap(void)
 {
     CPUState *env = first_cpu->next_cpu;
@@ -371,8 +376,8 @@ #endif
     vcpu->env = first_cpu;
     signal(SIG_IPI, sig_ipi_handler);
     for (i = 1; i < smp_cpus; ++i) {
-	pthread_create(&vcpu_info[i].thread, NULL, ap_main_loop, env);
-	env = env->next_cpu;
+        kvm_init_new_ap(i, env);
+        env = env->next_cpu;
     }
     return 0;
 }
diff --git a/qemu/qemu-kvm.h b/qemu/qemu-kvm.h
index a637d71..8e45f30 100644
--- a/qemu/qemu-kvm.h
+++ b/qemu/qemu-kvm.h
@@ -13,6 +13,7 @@ #include "cpu.h"
 int kvm_main_loop(void);
 int kvm_qemu_init(void);
 int kvm_qemu_create_context(void);
+void kvm_init_new_ap(int cpu, CPUState *env);
 int kvm_init_ap(void);
 void kvm_qemu_destroy(void);
 void kvm_load_registers(CPUState *env);
-- 
1.4.2

  reply	other threads:[~2008-02-26 20:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 19:56 [Qemu-devel] [PATCH 0/15] acpi processor hotplug Glauber Costa
2008-02-26 19:56 ` [Qemu-devel] [PATCH 1/15] Make a GPE register block be acessible Glauber Costa
2008-02-26 19:56   ` [Qemu-devel] [PATCH 2/15] mark extra cpus as present Glauber Costa
2008-02-26 19:56     ` [Qemu-devel] [PATCH 3/15] introduce cpu_set to qemu monitor Glauber Costa
2008-02-26 19:56       ` [Qemu-devel] [PATCH 4/15] mark processors as presents Glauber Costa
2008-02-26 19:56         ` [Qemu-devel] [PATCH 5/15] provide gpe _L0x methods Glauber Costa
2008-02-26 19:56           ` [Qemu-devel] [PATCH 6/15] provide operation region for pio to the gpes Glauber Costa
2008-02-26 19:56             ` [Qemu-devel] [PATCH 7/15] implement method _L00 for GPE0 Glauber Costa
2008-02-26 19:56               ` [Qemu-devel] [PATCH 8/15] isolate cpu initialization function in hw/pc.c Glauber Costa
2008-02-26 19:56                 ` [Qemu-devel] [PATCH 9/15] initialize hot add system Glauber Costa
2008-02-26 19:56                   ` [Qemu-devel] [PATCH 10/15] handle gpe data for pio Glauber Costa
2008-02-26 19:56                     ` [Qemu-devel] [PATCH 11/15] manipulate the gpe bits and send sci up the os Glauber Costa
2008-02-26 19:56                       ` Glauber Costa [this message]
2008-02-26 19:56                         ` [Qemu-devel] [PATCH 13/15] provide _MAT to acpi processor Glauber Costa
2008-02-26 19:56                           ` [Qemu-devel] [PATCH 14/15] start a new cpu thread Glauber Costa
2008-02-26 19:56                             ` [Qemu-devel] [PATCH 15/15] remove acpi_build_processor_ssdt Glauber Costa
2008-02-26 23:05         ` [Qemu-devel] Re: [kvm-devel] [PATCH 4/15] mark processors as presents Alexander Graf
2008-02-26 23:07           ` Alexander Graf
2008-02-27 10:55 ` [Qemu-devel] Re: [kvm-devel] [PATCH 0/15] acpi processor hotplug Avi Kivity

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=1204055805-32349-13-git-send-email-gcosta@redhat.com \
    --to=gcosta@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=glommer@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.org \
    --cc=qemu-devel@nongnu.org \
    /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).