Notification Functions

All of the functions described below return a 32-bit integer that is one of the values from the standard Microvisor enumeration MvStatus. All possible error values for a given system call are provided with each function's description.

Success is always signaled by a return value of zero (MV_STATUS_OKAY).

Instantiate a notification dispatch center

You configure the notification center by providing a pointer to a NotificationSetup structure:

1
struct MvNotificationSetup {
2
  uint32_t irq;
3
  struct MvNotification *buffer;
4
  uint32_t buffer_size;
5
}

These properties are:

• irq — The number of the non-secure interrupt line that will be triggered to signal that a new notification has been posted. The call to mvSetupNotifications() will return an error if this value indicates a secure interrupt, or has already been assigned to a notification center.
• buffer — A pointer to a previously allocated buffer. It must be 8-byte aligned.
• buffer_size — The size of the center's buffer in bytes. It must be at least 32 bytes and a multiple of 16 bytes.

Halt the dispatch of messages from a notification center

To stop receiving notifications from a specific notification center, call mvCloseNotifications() and pass in a pointer to the memory in which the center's handle is stored.

If the center is in use by other objects — for example, the same center is dispatching notifications from a network and a channel — calling mvCloseNotifications() will stop the delivery of notifications from all of its sources, and no error will be issued.

The center's non-secure interrupt will not be pended by Microvisor when the center is closed. If the interrupt has already been pended, it will not be cleared. This is the job of the application.

This example uses variables defined in the example above.

1
// If we have a valid notification center handle, then ask Microvisor
2
// to tear down the center and confirm acceptance of the request.
3
if (http_handles.notification != 0) {
4
  status = mvCloseNotifications(&http_handles.notification);
5
  assert((status == MV_STATUS_OKAY) && "[ERROR] Could not close HTTP channel NC");
6
}

Start the dispatch of system messages to a notification center

To begin receiving system notifications, call mvOpenSystemNotification() and pass in a pointer to the memory in which the system notification configuration is stored, and where a system event sender's handle will be stored.

The params parameter takes a pointer to a MvOpenSystemNotificationParams structure:

1
struct MvOpenSystemNotificationParams {
2
    MvNotificationHandle notification_handle;
3
    uint32_t notification_tag;
4
    enum MvSystemNotificationSource notification_source;
5
}

These properties are:

• notification_handle — The handle that will be issued for the notification center messages.
• notification_tag — An arbitrary 32-bit value you can specify and which will then be included in all notifications relating to this center.
• notification_source — One or more MvSystemNotificationSource values OR'd to indicate the type(s) of notifications to be issued. See below.

Available MvSystemNotificationSource values include:

1
enum MvSystemNotificationSource {
2
    MV_SYSTEMNOTIFICATIONSOURCE_NETWORK,
3
    MV_SYSTEMNOTIFICATIONSOURCE_UPDATE
4
};

Use MV_SYSTEMNOTIFICATIONSOURCE_UPDATE to receive polite deployment notifications.

Halt the dispatch of system messages to a notification center

To stop receiving system notifications, call mvCloseSystemNotification() and pass in the handle of the system event sender that was provided when you called mvOpenSystemNotification().

This call does not tear down the notification center to which system notifications are being sent.