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:14:09 +0100 [thread overview]
Message-ID: <20171208111409.2f75e054.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:
> Hello,
>
> I'd like to bring up a formal discussion regarding the utilization of
> reserved space
> in the IPL Parameter Blocks for s390x guests. Particularly the following:
>
> * How should we approach "claiming" bytes so that we do not obstruct
> future development?
> * What would be "the best" location to store these new fields?
As Christian said, you probably need to check with the architecture
folks whether you can get some fields reserved for your use case.
In general, having this anywhere in the reserved areas of the iplb
should probably be fine (we migrate the iplb in two mostly-opaque
blobs).
next prev parent reply other threads:[~2017-12-08 10:14 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 [this message]
2017-12-08 10:19 ` Cornelia Huck
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=20171208111409.2f75e054.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).