xen: use spin_lock_nest_lock when pinning a pagetable

Browse source

When pinning/unpinning a pagetable with split pte locks, we can end up
holding multiple pte locks at once (we need to hold the locks while
there's a pending batched hypercall affecting the pte page).  Because
all the pte locks are in the same lock class, lockdep thinks that
we're potentially taking a lock recursively.

This warning is spurious because we always take the pte locks while
holding mm->page_table_lock.  lockdep now has spin_lock_nest_lock to
express this kind of dominant lock use, so use it here so that lockdep
knows what's going on.

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>

...

This commit is contained in:

Jeremy Fitzhardinge 2008-10-08 13:01:39 -07:00 • committed by Ingo Molnar

parent d19c8e516e

commit eefb47f6a1

2 changed files with 48 additions and 29 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

74

arch/x86/xen/mmu.c

View file

3

arch/x86/xen/mmu.h

View file