On 22/06/2015 19:46, Andreas Färber wrote: >>>>> >>>> On the other hand, I wonder if current_cpu is available in >>>>> >>>> qemu_system_guest_panicked. If so, you could add the field to the >>>>> >>>> generic CPUState struct and migrate it as a subsection of >>>>> >>>> vmstate_cpu_common. >>> >> Hm, not sure whether it is. >> > >> > It should be... > Obviously depends on the call site. :) At some point in cpu-exec.c, > current_cpu gets set to NULL. So the function would at least deserve a > comment on when (not to) use it. I think it could be used anyway even if current_cpu. The difference would be whether the crash is attached to a CPU or not. Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
