-- On Wed, 8 Aug 2007, Jeremy Fitzhardinge wrote: > Steven Rostedt wrote: > > /* > > * x86 arch doesn't have an easy way to find out where > > * gs is located. So we need to read the MSR. But first > > * we need to save off the rcx, rax and rdx. > > > Why don't you store it in gs? movq %gs:my_gs_base, %rax? Because it can't be trusted. After the swapgs, we are pointing to the RW section of the HV. But by running the guest kernel in ring 1, we have no protection from the guest writing into that area too. So we can't put anything in that section and expect it to be safe after jumping to guest code. The only trusted values, is jumping in after getting there by an interrupt, where the hardware places the values onto the stack. But with Andi's comments, I realized I can point the gs pointer to the RO area. And make a constant offset that will point up into the RW area, so we could save the stack and replace it. -- Steve _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
