On 10.01.2010, at 13:22, Avi Kivity wrote: > On 01/10/2010 04:27 AM, Alexander Graf wrote: >> When we get a program interrupt in guest kernel mode, we try to emulate the >> instruction. >> >> If that doesn't fail, we report to the user and try again - at the exact same >> instruction pointer. So if the guest kernel really does trigger an invalid >> instruction, we loop forever. >> >> So let's better go and forward program exceptions to the guest when we don't >> know the instruction we're supposed to emulate. >> >> > > Applied both, and queued for .33. I was able to guess this from the description, but please mention it explicitly in the future. I'm not sure what to mention. From a stability point of view, all the Book3S patches should go in .33 because they all fix severe bugs. But then again the question is what our goal for .33 is. If we only want to give out the message "KVM for Book3S is coming! Stay tuned!" then we shouldn't do any updates for .33. If we want to have something working to the best of our knowledge, all patches should go into .33. Alex -- 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
