From: Cornelia Huck <cohuck@redhat.com>
To: "Collin L. Walling" <walling@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [Qemu-devel] Interactive Boot Menu: New Fields in IPLB
Date: Fri, 8 Dec 2017 11:19:19 +0100 [thread overview]
Message-ID: <20171208111919.2d5322b9.cohuck@redhat.com> (raw)
In-Reply-To: <49485e7e-f950-58c5-af56-b336b4d4f0e3@linux.vnet.ibm.com>
On Thu, 7 Dec 2017 18:56:16 -0500
"Collin L. Walling" <walling@linux.vnet.ibm.com> wrote:
> --- The Fields We Need To Store ---
>
> Currently, we're utilizing 3 bytes out of a 77 byte reserved field in
> the IPLB for
> CCW and SCSI. We do this because need a way to pass the Qemu command
> line options
> for a boot menu (on/off and timeout) to the s390-ccw bios. We require
> only two
> fields in the IPLB, totaling 3 bytes:
Hm, are we actually that constrained with space?
>
> * uint8_t boot_menu_flag
> o determines if we should show the menu or not
Should be fine. I'd recommend something along the lines of
- bit 0: show a boot menu
- bit 1-7: reserved [for future use]
>
> * uint16_t boot_menu_timeout
> o stored as milliseconds
> o A max value of approx 65,000 gives us 65 seconds -- should be
> plenty
65 seconds should be enough for everyone?
:)
> o could potentially be reduced to one byte, and we store the value
> as seconds instead
As said, do we really need to worry about the space this is using up
here?
>
> Note: these fields *only*have value in a QEMU environment.
next prev parent reply other threads:[~2017-12-08 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 23:56 [Qemu-devel] Interactive Boot Menu: New Fields in IPLB Collin L. Walling
2017-12-08 8:26 ` Christian Borntraeger
2017-12-08 10:14 ` Cornelia Huck
2017-12-08 10:19 ` Cornelia Huck [this message]
2017-12-08 11:59 ` David Hildenbrand
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=20171208111919.2d5322b9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@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.vnet.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).