Re: [PATCH 34/40] lasips2: update VMStateDescription for LASIPS2 device

2022-07-05 Thread Peter Maydell
On Tue, 5 Jul 2022 at 07:48, Mark Cave-Ayland wrote: > > On 04/07/2022 14:38, Peter Maydell wrote: > > > On Wed, 29 Jun 2022 at 13:41, Mark Cave-Ayland > > wrote: > >> > >> Since this series has already introduced a migration break for the HPPA > >> B160L > >> machine, we can use this opportunit

Re: [PATCH 34/40] lasips2: update VMStateDescription for LASIPS2 device

2022-07-04 Thread Mark Cave-Ayland
On 04/07/2022 14:38, Peter Maydell wrote: On Wed, 29 Jun 2022 at 13:41, Mark Cave-Ayland wrote: Since this series has already introduced a migration break for the HPPA B160L machine, we can use this opportunity to improve the VMStateDescription for the LASIPS2 device. Add the new int_status

Re: [PATCH 34/40] lasips2: update VMStateDescription for LASIPS2 device

2022-07-04 Thread Peter Maydell
On Wed, 29 Jun 2022 at 13:41, Mark Cave-Ayland wrote: > > Since this series has already introduced a migration break for the HPPA B160L > machine, we can use this opportunity to improve the VMStateDescription for > the LASIPS2 device. > > Add the new int_status field to the VMStateDescription and

[PATCH 34/40] lasips2: update VMStateDescription for LASIPS2 device

2022-06-29 Thread Mark Cave-Ayland
Since this series has already introduced a migration break for the HPPA B160L machine, we can use this opportunity to improve the VMStateDescription for the LASIPS2 device. Add the new int_status field to the VMStateDescription and remodel the ports as separate VMSTATE_STRUCT instances. Signed-of