Re: [PULL 00/29] KVM/ARM Changes for v4.7

Hi Itaru, Look at this commit that might be causing the problem. https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/firmware/efi/arm-runtime.c?id=14c43be60166981f0b1f034ad9c59252c6f99e0d Review your EFI system table and runtime service region attributes. On

Re: [PULL 00/29] KVM/ARM Changes for v4.7

Hi Itaru, I have tested kvmram patches (v4.6 and next-20160513) with ACPI/DTB firmware on Qualcomm platforms without any issue. Seems this problem could be related to memory region attributes and typethat contains runtime service code/data and EFI system table. Make sure EFI system table marked

Re: [PATCH v4 49/56] KVM: arm/arm64: vgic-new: vgic_init: implement kvm_vgic_hyp_init

Hi Andre, On 16/05/16 10:54, Andre Przywara wrote: + +/** + * vgic_v2_probe - probe for a GICv2 compatible interrupt controller in DT + * @node: pointer to the DT node This needs to be updated to match the parameters of vgic_v2_probe. + * + * Returns 0 if a GICv2 has been found,

Re: [PATCH v4 22/56] KVM: arm/arm64: vgic-new: Add MMIO handling framework

On 16/05/16 10:53, Andre Przywara wrote: > From: Marc Zyngier > > Add an MMIO handling framework to the VGIC emulation: > Each register is described by its offset, size (or number of bits per > IRQ, if applicable) and the read/write handler functions. We provide >

Re: [PATCH v4 18/56] KVM: arm/arm64: vgic-new: Add IRQ sync/flush framework

On 16/05/16 10:53, Andre Przywara wrote: > From: Marc Zyngier > > Implement the framework for syncing IRQs between our emulation and > the list registers, which represent the guest's view of IRQs. > This is done in kvm_vgic_flush_hwstate and kvm_vgic_sync_hwstate, > which

Re: [PULL 00/29] KVM/ARM Changes for v4.7

Hello, On 17/05/2016 00:28, Itaru Kitayama wrote: The new v4.6 upstream kernel gets to the prompt on Mustang (Rev A3). I would recommend you to bissect Linux and finger one or multiple commits which break booting on your board. Regards, -- Julien Grall