Avi Kivity wrote: > Dong, Eddie wrote: >> When thinking about live migration support for in kernel irqchip, one >> question comes out which need to be solved first: >> Do we need to support live migration among user level irqchip and >> kernel level? > > Yes. > >> If the answer is yes, kernel level irqchip must keep same state >> with user level, i.e. if Qemu changes the pic/apic/ioapic state >> definition, we need to do corresponding changes too, otherwise >> kernel side can stay as it is. >> > > The qemu state mimics the device state and should be independent of > implementation details. If the qemu state is added too, this most > likely indicates a but that needs to be fixed in kvm as well. > > The best way to do live migration is to copy the kernel state into the > qemu device model, and let qemu do state serialization. This ensures
"copy" means we define some device "state" both in kernel & user. I.e. kernel use user level state definition. > compatibility. > > -- > error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
