From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>,
Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>,
izumi.taku@jp.fujitsu.com, qemu-devel@nongnu.org,
pbonzini@redhat.com, guz.fnst@cn.fujitsu.com,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 3/4] cpu/apic: drop icc bus/bridge
Date: Fri, 22 May 2015 22:26:16 +0200 [thread overview]
Message-ID: <555F90E8.1090700@suse.de> (raw)
In-Reply-To: <20150522165622.GF28075@thinpad.lan.raisama.net>
Am 22.05.2015 um 18:56 schrieb Eduardo Habkost:
> On Fri, May 22, 2015 at 03:44:53PM +0800, Chen Fan wrote:
>> static void x86_cpu_apic_realize(X86CPU *cpu, Error **errp)
>> @@ -2801,8 +2793,6 @@ static void x86_cpu_realizefn(DeviceState *dev, Error
>> **errp)
>> }
>>
>> #ifndef CONFIG_USER_ONLY
>> - qemu_register_reset(x86_cpu_machine_reset_cb, cpu);
>> -
>> if (cpu->env.features[FEAT_1_EDX] & CPUID_APIC || smp_cpus > 1) {
>> x86_cpu_apic_create(cpu, &local_err);
>> if (local_err != NULL) {
>> diff --git a/vl.c b/vl.c
>> index 15bccc4..0c53053 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -1618,6 +1618,7 @@ void qemu_devices_reset(void)
>> QTAILQ_FOREACH_SAFE(re, &reset_handlers, entry, nre) {
>> re->func(re->opaque);
>> }
>> + reset_all_vcpus();
>> }
>
> What about all the other architectures and machines that may expect
> different reset ordering, and that already register their own CPU reset
> handlers?
>
> If x86 has specific CPU reset ordering requirements, we should be able
> to ensure the expected ordering in x86-specific code (in pc.c?), not
> hardcode reset ordering for all machines.
+1
In particular pseries has special ordering requirements.
> (BTW, what was the motivation to move qemu_register_reset() from pc.c to
> target-i386/cpu.c? The only architectures that register reset handlers
> inside the CPU code are x86 and s390x, all others register reset
> handlers inside machine code.)
I don't remember the motivation, it was Anthony overturning my objection
against that exception from the rule though. If we can bring x86 or the
other targets back in line, feel free to make an RFC.
I still have an old branch with initial reset support for alpha and rth
had a patch to that effect, too.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-05-22 20:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 2:40 [Qemu-devel] [PATCH v6 0/4] remove icc bus/bridge Zhu Guihua
2015-05-20 2:40 ` [Qemu-devel] [PATCH v6 1/4] apic: map APIC's MMIO region at each CPU's address space Zhu Guihua
2015-05-20 11:46 ` Igor Mammedov
2015-05-20 12:38 ` Eduardo Habkost
2015-05-20 13:50 ` Igor Mammedov
2015-05-20 14:10 ` Eduardo Habkost
2015-05-22 19:21 ` Eduardo Habkost
2015-05-20 2:40 ` [Qemu-devel] [PATCH v6 2/4] apic: convert ->busdev.qdev casts to C casts Zhu Guihua
2015-05-20 11:48 ` Igor Mammedov
2015-05-20 12:41 ` Andreas Färber
2015-05-22 19:22 ` Eduardo Habkost
2015-05-20 2:40 ` [Qemu-devel] [PATCH v6 3/4] cpu/apic: drop icc bus/bridge Zhu Guihua
2015-05-20 14:53 ` Igor Mammedov
2015-05-22 7:44 ` Chen Fan
2015-05-22 16:56 ` Eduardo Habkost
2015-05-22 20:26 ` Andreas Färber [this message]
2015-05-20 2:40 ` [Qemu-devel] [PATCH v6 4/4] icc_bus: drop the unused files Zhu Guihua
2015-05-20 14:14 ` [Qemu-devel] [PATCH v6 0/4] remove icc bus/bridge Eduardo Habkost
2015-05-20 14:54 ` Andreas Färber
2015-05-20 14:58 ` Eduardo Habkost
2015-05-20 15:00 ` Andreas Färber
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=555F90E8.1090700@suse.de \
--to=afaerber@suse.de \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).