diff options
author | Harald Freudenberger <[email protected]> | 2021-06-30 16:10:56 +0200 |
---|---|---|
committer | Vasily Gorbik <[email protected]> | 2021-07-08 15:37:27 +0200 |
commit | 1f0d22defd59f603d63ba51483eeb8d72726ce8b (patch) | |
tree | 2d5596036c3cdb260d56cc3b7902490f72ba25a2 /scripts/gdb/linux/tasks.py | |
parent | bd39654a2282c1a51c044575a6bc00d641d5dfd1 (diff) |
s390/ap: Rework ap_dqap to deal with messages greater than recv buffer
Rework of the ap_dqap() inline function with the dqap inline assembler
invocation and the caller code in ap_queue.c to be able to handle
replies which exceed the receive buffer size.
ap_dqap() now provides two additional parameters to handle together
with the caller the case where a reply in the firmware queue entry
exceeds the given message buffer size. It depends on the caller how to
exactly handle this. The behavior implemented now by ap_sm_recv() in
ap_queue.c is to simple purge this entry from the firmware queue and
let the caller 'receive' a -EMSGSIZE for the request without
delivering any reply data - not even a truncated reply message.
However, the reworked ap_dqap() could now get invoked in a way that
the message is received in multiple parts and the caller assembles the
parts into one reply message.
Signed-off-by: Harald Freudenberger <[email protected]>
Suggested-by: Juergen Christ <[email protected]>
Reviewed-by: Juergen Christ <[email protected]>
Signed-off-by: Vasily Gorbik <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions