On Sun, Aug 04, 2013 at 12:53:56PM +0300, Gleb Natapov wrote: > On Sun, Aug 04, 2013 at 12:32:06PM +0300, Gleb Natapov wrote: > > On Sun, Aug 04, 2013 at 11:24:41AM +0200, Jan Kiszka wrote: > > > On 2013-08-01 16:08, Gleb Natapov wrote: > > > > Another day -- another version of the nested EPT patches. In this version > > > > included fix for need_remote_flush() with shadowed ept, set bits 6:8 > > > > of exit_qualification during ept_violation, update_permission_bitmask() > > > > made to work with shadowed ept pages and other small adjustment according > > > > to review comments. > > > > > > Was just testing it here and ran into a bug: I've L2 accessing the HPET > > > MMIO region that my L1 passed through from L0 (where it is supposed to > > > be emulated in this setup). This used to work with an older posting of > > Not sure I understand your setup. L0 emulates HPET, L1 passes it through > > to L2 (mmaps it and creates kvm slot that points to it) and when L2 > > accessed it it locks up? > > > > > Jun, but now it locks up (infinite loop over L2's MMIO access, no L2->L1 > > > transition). Any ideas where to look for debugging this? > > > > > Can you do an ftrace -e kvm -e kvmmmu? Unit test will also be helpful :) > > > I did an MMIO access from nested guest in the vmx unit test (which is > naturally passed through to L0 since L1 is so simple) and I can see that > the access hits L0. > But then unit test not yet uses nested EPT :) -- Gleb. -- 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
