linux-toradex.git/virt/kvm/Kconfig, branch v4.4.73

KVM: don't pointlessly leave KVM_COMPAT=y in non-KVM configs

2015-11-04T15:24:30+00:00

The symbol was missing a KVM dependency.

Signed-off-by: Jan Beulich 
Signed-off-by: Paolo Bonzini

KVM: introduce kvm_arch functions for IRQ bypass

2015-10-01T13:06:45+00:00

This patch introduces
- kvm_arch_irq_bypass_add_producer
- kvm_arch_irq_bypass_del_producer
- kvm_arch_irq_bypass_stop
- kvm_arch_irq_bypass_start

They make possible to specialize the KVM IRQ bypass consumer in
case CONFIG_KVM_HAVE_IRQ_BYPASS is set.

Signed-off-by: Eric Auger 
[Add weak implementations of the callbacks. - Feng]
Signed-off-by: Feng Wu 
Reviewed-by: Alex Williamson 
Signed-off-by: Paolo Bonzini

KVM: Disable compat ioctl for s390

2015-02-09T11:44:14+00:00

We never had a 31bit QEMU/kuli running. We would need to review several
ioctls to check if this creates holes, bugs or whatever to make it work.
Lets just disable compat support for KVM on s390.

Signed-off-by: Christian Borntraeger 
Acked-by: Paolo Bonzini

KVM: Remove unused config symbol

2015-01-23T09:52:03+00:00

The dirty patch logging series introduced both
HAVE_KVM_ARCH_DIRTY_LOG_PROTECT and KVM_GENERIC_DIRTYLOG_READ_PROTECT
config symbols, but only KVM_GENERIC_DIRTYLOG_READ_PROTECT is used.
Just remove the unused one.

(The config symbol was renamed during the development of the patch
series and the old name just creeped in by accident.()

Reported-by: Paul Bolle 
Signed-off-by: Christoffer Dall

KVM: Add generic support for dirty page logging

2015-01-16T13:40:14+00:00

kvm_get_dirty_log() provides generic handling of dirty bitmap, currently reused
by several architectures. Building on that we intrdoduce
kvm_get_dirty_log_protect() adding write protection to mark these pages dirty
for future write access, before next KVM_GET_DIRTY_LOG ioctl call from user
space.

Reviewed-by: Christoffer Dall 
Signed-off-by: Mario Smarduch

KVM: Add architecture-defined TLB flush support

2015-01-16T13:40:14+00:00

Allow architectures to override the generic kvm_flush_remote_tlbs()
function via HAVE_KVM_ARCH_TLB_FLUSH_ALL. ARMv7 will need this to
provide its own TLB flush interface.

Reviewed-by: Christoffer Dall 
Reviewed-by: Marc Zyngier 
Reviewed-by: Paolo Bonzini 
Signed-off-by: Mario Smarduch

KVM: Give IRQFD its own separate enabling Kconfig option

2014-08-05T12:26:28+00:00

Currently, the IRQFD code is conditional on CONFIG_HAVE_KVM_IRQ_ROUTING.
So that we can have the IRQFD code compiled in without having the
IRQ routing code, this creates a new CONFIG_HAVE_KVM_IRQFD, makes
the IRQFD code conditional on it instead of CONFIG_HAVE_KVM_IRQ_ROUTING,
and makes all the platforms that currently select HAVE_KVM_IRQ_ROUTING
also select HAVE_KVM_IRQFD.

Signed-off-by: Paul Mackerras 
Tested-by: Eric Auger 
Tested-by: Cornelia Huck 
Signed-off-by: Paolo Bonzini

KVM: async_pf: Provide additional direct page notification

2014-01-30T11:51:38+00:00

By setting a Kconfig option, the architecture can control when
guest notifications will be presented by the apf backend.
There is the default batch mechanism, working as before, where the vcpu
thread should pull in this information.
Opposite to this, there is now the direct mechanism, that will push the
information to the guest.
This way s390 can use an already existing architecture interface.

Still the vcpu thread should call check_completion to cleanup leftovers.

Signed-off-by: Dominik Dingel 
Signed-off-by: Christian Borntraeger

kvm: Add VFIO device

2013-10-30T18:02:03+00:00

So far we've succeeded at making KVM and VFIO mostly unaware of each
other, but areas are cropping up where a connection beyond eventfds
and irqfds needs to be made.  This patch introduces a KVM-VFIO device
that is meant to be a gateway for such interaction.  The user creates
the device and can add and remove VFIO groups to it via file
descriptors.  When a group is added, KVM verifies the group is valid
and gets a reference to it via the VFIO external user interface.

Signed-off-by: Alex Williamson 
Signed-off-by: Paolo Bonzini

KVM: Introduce CONFIG_HAVE_KVM_IRQ_ROUTING

2013-04-26T18:27:14+00:00

Quite a bit of code in KVM has been conditionalized on availability of
IOAPIC emulation. However, most of it is generically applicable to
platforms that don't have an IOPIC, but a different type of irq chip.

Make code that only relies on IRQ routing, not an APIC itself, on
CONFIG_HAVE_KVM_IRQ_ROUTING, so that we can reuse it later.

Signed-off-by: Alexander Graf 
Acked-by: Michael S. Tsirkin