[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu
From: |
Jan Kiszka |
Subject: |
Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset |
Date: |
Tue, 26 Apr 2011 20:55:22 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
On 2011-04-26 20:00, Blue Swirl wrote:
> On Tue, Apr 26, 2011 at 11:50 AM, Jan Kiszka <address@hidden> wrote:
>> Instead of having an extra reset function at machine level and special
>> code for processing INIT, move the initialization of halted into the
>> cpu reset handler.
>
> Nack. A CPU is designated as a BSP at board level. CPUs do not need to
> know about this at all.
That's why we have cpu_is_bsp() in pc.c.
Obviously, every CPU (which includes the APIC) must know if it is
supposed to be BP or AP. It would be unable to enter the right state
after reset otherwise (e.g. Intel SDM 9.1). cpu_is_bsp() is basically
reporting the result of the MP init protocol in condensed from.
Jan
signature.asc
Description: OpenPGP digital signature
- [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Jan Kiszka, 2011/04/26
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Blue Swirl, 2011/04/26
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset,
Jan Kiszka <=
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Blue Swirl, 2011/04/26
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Jan Kiszka, 2011/04/27
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Blue Swirl, 2011/04/27
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Jan Kiszka, 2011/04/27
- Re: [Qemu-devel] [PATCH] target-i386: Initialize CPUState::halted in cpu_reset, Blue Swirl, 2011/04/27