summaryrefslogtreecommitdiffstats
path: root/drivers/mfd/asic3.c
diff options
context:
space:
mode:
authorChangbin Du2017-08-15 07:14:04 +0200
committerZhenyu Wang2017-09-08 08:21:13 +0200
commitf090a00df9ecdab5d066b099c1797e0070e27a36 (patch)
tree72a835f98ed37eb6213133e04bbc712fb90f04e3 /drivers/mfd/asic3.c
parentdrm/i915/kvmgt: Sanitize PCI bar emulation (diff)
downloadkernel-qcow2-linux-f090a00df9ecdab5d066b099c1797e0070e27a36.tar.gz
kernel-qcow2-linux-f090a00df9ecdab5d066b099c1797e0070e27a36.tar.xz
kernel-qcow2-linux-f090a00df9ecdab5d066b099c1797e0070e27a36.zip
drm/i915/gvt: Add emulation for BAR2 (aperture) with normal file RW approach
For vfio-pci, if the region support MMAP then it should support both mmap and normal file access. The user-space is free to choose which is being used. For qemu, we just need add 'x-no-mmap=on' for vfio-pci option. Currently GVTg only support MMAP for BAR2. So GVTg will not work when user turn on x-no-mmap option. This patch added file style access for BAR2, aka the GPU aperture. We map the entire aperture partition of active vGPU to kernel space when guest driver try to enable PCI Memory Space. Then we redirect the file RW operation from kvmgt to this mapped area. Link: https://bugzilla.redhat.com/show_bug.cgi?id=1458032 Signed-off-by: Changbin Du <changbin.du@intel.com> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Diffstat (limited to 'drivers/mfd/asic3.c')
0 files changed, 0 insertions, 0 deletions