diff options
author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2016-07-25 08:43:13 (GMT) |
---|---|---|
committer | Tony Luck <tony.luck@intel.com> | 2016-07-25 16:55:32 (GMT) |
commit | fbb0e4da96f4503e65bc4fb627cf4e1d7c8c64e6 (patch) | |
tree | 7c17fa1f6f451a838974067ef63372818404c495 /arch/arc/boot | |
parent | 70f4f9352317ed8bc70cd7fe2bf34a3f9f7f21e3 (diff) | |
download | linux-fbb0e4da96f4503e65bc4fb627cf4e1d7c8c64e6.tar.xz |
ia64: salinfo: use a waitqueue instead a sema down/up combo
The only purpose of down_try_lock() followed by up() seems to be to wake
up a possible reader. This patch replaces it with a wake-queue. There is
no locking around cpumask_empty() and the test is re-done in case there
was no hit.
With wait_event_interruptible_lock_irq(,&data_saved_lock) we would probably
be able to get rid of the `retry` label. However we still can return CPU
X which is valid now but later (after the lock dropped) the event may
have been removed because the CPU went offline.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'arch/arc/boot')
0 files changed, 0 insertions, 0 deletions