qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-ppc64 crashes during "info qtree"
Date: Fri, 3 Mar 2017 12:16:55 +0100	[thread overview]
Message-ID: <ee977c5e-affd-cf8d-d793-0d153fdf3e7d@kaod.org> (raw)
In-Reply-To: <5b2054e1-5867-979b-b476-b3aa8ecc5689@redhat.com>

On 03/03/2017 11:48 AM, Thomas Huth wrote:
>  Hi Cédric, hi David,
> 
> running "info qtree" at the HMP monitor with the pseries machine
> currently results in:
> 
>   [...]
>       dev: spapr-vty, id "vty@71000000"
>         reg = 1895825408 (0x71000000)
>         chardev = "serial0"
>         irq = 4098 (0x1002)
>   dev: spapr-rtc, id ""
>   dev: icp, id ""
> hw/core/sysbus.c:277:sysbus_dev_print: Object 0x7f83127fc3f0 is not an
> instance of type sys-bus-device
> Aborted (core dumped)
> 
> Since the last device that is printed here is "icp" ... could that be
> related to the recent ICP/XICS reworks that have been merged a couple of
> days ago?

The cleanup did not change the nature of ICP but as we removed 
the XICS object, which used to be a SysBusDevice, that might 
be a consequence. 

May be we should make the ICP objects SysBus devices now. I will 
check. 

Thanks,


C.

  reply	other threads:[~2017-03-03 11:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 10:48 [Qemu-devel] qemu-system-ppc64 crashes during "info qtree" Thomas Huth
2017-03-03 11:16 ` Cédric Le Goater [this message]
2017-03-03 12:49   ` Cédric Le Goater

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=ee977c5e-affd-cf8d-d793-0d153fdf3e7d@kaod.org \
    --to=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --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).