From: Eduardo Habkost <ehabkost@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eduardo Otubo <otubo@redhat.com>,
mst@redhat.com, qemu-trivial@nongnu.org,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, pbonzini@redhat.com,
Aurelien Jarno <aurelien@aurel32.net>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] dma/i82374: avoid double creation of i82374 device
Date: Fri, 1 Sep 2017 12:44:30 -0300 [thread overview]
Message-ID: <20170901154430.GN7570@localhost.localdomain> (raw)
In-Reply-To: <87lglyzb3p.fsf@dusky.pond.sub.org>
On Fri, Sep 01, 2017 at 05:34:34PM +0200, Markus Armbruster wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
>
> > i82374 is compiled in only on ppc and sh4, so I'm CCing the
> > maintainers for those architectures.
> >
> > On Fri, Sep 01, 2017 at 01:03:32PM +0200, Eduardo Otubo wrote:
> >> When used with the following command line:
> >>
> >> ./ppc64-softmmu/qemu-system-ppc64 -S -machine 40p,accel=tcg -device i82374
> >>
> >> QEMU with machine type 40p already creates the device i82374. If
> >> specified in the command line, it will try to create it again, hence
> >> generating the error.
> >
> > Which error?
> >
> >
> >> One way to avoid this problem is to set
> >> user_creatable=false.
> >>
> >> Signed-off-by: Eduardo Otubo <otubo@redhat.com>
> >
> > The patch does more than just avoiding double creation: it
> > prevents usage of "-device i82374" completely.
> >
> > Maybe nobody needs it to work with -device today (would the
> > device even work?) and it is OK to set user_creatable=false until
> > we fix the crash. But we need to be sure of that.
> >
> >> ---
> >> hw/dma/i82374.c | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/hw/dma/i82374.c b/hw/dma/i82374.c
> >> index 6c0f975df0..5275d822e0 100644
> >> --- a/hw/dma/i82374.c
> >> +++ b/hw/dma/i82374.c
> >> @@ -139,6 +139,7 @@ static void i82374_class_init(ObjectClass *klass, void *data)
> >> dc->realize = i82374_realize;
> >> dc->vmsd = &vmstate_i82374;
> >> dc->props = i82374_properties;
> >> + dc->user_creatable = false;
> >
> > A "Reason:" comment explaining why user_creatable=false is
> > mandatory. See the comment above user_creatable declaration in
> > qdev-core.h for reference.
> >
> > I suggest the following:
> >
> > /*
> > * Reason: i82374_realize() crashes (assertion failure inside isa_bus_dma()
> > * if the device is instantiated twice.
> > */
>
> We need to find out *why* it crashes. Once we know, we can likely write
> a better comment.
It crashes because isa_bus_dma() isn't supposed to be called
twice for the same bus.
Making isa_bus_dma()/DMA_init()/i82374_realize() return an error
instead of asserting would be even better than setting
user_creatable=false.
--
Eduardo
next prev parent reply other threads:[~2017-09-01 15:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:03 [Qemu-devel] [PATCH] dma/i82374: avoid double creation of i82374 device Eduardo Otubo
2017-09-01 14:30 ` Eduardo Habkost
2017-09-01 15:34 ` Markus Armbruster
2017-09-01 15:44 ` Eduardo Habkost [this message]
2017-09-07 8:38 ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo
2017-09-09 21:52 ` Eduardo Habkost
2017-09-02 9:15 ` [Qemu-devel] " Aurelien Jarno
2017-09-07 8:38 ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo
2017-09-07 16:05 ` [Qemu-devel] " Paolo Bonzini
2017-09-08 7:57 ` [Qemu-devel] [Qemu-trivial] " Eduardo Otubo
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 9:06 [Qemu-devel] " Eduardo Otubo
2017-09-15 10:18 ` Paolo Bonzini
2017-09-15 11:53 ` Eduardo Otubo
2017-09-15 22:21 ` Eduardo Habkost
2017-09-16 8:09 ` Paolo Bonzini
2017-09-24 21:02 ` [Qemu-devel] [[PATCH] " Michael Tokarev
2017-09-25 9:11 ` Paolo Bonzini
2017-09-25 9:26 ` Eduardo Otubo
2017-09-25 9:36 ` Paolo Bonzini
2017-09-25 10:54 ` [Qemu-devel] [PATCH] " Michael Tokarev
2017-09-25 11:25 ` Paolo Bonzini
2018-03-26 11:18 Eduardo Otubo
2018-03-26 12:14 ` Thomas Huth
2018-03-26 12:16 ` Paolo Bonzini
2018-03-26 15:20 ` Philippe Mathieu-Daudé
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=20170901154430.GN7570@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=aurelien@aurel32.net \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=otubo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@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).