linux.git/virt, branch v4.7-rc1

KVM: Create debugfs dir and stat files for each VM

2016-05-25T14:12:05+00:00

This patch adds a kvm debugfs subdirectory for each VM, which is named
after its pid and file descriptor. The directories contain the same
kind of files that are already in the kvm debugfs directory, but the
data exported through them is now VM specific.

This makes the debugfs kvm data a convenient alternative to the
tracepoints which already have per VM data. The debugfs data is easy
to read and low overhead.

CC: Dan Carpenter  [includes fixes by Dan Carpenter]
Signed-off-by: Janosch Frank 
Signed-off-by: Paolo Bonzini

Merge tag 'kvm-arm-for-4-7-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into kvm-next

2016-05-24T10:10:51+00:00

KVM/ARM Changes for v4.7 take 2

"The GIC is dead; Long live the GIC"

This set of changes include the new vgic, which is a reimplementation of
our horribly broken legacy vgic implementation.  The two implementations
will live side-by-side (with the new being the configured default) for
one kernel release and then we'll remove it.

Also fixes a non-critical issue with virtual abort injection to guests.

KVM: arm/arm64: vgic-new: Synchronize changes to active state

2016-05-20T14:26:38+00:00

When modifying the active state of an interrupt via the MMIO interface,
we should ensure that the write has the intended effect.

If a guest sets an interrupt to active, but that interrupt is already
flushed into a list register on a running VCPU, then that VCPU will
write the active state back into the struct vgic_irq upon returning from
the guest and syncing its state.  This is a non-benign race, because the
guest can observe that an interrupt is not active, and it can have a
reasonable expectations that other VCPUs will not ack any IRQs, and then
set the state to active, and expect it to stay that way.  Currently we
are not honoring this case.

Thefore, change both the SACTIVE and CACTIVE mmio handlers to stop the
world, change the irq state, potentially queue the irq if we're setting
it to active, and then continue.

We take this chance to slightly optimize these functions by not stopping
the world when touching private interrupts where there is inherently no
possible race.

Signed-off-by: Christoffer Dall

KVM: arm/arm64: vgic-new: enable build

2016-05-20T13:40:09+00:00

Now that the new VGIC implementation has reached feature parity with
the old one, add the new files to the build system and add a Kconfig
option to switch between the two versions.
We set the default to the new version to get maximum test coverage,
in case people experience problems they can switch back to the old
behaviour if needed.

Signed-off-by: Andre Przywara 
Acked-by: Christoffer Dall

KVM: arm/arm64: vgic-new: implement mapped IRQ handling

2016-05-20T13:40:09+00:00

We now store the mapped hardware IRQ number in our struct, so we
don't need the irq_phys_map for the new VGIC.
Implement the hardware IRQ mapping on top of the reworked arch
timer interface.

Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall

KVM: arm/arm64: vgic-new: Wire up irqfd injection

2016-05-20T13:40:08+00:00

Connect to the new VGIC to the irqfd framework, so that we can
inject IRQs.
GSI routing and MSI routing is not yet implemented.

Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall

KVM: arm/arm64: vgic-new: Add vgic_v2/v3_enable

2016-05-20T13:40:07+00:00

Enable the VGIC operation by properly initialising the registers
in the hypervisor GIC interface.

Signed-off-by: Eric Auger 
Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall

KVM: arm/arm64: vgic-new: vgic_init: implement map_resources

2016-05-20T13:40:07+00:00

map_resources is the last initialization step. It is executed on
first VCPU run. At that stage the code checks that userspace has provided
the base addresses for the relevant VGIC regions, which depend on the
type of VGIC that is exposed to the guest.  Also we check if the two
regions overlap.
If the checks succeeded, we register the respective register frames with
the kvm_io_bus framework.

If we emulate a GICv2, the function also forces vgic_init execution if
it has not been executed yet. Also we map the virtual GIC CPU interface
onto the guest's CPU interface.

Signed-off-by: Eric Auger 
Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall

KVM: arm/arm64: vgic-new: vgic_init: implement vgic_init

2016-05-20T13:40:06+00:00

This patch allocates and initializes the data structures used
to model the vgic distributor and virtual cpu interfaces. At that
stage the number of IRQs and number of virtual CPUs is frozen.

Signed-off-by: Eric Auger 
Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall

KVM: arm/arm64: vgic-new: vgic_init: implement vgic_create

2016-05-20T13:40:06+00:00

This patch implements the vgic_creation function which is
called on CREATE_IRQCHIP VM IOCTL (v2 only) or KVM_CREATE_DEVICE

Signed-off-by: Eric Auger 
Signed-off-by: Andre Przywara 
Reviewed-by: Christoffer Dall