In TDX guests, these WBINVD operations cause #VE exceptions. For debug,...but it doesn't WARN() it triggers unhandled #VE, unless I missed
it would be ideal for the #VE handler to be able to WARN() when an
unexpected WBINVD occurs. (<--- problem #2)
another patch that precedes this that turns it into a WARN()? If a
code path expects WBINVD for correct operation and the guest can't
execute that sounds fatal, not a WARN to me.