From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] qdev: Keep global allocation counter per bus
Date: Wed, 08 Jan 2014 14:40:13 +0100 [thread overview]
Message-ID: <52CD553D.3050207@suse.de> (raw)
In-Reply-To: <87sisyc2m3.fsf@blackfin.pond.sub.org>
Am 08.01.2014 09:13, schrieb Markus Armbruster:
> Peter Crosthwaite <peter.crosthwaite@xilinx.com> writes:
>
>> On Wed, Jan 8, 2014 at 2:59 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>> Il 07/01/2014 16:12, Markus Armbruster ha scritto:
>>>> aarch64 akita info qtree crashes
>>>> aarch64 borzoi info qtree crashes
>>>> aarch64 spitz info qtree crashes
>>>> aarch64 terrier info qtree crashes
>>>> aarch64 tosa info qtree crashes
>>>> arm akita info qtree crashes
>>>> arm borzoi info qtree crashes
>>>> arm spitz info qtree crashes
>>>> arm terrier info qtree crashes
>>>> arm tosa info qtree crashes
>>>> cris axis-dev88 info qtree crashes
>>>
>>> The crash is because of commit 7426aa7 (nand: Don't inherit from Sysbus,
>>> 2013-06-18). Should probably be reverted.
>>>
>>
>> Prefer not, under no reasonable definition is NAND a sysbus device.
>> Whats the real problem here? What is TYPE_SYS_BUS_DEVICE doing WRT to
>> qtree that TYPE_DEVICE is not?
>
> Maybe, but our definition of sysbus has never been reasonable :)
>
> Qdev, as designed by Paul Brook, assumed the parent of a qdev is always
> a qbus and vice versa. With the exception of the root, which has no
> parent, and is a sysbus, commonly the only one.
>
> A PCI qdev plugs into a PCI qbus, an USB qdev plugs into an USB qbus,
> and so forth. Any qdev that doesn't really plug into a bus was made a
> "sysbus device" by fiat. "Sysbus" is a catchall, no more. In
> particular, it's not a bus in the hardware sense.
>
> This "everything plugs into exactly one bus" assumption is of course a
> gross oversimplification, and we've been working on overcoming it for
> quite some time. It has become possible to define qdevs that aren't
> connected to a qbus. A TYPE_DEVICE isn't.
>
> That's progress. But progress isn't justification for not fixing crash
> bugs in monitor commands.
>
> Either you fix "info qtree" to cope with your change to the device
> graph, or the change needs to be reverted until somebody fixes it or it
> goes away.
Sharing a backtrace would be a start, rather than just throwing around
the word "crash" to justify reverting patches. :)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-01-08 13:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 1:41 [Qemu-devel] [PATCH v2] qdev: Keep global allocation counter per bus Alexander Graf
2013-12-21 10:42 ` Markus Armbruster
2013-12-22 13:43 ` Paolo Bonzini
2014-01-07 15:12 ` Markus Armbruster
2014-01-07 16:59 ` Paolo Bonzini
2014-01-07 17:34 ` Markus Armbruster
2014-01-08 14:04 ` Paolo Bonzini
2014-01-08 14:35 ` Markus Armbruster
2014-01-08 15:18 ` Paolo Bonzini
2014-01-08 16:52 ` Markus Armbruster
2014-01-08 3:07 ` Peter Crosthwaite
2014-01-08 4:24 ` Andreas Färber
2014-01-08 8:00 ` Markus Armbruster
2014-01-08 10:11 ` Peter Maydell
2014-01-08 8:13 ` Markus Armbruster
2014-01-08 8:26 ` Peter Crosthwaite
2014-01-08 13:40 ` Andreas Färber [this message]
2014-01-08 13:47 ` Paolo Bonzini
2014-01-10 7:50 ` Peter Crosthwaite
2014-01-10 8:48 ` Markus Armbruster
2014-02-04 9:28 ` Markus Armbruster
2014-02-05 5:19 ` Peter Crosthwaite
2014-02-05 8:45 ` Markus Armbruster
2014-01-08 11:02 ` Paolo Bonzini
2014-01-08 13:53 ` Andreas Färber
2014-01-08 14:07 ` Paolo Bonzini
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=52CD553D.3050207@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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).