From: David Hildenbrand <david@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org,
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: Farhan Ali <alifm@linux.ibm.com>,
Collin Walling <walling@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v4 0/3] pc-bios/s390-ccw: Some few network boot improvements
Date: Fri, 27 Apr 2018 15:14:57 +0200 [thread overview]
Message-ID: <06fd547e-6a1b-6920-fb5e-acadea0b8fd0@redhat.com> (raw)
In-Reply-To: <1524734910-17970-1-git-send-email-thuth@redhat.com>
On 26.04.2018 11:28, Thomas Huth wrote:
> Note: I've decided to removed the pxelinux.cfg patches from this series
> for now, since full pxelinux support requires to parse some additional
> DHCP options (see https://tools.ietf.org/html/rfc5071), and for this, the
> SLOF libnet code needs to be changed first. So I guess I first have to
> implement pxelinux.cfg support for PPC, too, which will likely take a
> little bit longer...
I don't think it would be wrong to include it for now. We just don't
support all options yet - that can be fixed later. If the current state
is what 99.9999% of all users will need, than include it. If it is a
crucial feature, than I agree.
> Thus to keep this series short and reviewable, and to avoid that the other
> patches bit-rot on my hard disk, I've now only included the patches that
> are not related to pxelinux.cfg.
>
> The first patch is just a minor code refactoring which should not have
> any visible impact, but makes the following patches easier.
>
> The second patch makes sure that we leave the machine in a sane state
> before jumping into the Linux kernel - i.e. the netboot firmware now
> resets the machine with diag308, too, just like the main s390-ccw
> is doing it already.
>
> Patch 3 adds support for loading kernels via .INS configuration files.
> You can find these .INS config files on ISO images, so with this patch,
> it should be possible to boot if the TFTP server is configured to use
> the contents of such an ISO image.
>
> v4:
> - s/uninit/release/ in the title of the first patch
> - Set schid of the network device in 184
> - Jump to 0x10000 start address if S390EP magic is available
>
> Thomas Huth (3):
> pc-bios/s390-ccw/net: Split up net_load() into init, load and release
> parts
> pc-bios/s390-ccw/net: Use diag308 to reset machine before jumping to
> the OS
> pc-bios/s390-ccw/net: Add support for .INS config files
>
> pc-bios/s390-ccw/Makefile | 4 +-
> pc-bios/s390-ccw/bootmap.c | 63 +---------------
> pc-bios/s390-ccw/bootmap.h | 4 --
> pc-bios/s390-ccw/jump2ipl.c | 91 +++++++++++++++++++++++
> pc-bios/s390-ccw/netboot.mak | 3 +-
> pc-bios/s390-ccw/netmain.c | 168 +++++++++++++++++++++++++++++++++++--------
> pc-bios/s390-ccw/s390-ccw.h | 4 ++
> 7 files changed, 240 insertions(+), 97 deletions(-)
> create mode 100644 pc-bios/s390-ccw/jump2ipl.c
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2018-04-27 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 9:28 [Qemu-devel] [PATCH v4 0/3] pc-bios/s390-ccw: Some few network boot improvements Thomas Huth
2018-04-26 9:28 ` [Qemu-devel] [PATCH v4 1/3] pc-bios/s390-ccw/net: Split up net_load() into init, load and release parts Thomas Huth
2018-04-26 9:28 ` [Qemu-devel] [PATCH v4 2/3] pc-bios/s390-ccw/net: Use diag308 to reset machine before jumping to the OS Thomas Huth
2018-04-26 9:28 ` [Qemu-devel] [PATCH v4 3/3] pc-bios/s390-ccw/net: Add support for .INS config files Thomas Huth
2018-04-27 13:14 ` David Hildenbrand [this message]
2018-05-02 8:23 ` [Qemu-devel] [qemu-s390x] [PATCH v4 0/3] pc-bios/s390-ccw: Some few network boot improvements Christian Borntraeger
2018-05-02 8:22 ` Christian Borntraeger
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=06fd547e-6a1b-6920-fb5e-acadea0b8fd0@redhat.com \
--to=david@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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).