qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCHv2 2/2] Don't register cpu reset handler for cpu with APIC.
Date: Wed, 10 Jun 2009 12:07:46 +0300	[thread overview]
Message-ID: <1244624866-13205-2-git-send-email-gleb@redhat.com> (raw)
In-Reply-To: <1244624866-13205-1-git-send-email-gleb@redhat.com>

APIC reset handler already resets cpu. Also register cpu_reset handler
directly to make it impossible to add additional code to main_cpu_reset()
by mistake.

Signed-off-by: Gleb Natapov <gleb@redhat.com>
---
 hw/pc.c |   10 +++-------
 1 files changed, 3 insertions(+), 7 deletions(-)

diff --git a/hw/pc.c b/hw/pc.c
index d5b4112..0cdc2a2 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -751,12 +751,6 @@ static void load_linux(target_phys_addr_t option_rom,
     generate_bootsect(option_rom, gpr, seg, 0);
 }
 
-static void main_cpu_reset(void *opaque)
-{
-    CPUState *env = opaque;
-    cpu_reset(env);
-}
-
 static const int ide_iobase[2] = { 0x1f0, 0x170 };
 static const int ide_iobase2[2] = { 0x3f6, 0x376 };
 static const int ide_irq[2] = { 14, 15 };
@@ -878,9 +872,11 @@ static void pc_init1(ram_addr_t ram_size,
         }
         if (i != 0)
             env->halted = 1;
-        qemu_register_reset(main_cpu_reset, 0, env);
         if ((env->cpuid_features & CPUID_APIC) || smp_cpus > 1) {
+            /* APIC reset callback resets cpu */
             apic_init(env);
+        } else {
+            qemu_register_reset((QEMUResetHandler*)cpu_reset, 0, env);
         }
     }
 
-- 
1.6.2.1

      reply	other threads:[~2009-06-10  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  9:07 [Qemu-devel] [PATCHv2 1/2] Apic creation should not depend on pci Gleb Natapov
2009-06-10  9:07 ` Gleb Natapov [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=1244624866-13205-2-git-send-email-gleb@redhat.com \
    --to=gleb@redhat.com \
    --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).