On Tue, 2022-04-26 at 19:05 +0200, Paolo Bonzini wrote: > On 4/26/22 18:56, Maxim Levitsky wrote: > > > Yeah, in that case I can't think of anything better than triple fault. > > > > > > Paolo > > > > > But do you think that it would be better to keep the vmcb12 page mapped/pinned while doing the nested run > > which will both solve the problem of calling sleeping function and allow us > > to remove the case of map failing on vm exit? > > > > If I remember correctly, vmx does something like that. > > Yes, it does, but that's because vmx would have to do a lot of mapping > and unmapping for vmread/vmwrite on highmem (32-bit) kernels. So it > maps at vmptrld and unmaps and vmclear. I wouldn't consider it an > example to follow. All right, but what are the downsides of keeping this page mapped? Best regards, Maxim Levitsky > > Paolo >
