RE: The necessity of injecting a hardware exception reported in VMX IDT vectoring information

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > re-execute the L2 code.
> 
> You cannot know why L1 injected an exception.  For example L1 could have
> injected a MCE just to test the code in L1.

Good example!

> 
> This is a scary change, in a scary area of code, with unclear benefits.
> It's going to be hard to convince people. :)

Yes, totally, I'm not seeking a change but more of a direction check.

How about adding comments about why we are NOT doing it?

Thanks!
  Xin




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux