aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/ide/ide.c
diff options
context:
space:
mode:
authorJames Bottomley <James.Bottomley@HansenPartnership.com>2011-01-20 12:54:18 -0600
committerJames Bottomley <James.Bottomley@suse.de>2011-02-09 11:22:21 -0600
commit8e1964a98920100f113ad26f78220ea706dbfa2b (patch)
treeeff1ff22212732ee39eab6919123886aea3fa1d4 /drivers/ide/ide.c
parent100b33c8bd8a3235fd0b7948338d6cbb3db3c63d (diff)
downloadkernel_samsung_tuna-8e1964a98920100f113ad26f78220ea706dbfa2b.zip
kernel_samsung_tuna-8e1964a98920100f113ad26f78220ea706dbfa2b.tar.gz
kernel_samsung_tuna-8e1964a98920100f113ad26f78220ea706dbfa2b.tar.bz2
[PARISC] fix vmap flush/invalidate
On parisc, we never implemented invalidate_kernel_vmap_range() because it was unnecessary for the xfs use case. However, we do need to implement an invalidate for the opposite use case (which occurred in a recent NFS change) where the user wants to read through the vmap range and write via the kernel address. There's an additional complexity to this in that if the page has no userspace mappings, it might have dirty cache lines in the kernel (indicated by the PG_dcache_dirty bit). In order to get full coherency, we need to flush these pages through the kernel mapping before invalidating the vmap range. Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/ide/ide.c')
0 files changed, 0 insertions, 0 deletions