qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] Revert "s390x/ccw: create s390 phb conditionally"
Date: Thu, 28 Sep 2017 16:15:28 +0200	[thread overview]
Message-ID: <20170928161528.31a623a5.cohuck@redhat.com> (raw)
In-Reply-To: <20170928131831.81393-1-borntraeger@de.ibm.com>

On Thu, 28 Sep 2017 15:18:31 +0200
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> This reverts commit d32bd032d8fde41281aae34c16a4aa97e9acfeac.
> 
> Turns out that old QEMUs always created a pci host bridge
> and for many CPU models the migration from old QEMUs to new
> QEMUs will fail with
> qemu-system-s390x: Unknown savevm section or instance 'PCIBUS' 0
> qemu-system-s390x: load of migration failed: Invalid argument
> 
> As a quick fix we will revert the commit and always create the
> pci host bridge.
> 
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> [fixed revert to keep the comment fixup, added a comment in the code]
> Cc: Cornelia Huck <cohuck@redhat.com>
> Cc: David Hildenbrand <david@redhat.com>
> ---
>  hw/s390x/s390-virtio-ccw.c | 16 +++++++++-------
>  1 file changed, 9 insertions(+), 7 deletions(-)
> 
> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> index b6aa2da..a77336f 100644
> --- a/hw/s390x/s390-virtio-ccw.c
> +++ b/hw/s390x/s390-virtio-ccw.c
> @@ -275,6 +275,7 @@ static void ccw_init(MachineState *machine)
>  {
>      int ret;
>      VirtualCssBus *css_bus;
> +    DeviceState *dev;
>  
>      s390_sclp_init();
>      s390_memory_init(machine->ram_size);
> @@ -290,13 +291,14 @@ static void ccw_init(MachineState *machine)
>                        machine->initrd_filename, "s390-ccw.img",
>                        "s390-netboot.img", true);
>  
> -    if (s390_has_feat(S390_FEAT_ZPCI)) {
> -        DeviceState *dev = qdev_create(NULL, TYPE_S390_PCI_HOST_BRIDGE);
> -        object_property_add_child(qdev_get_machine(),
> -                                  TYPE_S390_PCI_HOST_BRIDGE,
> -                                  OBJECT(dev), NULL);
> -        qdev_init_nofail(dev);
> -    }
> +    /*
> +     * We cannot easily make the pci host bridge conditional as older QEMUs
> +     * always created it. Doing so would break migration across QEMU versions

Added the missing trailing period.

> +     */
> +    dev = qdev_create(NULL, TYPE_S390_PCI_HOST_BRIDGE);
> +    object_property_add_child(qdev_get_machine(), TYPE_S390_PCI_HOST_BRIDGE,
> +                              OBJECT(dev), NULL);
> +    qdev_init_nofail(dev);
>  
>      /* register hypercalls */
>      virtio_ccw_register_hcalls();

Thanks, applied.

      parent reply	other threads:[~2017-09-28 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 13:18 [Qemu-devel] [PATCH] Revert "s390x/ccw: create s390 phb conditionally" Christian Borntraeger
2017-09-28 13:47 ` David Hildenbrand
2017-09-28 14:15 ` Cornelia Huck [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=20170928161528.31a623a5.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.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).