[PATCH] fixup! kvm: arm debug: introduce helper for single-step

--- arch/arm/include/asm/kvm_host.h | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/arm/include/asm/kvm_host.h b/arch/arm/include/asm/kvm_host.h index a2e881d6108e..26a1ea6c6542 100644 --- a/arch/arm/include/asm/kvm_host.h +++ b/arch/arm/include/asm/kvm_host.h @@

Re: [PATCH v4 00/21] SError rework + RAS for firmware first support

Hi guys, On 19/10/17 15:57, James Morse wrote: > Known issues: [...] > * KVM-Migration: VDISR_EL2 is exposed to userspace as DISR_EL1, but how > should >HCR_EL2.VSE or VSESR_EL2 be migrated when the guest has an SError pending > but >hasn't taken it yet...? I've been trying to work

Re: [PATCH v5 13/30] arm64/sve: Core task context handling

Dave Martin writes: > On Thu, Nov 09, 2017 at 05:16:40PM +, Alex Bennée wrote: >> >> Dave Martin writes: >> >> > This patch adds the core support for switching and managing the SVE >> > architectural state of user tasks. >> > >> > Calls to the

Re: [PULL 00/26] KVM/ARM Changes for v4.15

2017-11-07 11:47+0100, Christoffer Dall: > Hi Paolo and Radim, > > Here is the first round of KVM/ARM Changes for v4.15. I will follow up > with a second pull request based on tip:irq/core containing the KVM/ARM > side of the GICv4 support. > > Changes in this pull requestinclude: > -

Re: [PATCH v5 13/30] arm64/sve: Core task context handling

On Thu, Nov 09, 2017 at 05:16:40PM +, Alex Bennée wrote: > > Dave Martin writes: > > > This patch adds the core support for switching and managing the SVE > > architectural state of user tasks. > > > > Calls to the existing FPSIMD low-level save/restore functions are >

Re: [PATCH v5 13/30] arm64/sve: Core task context handling

Dave Martin writes: > This patch adds the core support for switching and managing the SVE > architectural state of user tasks. > > Calls to the existing FPSIMD low-level save/restore functions are > factored out as new functions task_fpsimd_{save,load}(), since SVE > now

[PATCH v2 2/3] kvm: arm64: handle single-stepping trapped instructions

If we are using guest debug to single-step the guest we need to ensure we exit after emulating the instruction. This only affects instructions completely emulated by the kernel. For userspace emulated instructions we need to exit and return to complete the emulation. The

[PATCH v2 3/3] kvm: arm64: handle single-step of userspace mmio instructions

The system state of KVM when using userspace emulation is not complete until we return into KVM_RUN. To handle mmio related updates we wait until they have been committed and then schedule our KVM_EXIT_DEBUG. The kvm_arm_handle_step_debug() helper tells us if we need to return and sets up the

Re: [3/3] arm64: Add software workaround for Falkor erratum 1041

James, Looks like my VM test raised a false alarm. I retested stock Artful 4.13 kernel (No erratum 1041 patches applied). Host: Ubuntu Artful 4.13 kernel with *no* erratum 1041 patches applied. Guest: Ubuntu Zesty (4.10) kernel. - Created 20 VMs one at a time In a loop: - Stop (virsh

Re: [3/3] arm64: Add software workaround for Falkor erratum 1041

James, (sorry for top-posting) Applied patch 3 patches to Ubuntu Artful Kernel ( 4.13.0-16-generic ) - Start 20 VMs one at a time In a loop: - Stop (virsh destroy) 20 VMs one at a time - Start (virsh start) 20 VMs one at a time. The system reset's itself after starting the last VM on the

Re: [PATCH 3/3] arm64: Add software workaround for Falkor erratum 1041

Hi James, On 11/09/2017 05:08 AM, James Morse wrote: > Hi Shanker, Robin, > > On 04/11/17 21:43, Shanker Donthineni wrote: >> On 11/03/2017 10:11 AM, Robin Murphy wrote: >>> On 03/11/17 03:27, Shanker Donthineni wrote: The ARM architecture defines the memory locations that are permitted

Re: [PATCH 3/3] arm64: Add software workaround for Falkor erratum 1041

Hi Shanker, Robin, On 04/11/17 21:43, Shanker Donthineni wrote: > On 11/03/2017 10:11 AM, Robin Murphy wrote: >> On 03/11/17 03:27, Shanker Donthineni wrote: >>> The ARM architecture defines the memory locations that are permitted >>> to be accessed as the result of a speculative instruction

Re: [3/3] arm64: Add software workaround for Falkor erratum 1041

Hi Manoj, On 08/11/17 19:05, Manoj Iyer wrote: > On Thu, 2 Nov 2017, Shanker Donthineni wrote: >> The ARM architecture defines the memory locations that are permitted >> to be accessed as the result of a speculative instruction fetch from >> an exception level for which all stages of translation