On Tue, Oct 30, Jan Beulich wrote: > And iirc you're doing this relocation because otherwise the newly > booting kernel image may get overwritten at an (from its > perspective) arbitrary location. What I'm trying to point out is > that the shared info structure is not the only thing (potentially) > inside the kernel image that might get overwritten - the relocated > (by the old kernel) vCPU info may as well. Plus I think the new > kernel has no way of relocating it a second time (including back > into the shared info structure) with how the hypervisor works at > present.
Thanks, I have not looked at this, nor was I aware of it until now. I will see what needs to be done. Is this also an issue with the xenlinux based PVonHVM code? Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
