From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH] hw/s390x: Add the possibility to specify the netboot image on the command line
Date: Mon, 5 Mar 2018 11:21:56 +0100 [thread overview]
Message-ID: <20180305112156.2df08098.cohuck@redhat.com> (raw)
In-Reply-To: <7f36d2d3-df76-9627-8976-ff06a6729ef1@redhat.com>
On Wed, 28 Feb 2018 13:24:35 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 28.02.2018 12:02, David Hildenbrand wrote:
> > On 27.02.2018 12:32, Thomas Huth wrote:
> >> The file name of the netboot binary is currently hard-coded to
> >> "s390-netboot.img", without a possibility for the user to select
> >> an alternative firmware image here. That's unfortunate, especially
> >> since the basics are already there: The filename is a property of
> >> the s390-ipl device. So we just have to add a check whether the user
> >> already provided the property and only set the default if the string
> >> is still empty. Now it is possible to select a different firmware
> >> image with "-global s390-ipl.netboot_fw=/path/to/s390-netboot.img".
> >>
> >> Signed-off-by: Thomas Huth <thuth@redhat.com>
> >> ---
> >> hw/s390x/s390-virtio-ccw.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> >> index 4abbe89..7b3fb5f 100644
> >> --- a/hw/s390x/s390-virtio-ccw.c
> >> +++ b/hw/s390x/s390-virtio-ccw.c
> >> @@ -254,8 +254,10 @@ static void s390_init_ipl_dev(const char *kernel_filename,
> >> }
> >> qdev_prop_set_string(dev, "cmdline", kernel_cmdline);
> >> qdev_prop_set_string(dev, "firmware", firmware);
> >> - qdev_prop_set_string(dev, "netboot_fw", netboot_fw);
> >> qdev_prop_set_bit(dev, "enforce_bios", enforce_bios);
> >> + if (!strlen(object_property_get_str(new, "netboot_fw", &error_abort))) {
> >
> > Isn't it the case that object_property_get_str() can return also NULL?
> >
> > (looking at s390_ipl_set_loadparm())
>
> It can return NULL in case of errors (e.g. the property is not a string
> or not available at all). In this case, we know that the property is a
> string and that it is available, so IMHO no need to check for NULL here.
>
> Not sure why s390_ipl_set_loadparm() explicitely checks for this ...
> maybe this was originally required to support the old s390-virtio
> (non-ccw) machine, too?
Probably, IIRC the loadparm patches are quite old. Potential cleanup?
next prev parent reply other threads:[~2018-03-05 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 11:32 [Qemu-devel] [PATCH] hw/s390x: Add the possibility to specify the netboot image on the command line Thomas Huth
2018-02-27 13:27 ` Viktor Mihajlovski
2018-02-27 19:04 ` Thomas Huth
2018-02-28 11:02 ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-02-28 12:24 ` Thomas Huth
2018-03-05 10:21 ` Cornelia Huck [this message]
2018-03-05 10:23 ` [Qemu-devel] " Cornelia Huck
2018-03-05 11:19 ` Christian Borntraeger
2018-03-06 9:24 ` Cornelia Huck
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=20180305112156.2df08098.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).