summaryrefslogtreecommitdiff
path: root/security/capability.c
diff options
context:
space:
mode:
authorChristoffer Dall <c.dall@virtualopensystems.com>2013-01-23 18:18:04 (GMT)
committerMarc Zyngier <marc.zyngier@arm.com>2013-02-11 18:58:39 (GMT)
commit3401d54696f992edf036f00f46c8c399d1b75c2a (patch)
treebbb3bb02050b3b513e4b55839b553d793c1e63b9 /security/capability.c
parenta96ab03917dcf4c9477d03b31e8d74779bca1074 (diff)
downloadlinux-fsl-qoriq-3401d54696f992edf036f00f46c8c399d1b75c2a.tar.xz
KVM: ARM: Introduce KVM_ARM_SET_DEVICE_ADDR ioctl
On ARM some bits are specific to the model being emulated for the guest and user space needs a way to tell the kernel about those bits. An example is mmio device base addresses, where KVM must know the base address for a given device to properly emulate mmio accesses within a certain address range or directly map a device with virtualiation extensions into the guest address space. We make this API ARM-specific as we haven't yet reached a consensus for a generic API for all KVM architectures that will allow us to do something like this. Reviewed-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Christoffer Dall <c.dall@virtualopensystems.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'security/capability.c')
0 files changed, 0 insertions, 0 deletions