From: Igor Mammedov <imammedo@redhat.com>
To: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Cc: ehabkost@redhat.com, qemu-devel@nongnu.org,
izumi.taku@jp.fujitsu.com, chen.fan.fnst@cn.fujitsu.com,
pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v12 3/5] x86: use new method to correct reset sequence
Date: Tue, 22 Sep 2015 14:29:19 +0200 [thread overview]
Message-ID: <20150922142919.3db1f463@nial.brq.redhat.com> (raw)
In-Reply-To: <9e346b5686cef7b084a2563eae9d8143126b3b33.1442380656.git.zhugh.fnst@cn.fujitsu.com>
On Wed, 16 Sep 2015 17:19:13 +0800
Zhu Guihua <zhugh.fnst@cn.fujitsu.com> wrote:
> During reset some devices (such as hpet, rtc) might send IRQ to APIC
> which changes APIC's state from default one it's supposed to have
> at machine startup time.
> Fix this by resetting APIC after devices have been reset to cancel
> any changes that qemu_devices_reset() might have done to its state.
>
> Signed-off-by: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> hw/i386/pc.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 631f89f..b414055 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -1924,6 +1924,25 @@ static void pc_machine_initfn(Object *obj)
> NULL, &error_abort);
> }
>
> +static void pc_machine_reset(void)
> +{
> + CPUState *cs;
> + X86CPU *cpu;
> +
> + qemu_devices_reset();
> +
> + /* Reset APIC after devices have been reset to cancel
> + * any changes that qemu_devices_reset() might have done.
> + */
> + CPU_FOREACH(cs) {
> + cpu = X86_CPU(cs);
> +
> + if (cpu->apic_state) {
> + device_reset(cpu->apic_state);
> + }
> + }
> +}
> +
> static unsigned pc_cpu_index_to_socket_id(unsigned cpu_index)
> {
> unsigned pkg_id, core_id, smt_id;
> @@ -1944,6 +1963,7 @@ static void pc_machine_class_init(ObjectClass *oc, void *data)
> mc->default_boot_order = "cad";
> mc->hot_add_cpu = pc_hot_add_cpu;
> mc->max_cpus = 255;
> + mc->reset = pc_machine_reset;
> hc->plug = pc_machine_device_plug_cb;
> hc->unplug_request = pc_machine_device_unplug_request_cb;
> hc->unplug = pc_machine_device_unplug_cb;
next prev parent reply other threads:[~2015-09-22 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:19 [Qemu-devel] [PATCH v12 0/5] remove icc bus/bridge Zhu Guihua
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 1/5] apic: move APIC's MMIO region mapping into APIC Zhu Guihua
2015-09-22 12:28 ` Igor Mammedov
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 2/5] apic: use per CPU AS to map APIC MMIO for TCG Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov
2015-10-02 18:24 ` Eduardo Habkost
2015-10-02 19:21 ` Eduardo Habkost
2015-10-09 9:00 ` Zhu Guihua
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 3/5] x86: use new method to correct reset sequence Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov [this message]
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 4/5] cpu/apic: drop icc bus/bridge Zhu Guihua
2015-09-22 12:29 ` Igor Mammedov
2015-09-16 9:19 ` [Qemu-devel] [PATCH v12 5/5] icc_bus: drop the unused files Zhu Guihua
2015-09-22 12:30 ` Igor Mammedov
2015-09-30 6:35 ` [Qemu-devel] [PATCH v12 0/5] remove icc bus/bridge Zhu Guihua
2015-10-02 17:58 ` Eduardo Habkost
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=20150922142919.3db1f463@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=ehabkost@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).