Re: [PATCH qemu v12] spapr: Implement Open Firmware client interface

2020-12-21 Thread Greg Kurz
On Mon, 21 Dec 2020 23:06:40 +1100 Alexey Kardashevskiy wrote: [...] > > Thanks for the split. The VOF paths are now clearly identified in > > the sPAPR code, and well guarded by a check on x-vof. Rest of the > > patch looks good to me. I gave it a try with a stock fedora 33 > > kernel and initr

Re: [PATCH qemu v12] spapr: Implement Open Firmware client interface

2020-12-21 Thread Alexey Kardashevskiy
On 19/12/2020 01:04, Greg Kurz wrote: On Fri, 18 Dec 2020 13:50:40 +1100 Alexey Kardashevskiy wrote: The PAPR platform which describes an OS environment that's presented by a combination of a hypervisor and firmware. The features it specifies require collaboration between the firmware and t

Re: [PATCH qemu v12] spapr: Implement Open Firmware client interface

2020-12-18 Thread Greg Kurz
On Fri, 18 Dec 2020 13:50:40 +1100 Alexey Kardashevskiy wrote: > The PAPR platform which describes an OS environment that's presented by > a combination of a hypervisor and firmware. The features it specifies > require collaboration between the firmware and the hypervisor. > > Since the beginnin

Re: [PATCH qemu v12] spapr: Implement Open Firmware client interface

2020-12-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20201218025040.98132-1-...@ozlabs.ru/ Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20201218025040.98132-1-...@ozlabs.ru Subject: [PATCH qemu v12] spapr: Implement Open Firmware

[PATCH qemu v12] spapr: Implement Open Firmware client interface

2020-12-17 Thread Alexey Kardashevskiy
The PAPR platform which describes an OS environment that's presented by a combination of a hypervisor and firmware. The features it specifies require collaboration between the firmware and the hypervisor. Since the beginning, the runtime component of the firmware (RTAS) has been implemented as a 2