From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Hot unplug of pci-serial-2x fails assertion
Date: Mon, 14 Jul 2014 21:48:12 +1000 [thread overview]
Message-ID: <CAEgOgz5XE_0udwDYEB6i5MHBAVy8x7g_TmdN3m6uABbdQSKWBA@mail.gmail.com> (raw)
In-Reply-To: <8738e4fb5y.fsf@blackfin.pond.sub.org>
On Mon, Jul 14, 2014 at 9:10 PM, Markus Armbruster <armbru@redhat.com> wrote:
> Watch this:
>
> (qemu) chardev-add file,path=foo2,id=foo2
> (qemu) chardev-add file,path=foo3,id=foo3
> (qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
> (qemu) device_del gg
> (qemu) upstream-qemu: /work/armbru/qemu/memory.c:1259: memory_region_finalize: Assertion `((&mr->subregions)->tqh_first == ((void *)0))' failed.
>
Are there more specifics to reproduction? I'm struggling and I've
tried a few variants.
Curiously I can device_del gg repeatedly with seemingly no effect however:
pcrost@pcrost-K42F:~/qemu$ ./x86_64-softmmu/qemu-system-x86_64 -nographic
QEMU 2.0.91 monitor - type 'help' for more information
(qemu) chardev-add file,path=foo2,id=foo2
(qemu) chardev-add file,path=foo3,id=foo3
(qemu) device_add id=gg,driver=pci-serial-2x,chardev1=foo2,chardev2=foo3
(qemu) device_del gg
(qemu) device_del gg
(qemu) device_del gg
(qemu) info qtree
bus: main-system-bus
type System
dev: hpet, id ""
gpio-in "" 2
gpio-out "" 1
timers = 3 (0x3)
msi = false
hpet-intcap = 4 (0x4)
irq 32
mmio 00000000fed00000/0000000000000400
dev: ioapic, id ""
gpio-in "" 24
irq 0
mmio 00000000fec00000/0000000000001000
dev: i440FX-pcihost, id ""
pci-hole64-size = 18446744073709551615 (16 EiB)
short_root_bus = 0 (0x0)
irq 0
bus: pci.0
type PCI
dev: pci-serial-2x, id "gg"
chardev1 = "foo2"
chardev2 = "foo3"
prog_if = 2 (0x2)
addr = 04.0
romfile = ""
rombar = 1 (0x1)
multifunction = false
command_serr_enable = true
class Serial port, addr 00:04.0, pci id 1b36:0003 (sub 1af4:1100)
bar 0: i/o at 0xffffffffffffffff [0xe]
Am I missing something?
Regards,
Peter
next prev parent reply other threads:[~2014-07-14 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 11:10 [Qemu-devel] Hot unplug of pci-serial-2x fails assertion Markus Armbruster
2014-07-14 11:44 ` Paolo Bonzini
2014-07-14 12:23 ` Markus Armbruster
2014-07-14 11:48 ` Peter Crosthwaite [this message]
2014-07-14 12:22 ` Markus Armbruster
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=CAEgOgz5XE_0udwDYEB6i5MHBAVy8x7g_TmdN3m6uABbdQSKWBA@mail.gmail.com \
--to=peter.crosthwaite@xilinx.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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 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).