summaryrefslogtreecommitdiff
path: root/fs/jbd2/commit.c
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@samba.org>2012-10-15 01:15:41 (GMT)
committerAlexander Graf <agraf@suse.de>2012-10-30 09:54:53 (GMT)
commit512691d4907d7cf4b8d05c6f8572d1fa60ccec20 (patch)
tree8cb0fb7f8cdc1b0283ef7cba585775f47b974ebc /fs/jbd2/commit.c
parentc99ec973a63e2249020d6d93a46d7572432da6a2 (diff)
downloadlinux-512691d4907d7cf4b8d05c6f8572d1fa60ccec20.tar.xz
KVM: PPC: Book3S HV: Allow KVM guests to stop secondary threads coming online
When a Book3S HV KVM guest is running, we need the host to be in single-thread mode, that is, all of the cores (or at least all of the cores where the KVM guest could run) to be running only one active hardware thread. This is because of the hardware restriction in POWER processors that all of the hardware threads in the core must be in the same logical partition. Complying with this restriction is much easier if, from the host kernel's point of view, only one hardware thread is active. This adds two hooks in the SMP hotplug code to allow the KVM code to make sure that secondary threads (i.e. hardware threads other than thread 0) cannot come online while any KVM guest exists. The KVM code still has to check that any core where it runs a guest has the secondary threads offline, but having done that check it can now be sure that they will not come online while the guest is running. Signed-off-by: Paul Mackerras <paulus@samba.org> Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions