After have a check again, for me, I'd like to simply remove it firstly,
since it is only for system mode.
- At present, we are only focus on user mode, and which I haven't done
quite well.
- After we finish user mode, and start system mode, then can add it.
- In this way, this feature will have no any negative effect with our
current coding/reviewing, either no any negative effect for our next
coding/reviewing.
Thanks.
On 4/11/15 05:04, Chen Gang wrote:
>>> +static const VMStateDescription vmstate_tilegx_cpu = {
>>> >> + .name = "cpu",
>>> >> + .unmigratable = 1,
>>> >> +};
>> >
>> > I'd prefer to see a correct VMState from the start -- it's
>> > not very difficult. Migration/snapshotting is much easier
>> > to enforce at the point where we let code in to the tree
>> > than if we let in non-migratable devices and CPUs and then
>> > have to fix them up later...
>> >
>> >
> OK, thanks. I shall try.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
