On Fri, Mar 17, 2023 at 11:33:38AM -0700, Anish Moorthy wrote: > On Thu, Mar 16, 2023 at 5:02 PM Isaku Yamahata <isaku.yamahata@xxxxxxxxx> wrote: > > > > +7.34 KVM_CAP_X86_MEMORY_FAULT_EXIT > > > +---------------------------------- > > > + > > > +:Architectures: x86 > > > > Why x86 specific? > > Sean was the only one to bring this functionality up and originally > did so in the context of some x86-specific functions, so I assumed > that x86 was the only ask and that maybe the other architectures had > alternative solutions. Admittedly I also wanted to avoid wading > through another big set of -EFAULT references :/ There isn't much :) Sanity checks in mmu.c and some currently unhandled failures to write guest memory in pvtime.c > Those are the only reasons though. Marc, Oliver, should I bring this > capability to Arm as well? The x86 implementation shouldn't preclude UAPI reuse, but I'm not strongly motivated in either direction on this. A clear use case where the exit information is actionable rather than just informational would make the change more desirable. -- Thanks, Oliver
