aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/timerlist.py
diff options
context:
space:
mode:
authorJeffrey Hugo <[email protected]>2022-05-11 09:23:02 -0600
committerWei Liu <[email protected]>2022-05-11 17:50:20 +0000
commitb4b77778ecc5bfbd4e77de1b2fd5c1dd3c655f1f (patch)
treec6ec67092f9314054fb3c6ccc76f65d0fc47ffe9 /scripts/gdb/linux/timerlist.py
parentac6811a9b36f3ceb549d8b84bd8aeedf6026df02 (diff)
PCI: hv: Reuse existing IRTE allocation in compose_msi_msg()
Currently if compose_msi_msg() is called multiple times, it will free any previous IRTE allocation, and generate a new allocation. While nothing prevents this from occurring, it is extraneous when Linux could just reuse the existing allocation and avoid a bunch of overhead. However, when future IRTE allocations operate on blocks of MSIs instead of a single line, freeing the allocation will impact all of the lines. This could cause an issue where an allocation of N MSIs occurs, then some of the lines are retargeted, and finally the allocation is freed/reallocated. The freeing of the allocation removes all of the configuration for the entire block, which requires all the lines to be retargeted, which might not happen since some lines might already be unmasked/active. Signed-off-by: Jeffrey Hugo <[email protected]> Reviewed-by: Dexuan Cui <[email protected]> Tested-by: Dexuan Cui <[email protected]> Tested-by: Michael Kelley <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Wei Liu <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions