On Tue, Mar 29, 2022, Maxim Levitsky wrote: > On Mon, 2022-03-28 at 17:50 +0000, Sean Christopherson wrote: > > I wouldn't call that abuse, the ioctl() isn't just for migration. Not checking for > > a pending exception is firmly a userspace bug and not something KVM should try to > > fix. > > yes, but to make the right decision, the userspace has to know if there is a pending > exception, and if there is, then merge it (which might even involve triple fault), There's no need for userspace to ever merge exceptions unless KVM supports either exiting to userspace on an exception that can occur during exception delivery, or userspace itself is emulating exception delivery. Outside of debug scenarios, #PF is likely the only exception that might ever be forwarded to userspace. But in those scenarios, userspace is almost always going to fix the #PF and resume the guest. If userspace doesn't fix the #PF, the guest is completely hosed because its IDT will trigger #PF, i.e. it's headed to shutdown regardless of KVM's ABI. VM introspection is the only use case I can think of that might possibly want to emulate exception delivery in userspace, and VMI is a completely new set of APIs, in no small part because supporting something like this in KVM would require far more hooks than KVM provides. > On top of that it is possible that pending excpetion is not intercepted by L1, > but merged result is, so injecting the exception will cause nested VMexit, > which is something that is hard for userspace to model. > > I think that the cleanest way to do this is to add new ioctl, KVM_INJECT_EXCEPTION, > which can do the right thing in the kernel, but I am not sure that it is worth it, > knowing that thankfully userspace doesn't inject exceptions much. > > > > > For #DB, I suspect it's a non-issue. The exit is synchronous, so unless userspace > > is deferring the reflection, which would be architecturally wrong in and of itself, > > there can never be another pending exception. > Could very be, but still there could be corner cases. Like what if you set data fetch > breakpoint on a IDT entry of some exception? I guess during delivery of that exception > there might be #DB, but I am not 100% expert on when and how #DB is generated, so > I can't be sure. Data #DBs are trap-like. The #DB will arrive after exception delivery completes, i.e. will occur "on" the first instruction in the exception handler.
