On 8/23/22 15:33, Paul Menzel wrote: >> Thanks for the extra debug info. Unfortunately, nothing is really >> sticking out as an obvious problem. >> >> The EREMOVE return codes would be interesting to know, as well as an >> idea what the physical addresses are that fail and the _counts_ of how >> many pages get sanitized versus fail. > > Is there a knob to print out this information? Or way to get this > information using ftrace? I’d like to avoid rebuilding the Linux kernel. You can probably do it with a kprobe and ftrace, but it's a little bit of a pain since the ENCL* instructions are all inlined and don't get wrapped in actual function calls. I'd just rebuild the kernel if it were me. Maybe we just just uninline all of the ENCL* instruction so that we *can* more easily trace them. It's not like they are performance sensitive.
