Re: [Qemu-devel] Interactive Boot Menu: New Fields in IPLB

2017-12-08 Thread David Hildenbrand
On 08.12.2017 00:56, Collin L. Walling 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

Re: [Qemu-devel] Interactive Boot Menu: New Fields in IPLB

2017-12-08 Thread Cornelia Huck
On Thu, 7 Dec 2017 18:56:16 -0500 "Collin L. Walling" 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 opti

Re: [Qemu-devel] Interactive Boot Menu: New Fields in IPLB

2017-12-08 Thread Cornelia Huck
On Thu, 7 Dec 2017 18:56:16 -0500 "Collin L. Walling" 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 w

Re: [Qemu-devel] Interactive Boot Menu: New Fields in IPLB

2017-12-08 Thread Christian Borntraeger
On 12/08/2017 12:56 AM, Collin L. Walling 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 obst

[Qemu-devel] Interactive Boot Menu: New Fields in IPLB

2017-12-07 Thread Collin L. Walling
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" locatio