Re: Vexpress TC2 no longer booting on v4.12-rc1

On Fri, Jun 02, 2017 at 04:16:59PM -0600, Mathieu Poirier wrote: > Good afternoon Russell and friends, > > I noticed that my vexpress-TC2 platform stopped booting when moving to > kernel v4.12-rc1 (same with -rc2 and 3). The last time things worked > properly was on v4.11. I did a bisect

Re: [RFC 07/55] KVM: arm/arm64: Add virtual EL2 state emulation framework

On Fri, Jun 02, 2017 at 01:36:23PM -0400, Bandan Das wrote: > Christoffer Dall writes: > > > On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote: > >> Jintack Lim writes: > >> ... > >> > +/** > >> > + * kvm_arm_setup_shadow_state -- prepare

Re: [RFC 07/55] KVM: arm/arm64: Add virtual EL2 state emulation framework

Christoffer Dall writes: > On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote: >> Jintack Lim writes: >> ... >> > +/** >> > + * kvm_arm_setup_shadow_state -- prepare shadow state based on emulated >> > mode >> > + * @vcpu: The VCPU pointer >>

Re: [PATCH 08/10] KVM: arm/arm64: vgic: Handle unshared mapped interrupts

On Fri, Jun 02, 2017 at 03:10:23PM +0100, Marc Zyngier wrote: > On 02/06/17 14:33, Christoffer Dall wrote: > > On Wed, May 24, 2017 at 10:13:21PM +0200, Eric Auger wrote: > >> Virtual interrupts directly mapped to physical interrupts require > >> some special care. Their pending and active state

Re: [PATCH v2 00/25] arm64: KVM: Mediate access to GICv3 sysregs at EL2

On 06/02/2017 02:11 AM, Marc Zyngier wrote: On 01/06/17 22:00, David Daney wrote: On 06/01/2017 03:20 AM, Marc Zyngier wrote: Some systems have less than perfect GICv3 implementations, leading to all kind of ugly issues (guest hanging, host dying). In order to allow some level of diagnostic,

Re: [PATCH V17 02/11] ras: acpi/apei: cper: add support for generic data v3 structure

On Fri, May 19, 2017 at 02:32:04PM -0600, Tyler Baicar wrote: > The ACPI 6.1 spec adds a new revision of the generic error data > entry structure. Add support to handle the new structure as well > as properly verify and iterate through the generic data entries. > > Signed-off-by: Tyler Baicar

Re: [PATCH 08/10] KVM: arm/arm64: vgic: Handle unshared mapped interrupts

On 02/06/17 14:33, Christoffer Dall wrote: > On Wed, May 24, 2017 at 10:13:21PM +0200, Eric Auger wrote: >> Virtual interrupts directly mapped to physical interrupts require >> some special care. Their pending and active state must be observed >> at distributor level and not in the list register.

Re: [PATCH 08/10] KVM: arm/arm64: vgic: Handle unshared mapped interrupts

On Wed, May 24, 2017 at 10:13:21PM +0200, Eric Auger wrote: > Virtual interrupts directly mapped to physical interrupts require > some special care. Their pending and active state must be observed > at distributor level and not in the list register. This is not entirely true. There's a

Re: [PATCH] arm64/kvm: fix misleading kconfig text for 16K pages

On Fri, Jun 02, 2017 at 12:02:20PM +0100, Mark Rutland wrote: > We've supported KVM with 16K pages since commit: > > 02e0b7600f835007 ("arm64: kvm: Add support for 16K pages") > > ... yet the kconfig text says this combination is not supported. > > Let's fix that by deleting the misleading

Re: [RFC 07/55] KVM: arm/arm64: Add virtual EL2 state emulation framework

On Thu, Jun 01, 2017 at 04:05:49PM -0400, Bandan Das wrote: > Jintack Lim writes: > ... > > +/** > > + * kvm_arm_setup_shadow_state -- prepare shadow state based on emulated > > mode > > + * @vcpu: The VCPU pointer > > + */ > > +void kvm_arm_setup_shadow_state(struct

Re: [PATCH] arm64/kvm: fix misleading kconfig text for 16K pages

On 02/06/17 12:02, Mark Rutland wrote: We've supported KVM with 16K pages since commit: 02e0b7600f835007 ("arm64: kvm: Add support for 16K pages") ... yet the kconfig text says this combination is not supported. Let's fix that by deleting the misleading text. Signed-off-by: Mark Rutland

[PATCH] arm64/kvm: fix misleading kconfig text for 16K pages

We've supported KVM with 16K pages since commit: 02e0b7600f835007 ("arm64: kvm: Add support for 16K pages") ... yet the kconfig text says this combination is not supported. Let's fix that by deleting the misleading text. Signed-off-by: Mark Rutland Acked-by: Marc

Re: [PATCH v2] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

On Fri, Jun 02, 2017 at 11:16:10AM +0100, James Morse wrote: > Hi Christoffer, > > On 01/06/17 23:22, Christoffer Dall wrote: > > On Wed, May 24, 2017 at 05:32:50PM +0100, James Morse wrote: > >> Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64, notifications for > >> broken memory can call

Re: [PATCH v2] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

Hi Christoffer, On 01/06/17 23:22, Christoffer Dall wrote: > On Wed, May 24, 2017 at 05:32:50PM +0100, James Morse wrote: >> Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64, notifications for >> broken memory can call memory_failure() in mm/memory-failure.c to deliver >> SIGBUS to any user

Re: [PATCH v2 00/25] arm64: KVM: Mediate access to GICv3 sysregs at EL2

On 01/06/17 22:00, David Daney wrote: > On 06/01/2017 03:20 AM, Marc Zyngier wrote: >> Some systems have less than perfect GICv3 implementations, leading to >> all kind of ugly issues (guest hanging, host dying). In order to allow >> some level of diagnostic, and in some cases implement

Re: [PATCH 05/10] VFIO: pci: Introduce direct EOI INTx interrupt handler

On 01/06/17 21:40, Auger Eric wrote: > Hi Alex, > > On 31/05/2017 20:24, Alex Williamson wrote: >> On Wed, 24 May 2017 22:13:18 +0200 >> Eric Auger wrote: >> >>> We add two new fields in vfio_pci_irq_ctx struct: deoi and handler. >>> If deoi is set, this means the physical