From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Hu Tao <hutao@cn.fujitsu.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] pvpanic: initialization cleanup
Date: Mon, 17 Jun 2013 09:56:56 +0200 [thread overview]
Message-ID: <51BEC148.50009@redhat.com> (raw)
In-Reply-To: <1371416189-29563-1-git-send-email-mst@redhat.com>
On 06/16/13 22:59, Michael S. Tsirkin wrote:
> Avoid use of static variables: PC systems initialize pvpanic device
> through pvpanic_init, so we can simply create the fw_cfg file at that
> point. Others don't use fw_cfg at all. This also makes it possible to
> assert if fw_cfg is not there rather than skipping the device silently.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> hw/misc/pvpanic.c | 23 ++++++++++-------------
> 1 file changed, 10 insertions(+), 13 deletions(-)
>
> diff --git a/hw/misc/pvpanic.c b/hw/misc/pvpanic.c
> index 060099b..9ed9897 100644
> --- a/hw/misc/pvpanic.c
> +++ b/hw/misc/pvpanic.c
> @@ -97,25 +97,22 @@ static void pvpanic_isa_realizefn(DeviceState *dev, Error **errp)
> {
> ISADevice *d = ISA_DEVICE(dev);
> PVPanicState *s = ISA_PVPANIC_DEVICE(dev);
> - static bool port_configured;
> - FWCfgState *fw_cfg;
>
> isa_register_ioport(d, &s->io, s->ioport);
> -
> - if (!port_configured) {
> - fw_cfg = fw_cfg_find();
> - if (fw_cfg) {
> - fw_cfg_add_file(fw_cfg, "etc/pvpanic-port",
> - g_memdup(&s->ioport, sizeof(s->ioport)),
> - sizeof(s->ioport));
> - port_configured = true;
> - }
> - }
> }
>
> int pvpanic_init(ISABus *bus)
> {
> - isa_create_simple(bus, TYPE_ISA_PVPANIC_DEVICE);
> + ISADevice *dev = isa_create_simple(bus, TYPE_ISA_PVPANIC_DEVICE);
> + PVPanicState *s = ISA_PVPANIC_DEVICE(dev);
> + FWCfgState *fw_cfg = fw_cfg_find();
> +
> + assert(fw_cfg);
Won't the assert fire if:
xen_enabled() &&
machine != "pc-0.10" && machine != "pc-0.11" &&
machine != "pc-0.12" && machine != "pc-0.13" &&
machine != "pc-q35-1.4"
Because under the above condition "has_pvpanic" remains "true", but
fw_cfg is not initialized.
(pc_init_pci_no_kvmclock() in "hw/i386/pc_piix.c" sets "has_pvpanic" to
"false", and claims to be "reused by xenfv", so the above condition may
be constant false.)
> +
> + fw_cfg_add_file(fw_cfg, "etc/pvpanic-port",
> + g_memdup(&s->ioport, sizeof(s->ioport)),
> + sizeof(s->ioport));
> +
> return 0;
> }
>
>
Series looks good to me otherwise.
Thanks
Laszlo
next prev parent reply other threads:[~2013-06-17 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 20:59 [Qemu-devel] [PATCH 1/2] pvpanic: initialization cleanup Michael S. Tsirkin
2013-06-16 20:59 ` [Qemu-devel] [PATCH 2/2] pvpanic: fix fwcfg for big endian hosts Michael S. Tsirkin
2013-06-17 7:56 ` Laszlo Ersek [this message]
2013-06-17 9:19 ` [Qemu-devel] [PATCH 1/2] pvpanic: initialization cleanup Michael S. Tsirkin
2013-06-17 9:35 ` Laszlo Ersek
2013-06-17 9:57 ` Michael S. Tsirkin
2013-06-17 10:07 ` Laszlo Ersek
2013-06-19 13:39 ` Stefano Stabellini
2013-06-19 13:58 ` Laszlo Ersek
2013-06-19 13:30 ` Stefano Stabellini
2013-06-19 13:29 ` Stefano Stabellini
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=51BEC148.50009@redhat.com \
--to=lersek@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.