summaryrefslogtreecommitdiff
path: root/lib/debugobjects.c
diff options
context:
space:
mode:
authorHeiko Carstens <hca@linux.ibm.com>2025-10-21 11:10:55 +0200
committerHeiko Carstens <hca@linux.ibm.com>2025-10-21 11:10:55 +0200
commit5c02c74dd482e0fb6c303a7e781812c26f06bcb8 (patch)
tree8608423a2e41910a96c58f08e183bced32d94de7 /lib/debugobjects.c
parent215231deeadd5942ce9fd61ea420c2c2105f6459 (diff)
parent9c11918040d6aa19c407ead4dc86b65e664f401f (diff)
Merge branch 'ap-bus-trace-events'
Harald Freudenberger says: ==================== Investigations related to runtime of crypto requests has revealed a lack of performance or runtime information with crypto requests. There are the two zcrypt ioctl trace events covering the entry and exit of an ioctl with crypto requests giving the overall runtime within the kernel. However, there is no way to figure out the time where a request is enqueued into the AP bus queue but not pushed into the firmware queue. Then there is no information about the runtime of an request during processing in the firmware. And finally some info about pulling the reply from the firmware and delivering it into user space is missing. This series is aiming to provide a way to collect measurements which can be used to cover these runtime information for each crypto request/reply. ==================== Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'lib/debugobjects.c')
0 files changed, 0 insertions, 0 deletions