From: Stefan Weil <weil@mail.berlios.de>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Fix duplicate device reset
Date: Mon, 01 Aug 2011 22:45:33 +0200 [thread overview]
Message-ID: <4E37106D.4090403@mail.berlios.de> (raw)
In-Reply-To: <20110801110028.GL31494@valinux.co.jp>
Am 01.08.2011 13:00, schrieb Isaku Yamahata:
>
> Hi, here is the patch. Can you please give it a try?
>
> From 41039df3174fa46477c4faf93d13eab360dccc22 Mon Sep 17 00:00:00 2001
> Message-Id:
> <41039df3174fa46477c4faf93d13eab360dccc22.1312196365.git.yamahata@valinux.co.jp>
> From: Isaku Yamahata <yamahata@valinux.co.jp>
> Date: Mon, 1 Aug 2011 19:56:42 +0900
> Subject: [PATCH] qdev: Fix duplicate reset
>
> qbus_reset_all_fn was registered twice, so a lot of device reset
> functions were also called twice when QEMU started.
> Which was introduced by 80376c3fc2c38fdd45354e4b0eb45031f35587ed
> This patch fixes it by making the main_sytem_bus creation not register
main_system_bus
> reset handler.
>
> Cc: Stefan Weil <weil@mail.berlios.de>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
> ---
> hw/qdev.c | 14 ++++++++++++--
> 1 files changed, 12 insertions(+), 2 deletions(-)
Thanks. I tested your patch with i386-softmmu (bios only)
and with mipsel-softmmu (debian boot / malta).
All registered reset functions were called only once,
and qbus_reset_all_fn was the last one called.
I noticed that there are two functions named piix3_reset.
One might be renamed to piix3_ide_reset, but this is
not related to your patch. There are also two functions
piix4_reset.
Tested-by: Stefan Weil <weil@mail.berlios.de>
prev parent reply other threads:[~2011-08-01 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 20:22 [Qemu-devel] [PATCH] Fix duplicate device reset Stefan Weil
2011-07-19 2:39 ` Isaku Yamahata
2011-07-19 5:56 ` Stefan Weil
2011-07-19 7:22 ` Isaku Yamahata
2011-08-01 11:00 ` Isaku Yamahata
2011-08-01 20:45 ` Stefan Weil [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=4E37106D.4090403@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).