qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-s390x@nongnu.org
Cc: Aleksandr Bezzubikov <zuban32s@gmail.com>
Subject: Re: [Qemu-devel] Crash with pcie-pci-bridge on qemu-system-s390x
Date: Thu, 2 Nov 2017 16:42:27 +0200	[thread overview]
Message-ID: <1e04415c-83d5-a6ac-f83f-d7a57b9b9868@redhat.com> (raw)
In-Reply-To: <a0750de5-d3ce-3f15-ba12-ce383ded143d@redhat.com>

On 02/11/2017 16:19, Thomas Huth wrote:
>   Hi,
> 

Hi Thomas,

> seems like there's a new way to crash QEMU with the pcie-pci-bridge
> device (using QEMU master branch of today):
>  > $ s390x-softmmu/qemu-system-s390x -nographic -S
> QEMU 2.10.50 monitor - type 'help' for more information
> (qemu) device_add pcie-pci-bridge,id=x
> Segmentation fault (core dumped)
> 

Thanks for noticing it.

> Does anybody have a clue what might be wrong here?
> 

It was tested with X86 and I think aarch64.
I am not sure how it would work with or if we
really need it for s390.

We need the device to start a PCI hierarchy by plugging
it to PCIe Root Port. If I understand correctly s390
does not use PCIe Root Ports and may not need it.

If the assumption is correct I suppose we should only
be compiled into the above archs.
If you agree, I can post a patch for this.

Thanks,
Marcel

> Backtrace looks like this:
> 
> #0  0x000055555577064b in pci_default_write_config (d=d@entry=0x0,
> addr=addr@entry=26, val_in=1, l=l@entry=1) at
> /home/thuth/devel/qemu/hw/pci/pci.c:1367
> #1  0x00005555556c885f in s390_pcihost_hot_plug (hotplug_dev=<optimized
> out>, dev=0x55555639b160, errp=0x7fffffffc5a0) at
> /home/thuth/devel/qemu/hw/s390x/s390-pci-bus.c:684
> #2  0x000055555575afeb in device_set_realized (obj=<optimized out>,
> value=<optimized out>, errp=0x7fffffffc6d8) at
> /home/thuth/devel/qemu/hw/core/qdev.c:936
> #3  0x00005555557ee48e in property_set_bool (obj=0x55555639b160,
> v=<optimized out>, name=<optimized out>, opaque=0x555556399fe0,
> errp=0x7fffffffc6d8)
>      at /home/thuth/devel/qemu/qom/object.c:1906
> #4  0x00005555557f25ff in object_property_set_qobject
> (obj=obj@entry=0x55555639b160, value=value@entry=0x55555639d170,
> name=name@entry=0x5555559a4157 "realized",
> errp=errp@entry=0x7fffffffc6d8) at
> /home/thuth/devel/qemu/qom/qom-qobject.c:27
> #5  0x00005555557f0270 in object_property_set_bool (obj=0x55555639b160,
> value=<optimized out>, name=0x5555559a4157 "realized", errp=0x7fffffffc6d8)
>      at /home/thuth/devel/qemu/qom/object.c:1171
> #6  0x000055555570b549 in qdev_device_add
> (opts=opts@entry=0x55555640cb50, errp=errp@entry=0x7fffffffc7b0) at
> /home/thuth/devel/qemu/qdev-monitor.c:632
> ...
> 
>   Thomas
> 

  reply	other threads:[~2017-11-02 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 14:19 [Qemu-devel] Crash with pcie-pci-bridge on qemu-system-s390x Thomas Huth
2017-11-02 14:42 ` Marcel Apfelbaum [this message]
2017-11-02 14:59   ` Aleksandr Bezzubikov
2017-11-07 10:34     ` Cornelia Huck

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=1e04415c-83d5-a6ac-f83f-d7a57b9b9868@redhat.com \
    --to=marcel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=zuban32s@gmail.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).