qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/arm/bcm283x: Fix crash with device_add bcm2837 on unsupported machines
Date: Thu, 12 Jul 2018 17:25:20 +0200	[thread overview]
Message-ID: <6cc1c007-4bdf-2b8c-b0b0-d32979a56ecd@redhat.com> (raw)
In-Reply-To: <87y3egmzem.fsf@dusky.pond.sub.org>

On 12.07.2018 14:06, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
>> On 11 July 2018 at 17:12, Eduardo Habkost <ehabkost@redhat.com> wrote:
>>> On Wed, Jul 11, 2018 at 09:21:48AM +0200, Thomas Huth wrote:
>>>> Hm, ok, so how to continue here now? Shall we at least mark the
>>>> bcm2836/7 devices with user_creatable=false, so that users can not crash
>>>> their QEMU so easily with device_add? The problem with introspection via
>>>> device-list-properties would still continue to exist, but I think that's
>>>> less likely used in practice... otherwise we could still move the
>>>> qdev_set_parent_bus() calls to the realize() function instead, and just
>>>> add a big fat FIXME comment in front of the code block, so that we
>>>> remember to clean that up one day...
>>>
>>> Crashing device-list-properties should be a blocker bug, IMO.
> 
> Seconded.

Well, maybe I should then not suggest to add a hmp("info qtree") below
the hmp("info qom-tree") in test_one_device() of
tests/device-introspect-test.c ... otherwise we'll be quite busy in the
next weeks...

 Thomas

  parent reply	other threads:[~2018-07-12 15:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 21:03 [Qemu-devel] [PATCH] hw/arm/bcm283x: Fix crash with device_add bcm2837 on unsupported machines Thomas Huth
2018-07-09 21:31 ` Eduardo Habkost
2018-07-09 21:36   ` Thomas Huth
2018-07-09 21:42 ` Peter Maydell
2018-07-09 22:03   ` Thomas Huth
2018-07-10  6:50     ` Peter Maydell
2018-07-11  7:21       ` Thomas Huth
2018-07-11 16:12         ` Eduardo Habkost
2018-07-11 17:15           ` Peter Maydell
2018-07-12 12:06             ` Markus Armbruster
2018-07-12 12:55               ` Peter Maydell
2018-07-12 13:19                 ` Markus Armbruster
2018-07-12 15:25               ` Thomas Huth [this message]
2018-07-12 16:16                 ` Markus Armbruster
2018-07-12 16:22                   ` Peter Maydell
2018-07-12 16:32                     ` Thomas Huth
2018-07-16  6:41                       ` Markus Armbruster
2018-07-11 17:21       ` Paolo Bonzini
2018-07-11 19:04         ` Thomas Huth
2018-07-11 19:59           ` Eduardo Habkost
2018-07-12  8:04             ` Paolo Bonzini
2018-07-12 12:04     ` Markus Armbruster
2018-07-11 17:20 ` Paolo Bonzini
2018-07-11 18:30   ` Eduardo Habkost
2018-07-11 20:16     ` Paolo Bonzini
2018-07-11 20:23       ` Eduardo Habkost
2018-07-12  8:05         ` Paolo Bonzini
2018-07-12 18:04           ` Eduardo Habkost
2018-07-16  6:43             ` Markus Armbruster
2018-07-16 14:25               ` Eduardo Habkost
2018-07-11 18:43   ` Thomas Huth
2018-07-11 20:15     ` Paolo Bonzini
2018-07-12  5:57       ` Thomas Huth

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=6cc1c007-4bdf-2b8c-b0b0-d32979a56ecd@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).