summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAlex Elder <elder@linaro.org>2024-01-30 22:23:00 +0300
committerJakub Kicinski <kuba@kernel.org>2024-02-02 07:50:36 +0300
commit688de12f080f10dff8f3ddc80103e432ad8deb0b (patch)
treee90c9ce15e2bf789ddef0aff4c913370a78aea46 /tools/perf/scripts/python/export-to-postgresql.py
parent844ecc4aa78e2f291071025cf76a98287b38856a (diff)
downloadlinux-688de12f080f10dff8f3ddc80103e432ad8deb0b.tar.xz
net: ipa: kill the STARTED IPA power flag
A transmit on the modem netdev can only complete if the IPA hardware is powered. Currently, if a transmit request arrives when the hardware was not powered, further transmits are be stopped to allow power-up to complete. Once power-up completes, transmits are once again enabled. Runtime resume can complete at the same time a transmit request is being handled, and previously there was a race between stopping and restarting transmits. The STARTED flag was used to ensure the stop request in the transmit path was skipped if the start request in the runtime resume path had already occurred. Now, the queue is *always* stopped in the transmit path, *before* determining whether power is ACTIVE. If power is found to already be active (or if the socket buffer is gets dropped), transmit is re-enabled. Otherwise it will (always) be enabled after runtime resume completes. The race between transmit and runtime resume no longer exists, so there is no longer any need to maintain the STARTED flag. Signed-off-by: Alex Elder <elder@linaro.org> Link: https://lore.kernel.org/r/20240130192305.250915-4-elder@linaro.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions