From: Markus Armbruster <armbru@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Marcel Apfelbaum <marcel@redhat.com>,
Cao jin <caoj.fnst@cn.fujitsu.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Reproducible crash on PCIe hotplug
Date: Mon, 12 Dec 2016 17:48:43 +0100 [thread overview]
Message-ID: <8760mp14b8.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20161209203954.GW4027@thinpad.lan.raisama.net> (Eduardo Habkost's message of "Fri, 9 Dec 2016 18:39:54 -0200")
Eduardo Habkost <ehabkost@redhat.com> writes:
> Using latest qemu.git master:
>
> $ qemu-system-x86_64 -machine q35 -readconfig docs/q35-chipset.cfg -monitor stdio
> QEMU 2.7.93 monitor - type 'help' for more information
> (qemu) device_add e1000e,bus=ich9-pcie-port-4,addr=00
> (qemu) device_add e1000e,bus=ich9-pcie-port-4,addr=08
> Segmentation fault (core dumped)
Bisected to
commit 3f1e1478db2d67098d98f2c3acf5a4946b7fb643
Author: Cao jin <caoj.fnst@cn.fujitsu.com>
Date: Wed Oct 28 14:20:31 2015 +0800
enable multi-function hot-add
Enable PCIe device multi-function hot-add, just ensure function 0 is added
last, then driver will get the notification to scan the slot.
Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
It's in v2.5.0, probably no need to hold the release for a fix.
prev parent reply other threads:[~2016-12-12 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 20:39 [Qemu-devel] Reproducible crash on PCIe hotplug Eduardo Habkost
2016-12-12 5:34 ` Cao jin
2016-12-12 17:29 ` Stefan Hajnoczi
2016-12-12 17:32 ` Eduardo Habkost
2016-12-12 18:27 ` Stefan Hajnoczi
2016-12-12 18:41 ` Michael S. Tsirkin
2016-12-12 18:57 ` Eduardo Habkost
2016-12-12 22:09 ` Michael S. Tsirkin
2016-12-13 2:41 ` Cao jin
2016-12-13 12:02 ` Eduardo Habkost
2016-12-12 16:48 ` Markus Armbruster [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=8760mp14b8.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.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.