From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] hw/s390x/ipl: The s390-ipl device is not hot-pluggable
Date: Thu, 17 Aug 2017 11:16:09 +0200 [thread overview]
Message-ID: <20170817111609.4beac270.cohuck@redhat.com> (raw)
In-Reply-To: <96918c60-9133-064a-d289-d13562a5f551@redhat.com>
On Thu, 17 Aug 2017 11:05:35 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 16.08.2017 07:30, Thomas Huth wrote:
> > The s390-ipl device can not be created by the user, since it is meant only
> > to be instantiated once internally to load the ROMs and kernel. If the user
> > tries to do a "device_add s390-ipl" via the monitor later, QEMU aborts with
> > a "ROM images must be loaded at startup" error message.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > hw/s390x/ipl.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
> > index cc36003..0d06fc1 100644
> > --- a/hw/s390x/ipl.c
> > +++ b/hw/s390x/ipl.c
> > @@ -442,6 +442,8 @@ static void s390_ipl_class_init(ObjectClass *klass, void *data)
> > dc->reset = s390_ipl_reset;
> > dc->vmsd = &vmstate_ipl;
> > set_bit(DEVICE_CATEGORY_MISC, dc->categories);
> > + /* Reason: Loads the ROMs and thus can only be used one time - internally */
> > + dc->user_creatable = false;
> > }
> >
> > static const TypeInfo s390_ipl_info = {
> >
>
> Late but still
>
> Reviewed-by: David Hildenbrand <david@redhat.com>
>
Not too late for me to add the tag :)
Thanks!
prev parent reply other threads:[~2017-08-17 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 5:30 [Qemu-devel] [PATCH] hw/s390x/ipl: The s390-ipl device is not hot-pluggable Thomas Huth
2017-08-16 12:33 ` Cornelia Huck
2017-08-17 9:05 ` David Hildenbrand
2017-08-17 9:16 ` Cornelia Huck [this message]
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=20170817111609.4beac270.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@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).