diff options
author | 2013-07-23 17:23:54 +0000 | |
---|---|---|
committer | 2013-08-20 10:25:35 -0400 | |
commit | ee0726407feaf504dff304fb603652fb2d778b42 (patch) | |
tree | 408473642b805ba2e56b94766f877fcb8518f24b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | xen: fix ARM build after 6efa20e4 (diff) | |
download | linux-dev-ee0726407feaf504dff304fb603652fb2d778b42.tar.xz linux-dev-ee0726407feaf504dff304fb603652fb2d778b42.zip |
xen/m2p: use GNTTABOP_unmap_and_replace to reinstate the original mapping
GNTTABOP_unmap_grant_ref unmaps a grant and replaces it with a 0
mapping instead of reinstating the original mapping.
Doing so separately would be racy.
To unmap a grant and reinstate the original mapping atomically we use
GNTTABOP_unmap_and_replace.
GNTTABOP_unmap_and_replace doesn't work with GNTMAP_contains_pte, so
don't use it for kmaps. GNTTABOP_unmap_and_replace zeroes the mapping
passed in new_addr so we have to reinstate it, however that is a
per-cpu mapping only used for balloon scratch pages, so we can be sure that
it's not going to be accessed while the mapping is not valid.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
CC: alex@alex.org.uk
CC: dcrisan@flexiant.com
[v1: Konrad fixed up the conflicts]
Conflicts:
arch/x86/xen/p2m.c
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions