Re: [Qemu-devel] [PATCH v4 5/6] xics: directly register ICPState objects to vmstate

2017-06-13 Thread David Gibson
On Tue, Jun 13, 2017 at 09:14:55AM +0200, Greg Kurz wrote: > On Mon, 12 Jun 2017 22:15:46 +0800 > David Gibson wrote: > > > On Thu, Jun 08, 2017 at 03:43:18PM +0200, Greg Kurz wrote: > > > The ICPState objects are currently registered to vmstate as qdev objects. > > > Their instance ids are hence

Re: [Qemu-devel] [PATCH v4 5/6] xics: directly register ICPState objects to vmstate

2017-06-13 Thread Greg Kurz
On Mon, 12 Jun 2017 22:15:46 +0800 David Gibson wrote: > On Thu, Jun 08, 2017 at 03:43:18PM +0200, Greg Kurz wrote: > > The ICPState objects are currently registered to vmstate as qdev objects. > > Their instance ids are hence computed automatically in the migration code, > > and thus depends on

Re: [Qemu-devel] [PATCH v4 5/6] xics: directly register ICPState objects to vmstate

2017-06-12 Thread David Gibson
On Thu, Jun 08, 2017 at 03:43:18PM +0200, Greg Kurz wrote: > The ICPState objects are currently registered to vmstate as qdev objects. > Their instance ids are hence computed automatically in the migration code, > and thus depends on the order the CPU cores were plugged. > > If the destination had

[Qemu-devel] [PATCH v4 5/6] xics: directly register ICPState objects to vmstate

2017-06-08 Thread Greg Kurz
The ICPState objects are currently registered to vmstate as qdev objects. Their instance ids are hence computed automatically in the migration code, and thus depends on the order the CPU cores were plugged. If the destination had its CPU cores plugged in a different order than the source, then ICP