On Mon, 13 Mar 2006, Zachary Amsden wrote:
> One shortcut we have found most helpful is to simply disable NMI delivery
> to the paravirtualized kernel. There is no reason NMIs can't be
> supported, but typical uses for them are not as productive in a
> virtualized environment. Watchdog NMIs are of limited use if the OS is
> already correct and running on stable hardware; profiling NMIs are
> similarly of less use, since this task is accomplished with more accuracy
> in the VMM itself; and NMIs for machine check errors should be handled
> outside of the VM. The addition of NMI support does create additional
> complexity for the trap handling code in the VM, and although the task is
> surmountable, the value proposal is debatable. Here, again, feedback
> is desired.
A guest unmaskable (with programmable interrupt frequency) event would
certainly be of use and would take care of the majority of NMI users.
Thanks,
Zwane
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
