The guest is at fault here as it expects Hyper-V to consume argumentsPerhaps Siddharth should clarify this, but I read it as Hyper-V beingAlthough the Hyper-v TLFS mentions that a guest cannot use this featureNo, please don't do this. Check the feature bit(s) before you issue
unless the hypervisor advertises support for it, some hypercalls which
we plan on upstreaming in future uses them anyway.
hypercalls which rely on the extended interface.
buggy and using XMM arguments unconditionally.
from XMM registers for certain hypercalls (that we are working) even if
we didn't expose the feature via CPUID bits.