summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorHarald Freudenberger <freude@linux.ibm.com>2026-04-27 18:43:14 +0200
committerAlexander Gordeev <agordeev@linux.ibm.com>2026-05-11 16:42:31 +0200
commit4179c39842273d3452db062ef73f850327bfd638 (patch)
tree49cdb4eb4c96c5ffb04e60185013dd821c61c8d5 /scripts/Makefile.thinlto
parent1f5ea7ade1bfb315ddec17814be31d21bfa28bc3 (diff)
s390/ap: Implement SE bind and associate uevents
Notify userspace about two important events on AP queues when run within Secure Execution (SE) environment: - Send AP CHANGE uevent with "SE_BIND=1" on successful bind operation on this AP queue device. - Send AP CHANGE uevent with "SE_ASSOC=<association_index>" on successful association operation with the secret of the reported index on this AP queue device. Note there is no SE unbind/unassociate event. Unbind/unassociate can have different triggers and technically there is no signaling done which the AP code could catch. A user space application can, if this information is crucial, query the sysfs attribute se_bind on the AP queue which runs a synchronous TAPQ. If the attribute returns with "unbound" a reset took place and SE bind and associate states are unbound and unassociated. Suggested-by: Marc Hartmayer mhartmay@linux.ibm.com Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Reviewed-by: Holger Dengler <dengler@linux.ibm.com> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions