summaryrefslogtreecommitdiffstats
path: root/target-lm32
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2011-10-27 15:56:31 +0000
committerAlexander Graf <agraf@suse.de>2011-10-30 20:03:27 +0100
commit74b41e5676568e6560474267bbf1a5a32d3e2c41 (patch)
tree7a9b10d619f34b9248ab10909449293b494275b5 /target-lm32
parent70bca53ffb811ea59dc090b3ca7825cf0bf346a7 (diff)
downloadhqemu-74b41e5676568e6560474267bbf1a5a32d3e2c41.zip
hqemu-74b41e5676568e6560474267bbf1a5a32d3e2c41.tar.gz
pseries: Allow writes to KVM accelerated TCE table
Sufficiently recent kernels include a KVM call to accelerate use of PAPR TCE tables (IOMMU), which are used by PAPR virtual IO devices. This involves qemu mapping the TCE table in from a kernel obtained fd, which currently we do with PROT_READ only. This is a hangover from early (never released) versions of this kernel interface which only permitted read-only mappings and required us to destroy and recreate the table when we needed to clear it from qemu. Now, the kernel permits read-write mappings, and we rely on this to clear the table in spapr_vio_quiesce_one(). However, due to insufficient testing, I forgot to update the actual mapping of the table in kvmppc_create_spapr_tce() to add PROT_WRITE to the mmap(). This patch corrects the oversight. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'target-lm32')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud