diff options
author | Peter Zijlstra <peterz@infradead.org> | 2015-07-03 18:53:58 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-07-03 18:55:00 +0200 |
commit | 2ecd9d29abb171d6e97a4f3eb29d7456a11401b7 (patch) | |
tree | 2c31785e4dff264db31ee0dea5f74c5d29905898 /lib/iomap.c | |
parent | 9bdc771f2c29a11920f477fba05a58e23ee42554 (diff) | |
download | linux-2ecd9d29abb171d6e97a4f3eb29d7456a11401b7.tar.gz linux-2ecd9d29abb171d6e97a4f3eb29d7456a11401b7.tar.bz2 linux-2ecd9d29abb171d6e97a4f3eb29d7456a11401b7.zip |
sched, preempt_notifier: separate notifier registration from static_key inc/dec
Commit 1cde2930e154 ("sched/preempt: Add static_key() to preempt_notifiers")
had two problems. First, the preempt-notifier API needs to sleep with the
addition of the static_key, we do however need to hold off preemption
while modifying the preempt notifier list, otherwise a preemption could
observe an inconsistent list state. KVM correctly registers and
unregisters preempt notifiers with preemption disabled, so the sleep
caused dmesg splats.
Second, KVM registers and unregisters preemption notifiers very often
(in vcpu_load/vcpu_put). With a single uniprocessor guest the static key
would move between 0 and 1 continuously, hitting the slow path on every
userspace exit.
To fix this, wrap the static_key inc/dec in a new API, and call it from
KVM.
Fixes: 1cde2930e154 ("sched/preempt: Add static_key() to preempt_notifiers")
Reported-by: Pontus Fuchs <pontus.fuchs@gmail.com>
Reported-by: Takashi Iwai <tiwai@suse.de>
Tested-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'lib/iomap.c')
0 files changed, 0 insertions, 0 deletions