linux-toradex.git/arch/arm/kvm, branch master

arm: Remove 32bit KVM host support

2020-03-24T10:56:04+00:00

That's it. Remove all references to KVM itself, and document
that although it is no more, the ABI between SVC and HYP still
exists.

Signed-off-by: Marc Zyngier 
Acked-by: Olof Johansson 
Acked-by: Arnd Bergmann 
Acked-by: Will Deacon 
Acked-by: Vladimir Murzin 
Acked-by: Catalin Marinas 
Acked-by: Linus Walleij 
Acked-by: Christoffer Dall

KVM: Drop kvm_arch_vcpu_setup()

2020-01-27T18:59:28+00:00

Remove kvm_arch_vcpu_setup() now that all arch specific implementations
are nops.

Acked-by: Christoffer Dall 
Signed-off-by: Sean Christopherson 
Reviewed-by: Cornelia Huck 
Signed-off-by: Paolo Bonzini

Merge remote-tracking branch 'kvmarm/misc-5.5' into kvmarm/next

2019-11-08T11:27:29+00:00

KVM: arm/arm64: Show halt poll counters in debugfs

2019-10-28T13:52:50+00:00

ARM/ARM64 has counters halt_successful_poll, halt_attempted_poll,
halt_poll_invalid, and halt_wakeup but never exposed those in debugfs.

Signed-off-by: Christian Borntraeger 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/1572164390-5851-1-git-send-email-borntraeger@de.ibm.com

Merge remote-tracking branch 'kvmarm/kvm-arm64/stolen-time' into kvmarm-master/next

2019-10-24T14:04:09+00:00

KVM: arm/arm64: Factor out hypercall handling from PSCI code

2019-10-21T18:20:26+00:00

We currently intertwine the KVM PSCI implementation with the general
dispatch of hypercall handling, which makes perfect sense because PSCI
is the only category of hypercalls we support.

However, as we are about to support additional hypercalls, factor out
this functionality into a separate hypercall handler file.

Signed-off-by: Christoffer Dall 
[steven.price@arm.com: rebased]
Reviewed-by: Andrew Jones 
Signed-off-by: Steven Price 
Signed-off-by: Marc Zyngier

KVM: arm/arm64: Allow user injection of external data aborts

2019-10-21T17:59:51+00:00

In some scenarios, such as buggy guest or incorrect configuration of the
VMM and firmware description data, userspace will detect a memory access
to a portion of the IPA, which is not mapped to any MMIO region.

For this purpose, the appropriate action is to inject an external abort
to the guest.  The kernel already has functionality to inject an
external abort, but we need to wire up a signal from user space that
lets user space tell the kernel to do this.

It turns out, we already have the set event functionality which we can
perfectly reuse for this.

Signed-off-by: Christoffer Dall 
Signed-off-by: Marc Zyngier

kbuild: change *FLAGS_.o to take the path relative to $(obj)

2019-09-04T14:12:50+00:00

Kbuild provides per-file compiler flag addition/removal:

  CFLAGS_.o
  CFLAGS_REMOVE_.o
  AFLAGS_.o
  AFLAGS_REMOVE_.o
  CPPFLAGS_.lds
  HOSTCFLAGS_.o
  HOSTCXXFLAGS_.o

The  is the filename of the target with its directory and
suffix stripped.

This syntax comes into a trouble when two files with the same basename
appear in one Makefile, for example:

  obj-y += foo.o
  obj-y += dir/foo.o
  CFLAGS_foo.o := 

Here, the  applies to both foo.o and dir/foo.o

The real world problem is:

  scripts/kconfig/util.c
  scripts/kconfig/lxdialog/util.c

Both files are compiled into scripts/kconfig/mconf, but only the
latter should be given with the ncurses flags.

It is more sensible to use the relative path to the Makefile, like this:

  obj-y += foo.o
  CFLAGS_foo.o := 
  obj-y += dir/foo.o
  CFLAGS_dir/foo.o := 

At first, I attempted to replace $(basetarget) with $*. The $* variable
is replaced with the stem ('%') part in a pattern rule. This works with
most of cases, but does not for explicit rules.

For example, arch/ia64/lib/Makefile reuses rule_as_o_S in its own
explicit rules, so $* will be empty, resulting in ignoring the per-file
AFLAGS.

I introduced a new variable, target-stem, which can be used also from
explicit rules.

Signed-off-by: Masahiro Yamada 
Acked-by: Marc Zyngier

KVM: arm: Don't write junk to CP15 registers on reset

2019-08-09T07:07:24+00:00

At the moment, the way we reset CP15 registers is mildly insane:
We write junk to them, call the reset functions, and then check that
we have something else in them.

The "fun" thing is that this can happen while the guest is running
(PSCI, for example). If anything in KVM has to evaluate the state
of a CP15 register while junk is in there, bad thing may happen.

Let's stop doing that. Instead, we track that we have called a
reset function for that register, and assume that the reset
function has done something.

In the end, the very need of this reset check is pretty dubious,
as it doesn't check everything (a lot of the CP15 reg leave outside
of the cp15_regs[] array). It may well be axed in the near future.

Signed-off-by: Marc Zyngier

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 234

2019-06-19T15:09:07+00:00

Based on 1 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation this program is
  distributed in the hope that it will be useful but without any
  warranty without even the implied warranty of merchantability or
  fitness for a particular purpose see the gnu general public license
  for more details you should have received a copy of the gnu general
  public license along with this program if not see http www gnu org
  licenses

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 503 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Alexios Zavras 
Reviewed-by: Allison Randal 
Reviewed-by: Enrico Weigelt 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190602204653.811534538@linutronix.de
Signed-off-by: Greg Kroah-Hartman