AP bus and zcrypt uevents
The AP bus and the zcrypt device driver generate uevents.
Table 1 summarizes the uevents that are generated by the AP bus, and Table 2 those that are generated by the zcrypt device driver. The uevents include one or more zcrypt-specific properties, see Properties.
Uevent | Example |
---|---|
An ADD uevent is generated for each cryptographic adapter when the AP card device struct is registered at the Linux® device model. |
|
An ADD uevent is generated for each AP queue when the AP queue device struct is registered at the Linux device model. |
|
A BIND uevent is generated for each cryptographic adapter when the AP card device is bound to a device driver. |
|
A BIND uevent is generated for each AP queue when the AP queue device is bound to a device driver. |
|
A CHANGE uevent is generated when the first AP bus scan is complete. This uevent indicates
that all AP devices have been detected and are represented in sysfs. The AP devices might still require bindings to the appropriate zcrypt device drivers to become usable to user space. |
|
A CHANGE uevent is generated when all AP devices are bound to device drivers. This event can recur, for example, in response to user space actions that change driver bindings through unbind or rebind. The uevent is then generated when all device driver bindings are, again, complete. The COMPLETECOUNT property shows how often this uevent has occurred. |
|
An UNBIND uevent is generated for each cryptographic adapter when the AP card device is unbound from its device driver. |
|
An UNBIND uevent is generated for each AP queue when the AP queue device is unbound from its device driver. |
|
A REMOVE uevent is generated for each cryptographic adapter when the AP card device struct is unregistered at the Linux device model. |
|
A REMOVE uevent is generated for each AP queue when the AP queue device struct is unregistered at the Linux device model. |
|
A CHANGE uevent is generated for each cryptographic adapter when the configuration state of
the adapter changes. The configuration state can change when the adapter is switched between
The configuration state can also be changed from Linux, see AP queue status overview. The property field CONFIG shows the new configuration state of the adapter (0 or 1). |
|
A CHANGE uevent is generated for each AP queue when the configuration state of the adapter changes. The property field CONFIG shows the new configuration state of the queue (0 or 1). |
|
Uevent | Example |
---|---|
A CHANGE uevent is generated when the online state, within Linux, of a cryptographic adapter changes. The online state can be changed through the online sysfs attribute of the card device. An adapter can also be set offline in response to failures being detected within the zcrypt device driver. The property field ONLINE shows the new online state of the adapter (0 or 1). |
|
A CHANGE uevent is generated when the online state, within Linux, of an AP queue changes. The online state can be changed through the online sysfs attribute of the AP queue device. An AP queue can also be set offline in response to failures being detected within the zcrypt device driver. The property field ONLINE shows the new online state of the AP queue (0 or 1). |
|
Properties
- COMPLETECOUNT
- The bindings complete counter. For the first bindings complete uevent its value is 1. The value is then incremented with each subsequent bindings complete uevent.
- CONFIG
- The new configuration state, 0 or 1, for an adapter or AP queue.
- DEVPATH
- The path to the device representation in sysfs. This path does not include the sysfs mount point, which is usually /sys.
- DEVTYPE
- Indicates whether the uevent is for an adapter (
ap_card
) or for an AP queue (ap_queue
). - DEV_TYPE
- The device type as a 4-digit hexadecimal value.
- DRIVER
- The device driver module that is bound to or unbound from the AP device, for example, cex4card, cex4queue, or vfio_ap.
- INITSCAN
- Indication that the initial AP bus scan is complete. The value is always
.done
- MODALIAS: ap:t<xx>
- The module alias of the AP device, where <xx> is a two-digit hexadecimal value for the mapped device type.
- MODE
- The mode of operation of the adapter or AP queue:
- accel
- for cryptographic accelerator mode.
- ep11
- for EP11 coprocessor mode.
- cca
- for CCA coprocessor mode.
- ONLINE
- The online state, within Linux, of the adapter or AP queue.
- SUBSYSTEM
- Identifier for the AP subsystem. The value is always
.ap