diff options
| author | Johannes Berg <johannes.berg@intel.com> | 2023-06-13 15:57:27 +0300 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2023-06-14 12:32:21 +0200 |
| commit | 93ae81454b1107843ad36dcdc457dd10ee0f2cbe (patch) | |
| tree | 818b1f0ee58a5d5f418ca30ae8e2e2198a5a042b /tools/perf/scripts/python/bin/flamegraph-record | |
| parent | 855e2f60fe341a4fd1f9343ed07d6e7fd05ab3f6 (diff) | |
| download | linux-93ae81454b1107843ad36dcdc457dd10ee0f2cbe.tar.gz linux-93ae81454b1107843ad36dcdc457dd10ee0f2cbe.zip | |
wifi: iwlwifi: dbg-tlv: clear FW debug memory on init
When we restart the firmware, we shouldn't keep old debug data
around. Since the "allocate" function might not reallocate the
memory blocks (they're only freed when we unbind from the device),
clear the memory to have a clean slate for debug data.
This is a bit more complex since we normally don't enter into
the allocation function, but duplicating the logic didn't seem
enticing either, so rework the allocation a bit to always go
into the individual block allocation, but there clear if it's
already allocated, rather than allocating again.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Gregory Greenman <gregory.greenman@intel.com>
Link: https://lore.kernel.org/r/20230613155501.30b82881cfbf.I39520aff8ac95ee64d39dc5913525a1efd7995fa@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/flamegraph-record')
0 files changed, 0 insertions, 0 deletions