Hi, > Right, I have the same question -- although, admittedly, I've not been > CC'd on the cover letter (0/6), and the reason could be captured there.
It wasn't. > On a second thought, I'm (retroactively?) surprised that > LocalApicTimerDxe was (apparently?) first introduced under OvmfPkg -- > i.e., for VMs? That's not impossible, but feels a bit strange. I think the reason is that the next timer interrupt arriving while the handler is running still is *much* more likely in virtual machines because the vCPU does not get 100% of the of the physical CPU time slice. So on OVMF we will continue to need NestedInterruptTplLib. I like the idea to have a Null version of the library, so OVMF does not need its own version of the driver just because of NestedInterruptTplLib. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#113880): https://edk2.groups.io/g/devel/message/113880 Mute This Topic: https://groups.io/mt/103734961/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
