From: Igor Mammedov <imammedo@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] pc: don't access fw cfg if NULL
Date: Thu, 11 Jul 2013 14:18:16 +0200 [thread overview]
Message-ID: <20130711141816.0152e4bc@nial.usersys.redhat.com> (raw)
In-Reply-To: <20130711115240.GA24956@redhat.com>
On Thu, 11 Jul 2013 14:52:40 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> commit f8c457b88d72a48989f190bc3d7b79f4f3b7d11c
> "pc: pass PCI hole ranges to Guests"
> broke Xen as it has no fw_cfg.
> Check for this configuration and boil out.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Tested-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> ---
>
> Anthony, could you fast-track this into master please?
> Thanks!
>
> hw/i386/pc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 9f9207d..c7fc475 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -999,7 +999,7 @@ typedef struct PcRomPciInfo {
> static void pc_fw_cfg_guest_info(PcGuestInfo *guest_info)
> {
> PcRomPciInfo *info;
> - if (!guest_info->has_pci_info) {
> + if (!guest_info->has_pci_info || !guest_info->fw_cfg) {
> return;
> }
>
Reviewed-By: Igor Mammedov <imammedo@redhat.com>
prev parent reply other threads:[~2013-07-11 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 11:52 [Qemu-devel] [PATCH] pc: don't access fw cfg if NULL Michael S. Tsirkin
2013-07-11 12:18 ` Igor Mammedov [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=20130711141816.0152e4bc@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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).