From: Greg Kurz <groug@kaod.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] xive: Make some device types not user creatable
Date: Fri, 4 Oct 2019 12:00:07 +0200 [thread overview]
Message-ID: <20191004120007.24d70d6f@bahia.lan> (raw)
In-Reply-To: <e4c1619d-b982-e4ab-eeb9-31baddd885ba@redhat.com>
On Fri, 4 Oct 2019 11:17:30 +0200
Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> Hi Greg,
>
> On 10/4/19 9:38 AM, Greg Kurz wrote:
> > Some device types of the XIVE model are exposed to the QEMU command
> > line:
> >
> > $ ppc64-softmmu/qemu-system-ppc64 -device help | grep xive
> > name "xive-end-source", desc "XIVE END Source"
> > name "xive-source", desc "XIVE Interrupt Source"
> > name "xive-tctx", desc "XIVE Interrupt Thread Context"
> >
> > These are internal devices that shouldn't be instantiable by the
> > user. By the way, they can't be because their respective realize
> > functions expect link properties that can't be set from the command
> > line:
> >
> > qemu-system-ppc64: -device xive-source: required link 'xive' not found:
> > Property '.xive' not found
> > qemu-system-ppc64: -device xive-end-source: required link 'xive' not found:
> > Property '.xive' not found
> > qemu-system-ppc64: -device xive-tctx: required link 'cpu' not found:
> > Property '.cpu' not found
>
> Why do you have to test that manually, isn't it what
> tests/device-introspect-test.c::test_one_device does?
>
Heh probably because I wasn't aware of it :)
And BTW, test_one_device() can't help here since it only cares
about 'device_add foo,help' not crashing QEMU:
help = qtest_hmp(qts, "device_add \"%s,help\"", type);
as explained in a comment at the beginning of the file.
/*
* Covers QMP device-list-properties and HMP device_add help. We
* currently don't check that their output makes sense, only that QEMU
* survives. Useful since we've had an astounding number of crash
* bugs around here.
*/
> > Hide them by setting dc->user_creatable to false in their respective
> > class init functions.
> >
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > hw/intc/xive.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/hw/intc/xive.c b/hw/intc/xive.c
> > index 29df06df1136..6c54a35fd4bb 100644
> > --- a/hw/intc/xive.c
> > +++ b/hw/intc/xive.c
> > @@ -670,6 +670,7 @@ static void xive_tctx_class_init(ObjectClass *klass, void *data)
> > dc->realize = xive_tctx_realize;
> > dc->unrealize = xive_tctx_unrealize;
> > dc->vmsd = &vmstate_xive_tctx;
> > + dc->user_creatable = false;
> > }
> >
> > static const TypeInfo xive_tctx_info = {
> > @@ -1118,6 +1119,7 @@ static void xive_source_class_init(ObjectClass *klass, void *data)
> > dc->props = xive_source_properties;
> > dc->realize = xive_source_realize;
> > dc->vmsd = &vmstate_xive_source;
> > + dc->user_creatable = false;
> > }
> >
> > static const TypeInfo xive_source_info = {
> > @@ -1853,6 +1855,7 @@ static void xive_end_source_class_init(ObjectClass *klass, void *data)
> > dc->desc = "XIVE END Source";
> > dc->props = xive_end_source_properties;
> > dc->realize = xive_end_source_realize;
> > + dc->user_creatable = false;
> > }
> >
> > static const TypeInfo xive_end_source_info = {
> >
> >
next prev parent reply other threads:[~2019-10-04 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 7:38 [PATCH] xive: Make some device types not user creatable Greg Kurz
2019-10-04 8:27 ` Cédric Le Goater
2019-10-04 9:17 ` Philippe Mathieu-Daudé
2019-10-04 10:00 ` Greg Kurz [this message]
2019-10-05 10:21 ` David Gibson
2019-10-07 9:02 ` 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=20191004120007.24d70d6f@bahia.lan \
--to=groug@kaod.org \
--cc=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=philmd@redhat.com \
--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).