On 2022/10/13 23:39, Dave Hansen wrote: > I wanted an example here of a SIGBUS that can occur from sources *OTHER* > than a recoverable machine check. Oh, got it, it should like this: There is already a signal-based ABI to tell userspace about machine checks. But, SGX does not use that ABI. Today, the kernel delivers a generic SIGBUS if a machine check occurs when accessing SGX memory. Userspace can not differentiate that SIGBUS from invalid address alignment, nonexistent physical address or object-specific hardware error, so it is very unlikely to be able to recover from the signal and the app will die. Thanks for the clarification, Dave. Best Regards, Zhiquan
