[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Segment registers at top of stack


While debugging an issue of 0xdeadbeef's appearing in a crash report, I have discovered that the es thru gs entries in cpu_user_regs appear to be completely unused on a 64bit hypervisor per-cpu stack.

In 64bit mode, all segment register changes happen in {load,save}segments(). The only code I can find which ever sets these values is the NDEBUG poisoning on the VMX/SVM vmexit hypervisor entry paths.

If the values are indeed completely unused, would it be sensible to remove them from the per-cpu stacks as we have now dropped support for the 32bit hypervisor (which certainly does use them)?

On the plus side, it would mean that our hypervisor entry points would be at the start of a cache line, rather than half way along it, and we gain an extra 32 bytes of space on the cpu stacks. On the other hand, doing it neatly would be rather more difficult, and might just be a lot of effort for minimal gains.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.