On Sun, Feb 21, 2010 at 03:40:55PM +0200, Avi Kivity wrote: > On 02/21/2010 03:14 PM, Avi Kivity wrote: >> >> (Either synthetic msrs, or an new state ioctl). The state would >> contain a bit that says whether the guest is in guest or host mode. >> >> However, since we're breaking the architecture one way or another, >> let's just go with the synthetic INTR intercept. >> > > On the other hand, there is no equivalent intercept in vmx. The > "external interrupt" exit can be configured to run an INTACK cycle and > capture the vector in a vmcs field, and there's no vector we can insert > there (Xen for example uses this). Difficult. We could use an instruction intercept which has no side effect on guest state (invlpg for example). But thats a lot more dangerous than an INTR intercept. What about PENDING_INTERRUPT? Are there hypervisors that may get confused getting this intercept without asking for it? Joerg -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
