Re: [Qemu-devel] [PATCH 03/15] s390-bios: decouple common boot logic from virtio

2019-02-04 Thread Cornelia Huck
On Tue, 29 Jan 2019 08:29:10 -0500 "Jason J. Herne" wrote: > Create a boot_setup function to handle getting boot information from > the machine/hypervisor. This decouples common boot logic from the > virtio code path and allows us to make use of it for the real dasd boot > scenario. > > Signed-o

Re: [Qemu-devel] [PATCH 03/15] s390-bios: decouple common boot logic from virtio

2019-01-30 Thread Farhan Ali
On 01/29/2019 08:29 AM, Jason J. Herne wrote: Create a boot_setup function to handle getting boot information from the machine/hypervisor. This decouples common boot logic from the virtio code path and allows us to make use of it for the real dasd boot scenario. Signed-off-by: Jason J. Herne

[Qemu-devel] [PATCH 03/15] s390-bios: decouple common boot logic from virtio

2019-01-29 Thread Jason J. Herne
Create a boot_setup function to handle getting boot information from the machine/hypervisor. This decouples common boot logic from the virtio code path and allows us to make use of it for the real dasd boot scenario. Signed-off-by: Jason J. Herne Acked-by: Halil Pasic Reviewed-by: Collin Walling

Re: [Qemu-devel] [PATCH 03/15] s390-bios: decouple common boot logic from virtio

2018-12-13 Thread Farhan Ali
On 12/12/2018 09:11 AM, Jason J. Herne wrote: Create a boot_setup function to handle getting boot information from the machine/hypervisor. This decouples common boot logic from the virtio code path and allows us to make use of it for the real dasd boot scenario. Signed-off-by: Jason J. Herne

[Qemu-devel] [PATCH 03/15] s390-bios: decouple common boot logic from virtio

2018-12-12 Thread Jason J. Herne
Create a boot_setup function to handle getting boot information from the machine/hypervisor. This decouples common boot logic from the virtio code path and allows us to make use of it for the real dasd boot scenario. Signed-off-by: Jason J. Herne Acked-by: Halil Pasic Reviewed-by: Collin Walling