Re: [PATCH 00/19] hw: Set QDev properties using QDev API (part 1/3)

2023-03-01 Thread Igor Mammedov
On Fri, 3 Feb 2023 19:08:55 +0100 Philippe Mathieu-Daudé wrote: > QEMU provides the QOM API for core objects. > Devices are modelled on top of QOM as QDev objects. > > There is no point in using the lower level QOM API with > QDev; it makes the code more complex and harder to review. > > I

Re: [PATCH 00/19] hw: Set QDev properties using QDev API (part 1/3)

2023-02-03 Thread BALATON Zoltan
On Fri, 3 Feb 2023, Philippe Mathieu-Daudé wrote: On 3/2/23 19:08, Philippe Mathieu-Daudé wrote: QEMU provides the QOM API for core objects. Devices are modelled on top of QOM as QDev objects. There is no point in using the lower level QOM API with QDev; it makes the code more complex and

Re: [PATCH 00/19] hw: Set QDev properties using QDev API (part 1/3)

2023-02-03 Thread Philippe Mathieu-Daudé
On 3/2/23 19:08, Philippe Mathieu-Daudé wrote: QEMU provides the QOM API for core objects. Devices are modelled on top of QOM as QDev objects. There is no point in using the lower level QOM API with QDev; it makes the code more complex and harder to review. I first converted all the calls

[PATCH 00/19] hw: Set QDev properties using QDev API (part 1/3)

2023-02-03 Thread Philippe Mathieu-Daudé
QEMU provides the QOM API for core objects. Devices are modelled on top of QOM as QDev objects. There is no point in using the lower level QOM API with QDev; it makes the code more complex and harder to review. I first converted all the calls using errp=_abort or =NULL, then noticed the other