diff options
| author | Frederic Weisbecker <frederic@kernel.org> | 2024-10-29 15:54:42 +0300 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2024-10-31 12:41:42 +0300 |
| commit | 17a8945f369ce2de2532ba8abdb93bb5b2d1c118 (patch) | |
| tree | 571ffcb766ed2c70027f528f824fb6489e5c9b25 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | b35108a51cf7bab58d7eace1267d7965978bcdb8 (diff) | |
| download | linux-17a8945f369ce2de2532ba8abdb93bb5b2d1c118.tar.xz | |
clockevents: Improve clockevents_notify_released() comment
When a new clockevent device is added and replaces a previous device,
the latter is put into the released list. Then the released list is
added back.
This may look counter-intuitive but the reason is that released device
might be suitable for other uses. For example a released CPU regular
clockevent can be a better replacement for the current broadcast event.
Similarly a released broadcast clockevent can be a better replacement
for the current regular clockevent of a given CPU.
Improve comments stating about these subtleties.
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/all/20241029125451.54574-2-frederic@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions