Monitored Notifications
The monitored notification facility (MNF) introduces the concept of shared triggers between two communicating partitions. MNF uses a port (in the recipient partition) and a connection (in the originating partition) to establish a notification channel that is unidirectional and monitored by the hypervisor. A monitor port and connection pair alone is not enough to form the notification channel. In addition, the pair must be associated with an event connection through the monitored notification parameters in the monitored notification page.
When the hypervisor creates a notification channel, the hypervisor establishes a monitored notification mechanism in an overlay page that includes the following items:
-
A trigger
-
A latency hint
-
A set of input parameters that is appropriate for the HvSignalEvent hypercall function.
After the hypervisor establishes the monitor page, the hypervisor periodically examines the trigger at a rate that is subject to the latency hint to determine if a notification is warranted. If so, the hypervisor calls HvSignalEvent internally on behalf of the originating guest. The behavior is the same as if the originating guest had called HvSignalEvent directly.
The following sections describe the monitored notification mechanism:
Send comments about this topic to Microsoft
Build date: 11/16/2013