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]

 



On 4/6/23 08:37, Yao, Yuan wrote:
It's definitely broken for nested case if the exception Is injected
by L1 in the first place, but if it's injected after interception (by
L1) for same exception, and it's trap, it can be regenerated by
                                   ^^^^

if it's a fault

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.

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

Paolo




[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