All of lore.kernel.org
 help / color / mirror / Atom feed
* KVM on ARM crashes with new VGIC v4.7-rc7
@ 2016-07-22  5:57 Stefan Agner
  2016-07-22  7:47 ` Marc Zyngier
                   ` (2 more replies)
  0 siblings, 3 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-22  5:57 UTC (permalink / raw)
  To: marc.zyngier, christoffer.dall; +Cc: kvmarm

Hi,

I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
this stack trace immediately after invoking qemu-system-arm:

Unable to handle kernel paging request at virtual address ffffffe4
pgd = 8ca52740
[ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
Internal error: Oops: 207 [#1] SMP ARM
Modules linked in:  
CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
4.7.0-rc7-00094-gea3ed2c #109
Hardware name: Freescale i.MX7 Dual (Device Tree)
task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
PC is at do_raw_spin_lock+0x8/0x1dc
LR is at kvm_vgic_flush_hwstate+0x8c/0x224
pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
fec 30be0000.ethernet eth0: MDIO read timeout
r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
Stack: (0x8d2b1e38 to 0x8d2b2000)
1e20:                                                       ffffffe0
00000000
1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
810074f8
1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
8ca5f800
1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
7ffbfeff
1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
ffffe000
1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
8023f248
1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
00000000
1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
00000000
1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
80bc2ec4
1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
007c1e70
1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
00000000
1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
00000036
1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
755feac0
1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
755fec6c
1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
00000000
[<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
(kvm_vgic_flush_hwstate+0x8c/0x224)
[<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
(kvm_arch_vcpu_ioctl_run+0x110/0x478)
[<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
(kvm_vcpu_ioctl+0x2e0/0x6d4)
[<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
(do_vfs_ioctl+0xa0/0x8b8)
[<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
[<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
---[ end trace cb88537fdc8fa206 ]---

I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
-nographic -serial stdio -kernel zImage).

Using a bit older Qemu version 2.4.0.

Is there something missing on my platform or is this a general KVM ARM
issue?

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  5:57 KVM on ARM crashes with new VGIC v4.7-rc7 Stefan Agner
@ 2016-07-22  7:47 ` Marc Zyngier
  2016-07-22  7:52   ` Auger Eric
  2016-07-22  8:10   ` Stefan Agner
  2016-07-22  9:15 ` Marc Zyngier
  2016-07-22 10:42 ` Andre Przywara
  2 siblings, 2 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22  7:47 UTC (permalink / raw)
  To: Stefan Agner, christoffer.dall; +Cc: kvmarm

Hi Stefan,

On 22/07/16 06:57, Stefan Agner wrote:
> Hi,
> 
> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> this stack trace immediately after invoking qemu-system-arm:
> 
> Unable to handle kernel paging request at virtual address ffffffe4
> pgd = 8ca52740
> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> Internal error: Oops: 207 [#1] SMP ARM
> Modules linked in:  
> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> 4.7.0-rc7-00094-gea3ed2c #109
> Hardware name: Freescale i.MX7 Dual (Device Tree)
> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> PC is at do_raw_spin_lock+0x8/0x1dc
> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> fec 30be0000.ethernet eth0: MDIO read timeout
> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> Stack: (0x8d2b1e38 to 0x8d2b2000)
> 1e20:                                                       ffffffe0
> 00000000
> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> 810074f8
> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> 8ca5f800
> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> 7ffbfeff
> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> ffffe000
> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> 8023f248
> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> 00000000
> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> 00000000
> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> 80bc2ec4
> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> 007c1e70
> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> 00000000
> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> 00000036
> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> 755feac0
> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> 755fec6c
> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> 00000000
> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> (kvm_vgic_flush_hwstate+0x8c/0x224)
> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> (do_vfs_ioctl+0xa0/0x8b8)
> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> ---[ end trace cb88537fdc8fa206 ]---
> 
> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> -nographic -serial stdio -kernel zImage).
> 
> Using a bit older Qemu version 2.4.0.
> 
> Is there something missing on my platform or is this a general KVM ARM
> issue?

This looks like a genuine bug, and I suspect this is triggered by having
an older QEMU that predates the explicit vgic init, hence relying on the
"init at first run". But in the meantime, could you dump me the bit of
kernel log that shows the KVM initialization, just in case I spot
something odd there?

I'll try and dig a QEMU of that particular vintage to reproduce it.

Thanks for the heads up!

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  7:47 ` Marc Zyngier
@ 2016-07-22  7:52   ` Auger Eric
  2016-07-22  7:59     ` Marc Zyngier
  2016-07-22  8:10   ` Stefan Agner
  1 sibling, 1 reply; 45+ messages in thread
From: Auger Eric @ 2016-07-22  7:52 UTC (permalink / raw)
  To: Marc Zyngier, Stefan Agner, christoffer.dall; +Cc: kvmarm

Hi Marc,

On 22/07/2016 09:47, Marc Zyngier wrote:
> Hi Stefan,
> 
> On 22/07/16 06:57, Stefan Agner wrote:
>> Hi,
>>
>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> this stack trace immediately after invoking qemu-system-arm:
>>
>> Unable to handle kernel paging request at virtual address ffffffe4
>> pgd = 8ca52740
>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> Internal error: Oops: 207 [#1] SMP ARM
>> Modules linked in:  
>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>> 4.7.0-rc7-00094-gea3ed2c #109
>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> PC is at do_raw_spin_lock+0x8/0x1dc
>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> fec 30be0000.ethernet eth0: MDIO read timeout
>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> 1e20:                                                       ffffffe0
>> 00000000
>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> 810074f8
>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> 8ca5f800
>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> 7ffbfeff
>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> ffffe000
>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> 8023f248
>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> 00000000
>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> 00000000
>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> 80bc2ec4
>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> 007c1e70
>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> 00000000
>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> 00000036
>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> 755feac0
>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> 755fec6c
>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> 00000000
>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> (do_vfs_ioctl+0xa0/0x8b8)
>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> ---[ end trace cb88537fdc8fa206 ]---
>>
>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> -nographic -serial stdio -kernel zImage).
>>
>> Using a bit older Qemu version 2.4.0.
>>
>> Is there something missing on my platform or is this a general KVM ARM
>> issue?
> 
> This looks like a genuine bug, and I suspect this is triggered by having
> an older QEMU that predates the explicit vgic init, hence relying on the
> "init at first run". But in the meantime, could you dump me the bit of
> kernel log that shows the KVM initialization, just in case I spot
> something odd there?
Had the same idea but QEMU v2.4.0 has the commit:

hw/intc/arm_gic: Initialize the vgic in the realize function
(f0bb55890a173cb1e9e87d608647cac70f8f9dd4)

Eric
> 
> I'll try and dig a QEMU of that particular vintage to reproduce it.
> 
> Thanks for the heads up!
> 
> 	M.
> 

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  7:52   ` Auger Eric
@ 2016-07-22  7:59     ` Marc Zyngier
  0 siblings, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22  7:59 UTC (permalink / raw)
  To: Auger Eric, Stefan Agner, christoffer.dall; +Cc: kvmarm

On 22/07/16 08:52, Auger Eric wrote:
> Hi Marc,
> 
> On 22/07/2016 09:47, Marc Zyngier wrote:
>> Hi Stefan,
>>
>> On 22/07/16 06:57, Stefan Agner wrote:
>>> Hi,
>>>
>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>> this stack trace immediately after invoking qemu-system-arm:
>>>
>>> Unable to handle kernel paging request at virtual address ffffffe4
>>> pgd = 8ca52740
>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>> Internal error: Oops: 207 [#1] SMP ARM
>>> Modules linked in:  
>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>> 4.7.0-rc7-00094-gea3ed2c #109
>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>> 1e20:                                                       ffffffe0
>>> 00000000
>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>> 810074f8
>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>> 8ca5f800
>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>> 7ffbfeff
>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>> ffffe000
>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>> 8023f248
>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>> 00000000
>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>> 00000000
>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>> 80bc2ec4
>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>> 007c1e70
>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>> 00000000
>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>> 00000036
>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>> 755feac0
>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>> 755fec6c
>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>> 00000000
>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>> (do_vfs_ioctl+0xa0/0x8b8)
>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>> ---[ end trace cb88537fdc8fa206 ]---
>>>
>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>> -nographic -serial stdio -kernel zImage).
>>>
>>> Using a bit older Qemu version 2.4.0.
>>>
>>> Is there something missing on my platform or is this a general KVM ARM
>>> issue?
>>
>> This looks like a genuine bug, and I suspect this is triggered by having
>> an older QEMU that predates the explicit vgic init, hence relying on the
>> "init at first run". But in the meantime, could you dump me the bit of
>> kernel log that shows the KVM initialization, just in case I spot
>> something odd there?
> Had the same idea but QEMU v2.4.0 has the commit:
> 
> hw/intc/arm_gic: Initialize the vgic in the realize function
> (f0bb55890a173cb1e9e87d608647cac70f8f9dd4)

Fair enough. I'm (slowly) rebuilding a v2.4.0 QEMU on my A7 board, and
hopefully I'll be able to reproduce this sucker.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  7:47 ` Marc Zyngier
  2016-07-22  7:52   ` Auger Eric
@ 2016-07-22  8:10   ` Stefan Agner
  1 sibling, 0 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-22  8:10 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: kvmarm

Hi Marc,

On 2016-07-22 00:47, Marc Zyngier wrote:
> Hi Stefan,
> 
> On 22/07/16 06:57, Stefan Agner wrote:
>> Hi,
>>
>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> this stack trace immediately after invoking qemu-system-arm:
>>
>> Unable to handle kernel paging request at virtual address ffffffe4
>> pgd = 8ca52740
>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> Internal error: Oops: 207 [#1] SMP ARM
>> Modules linked in:
>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> 4.7.0-rc7-00094-gea3ed2c #109
>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> PC is at do_raw_spin_lock+0x8/0x1dc
>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> fec 30be0000.ethernet eth0: MDIO read timeout
>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> 1e20:                                                       ffffffe0
>> 00000000
>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> 810074f8
>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> 8ca5f800
>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> 7ffbfeff
>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> ffffe000
>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> 8023f248
>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> 00000000
>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> 00000000
>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> 80bc2ec4
>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> 007c1e70
>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> 00000000
>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> 00000036
>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> 755feac0
>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> 755fec6c
>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> 00000000
>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> (do_vfs_ioctl+0xa0/0x8b8)
>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> ---[ end trace cb88537fdc8fa206 ]---
>>
>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> -nographic -serial stdio -kernel zImage).
>>
>> Using a bit older Qemu version 2.4.0.
>>
>> Is there something missing on my platform or is this a general KVM ARM
>> issue?
> 
> This looks like a genuine bug, and I suspect this is triggered by having
> an older QEMU that predates the explicit vgic init, hence relying on the
> "init at first run". But in the meantime, could you dump me the bit of
> kernel log that shows the KVM initialization, just in case I spot
> something odd there?

# dmesg | grep -C 2 kvm      
[    0.303848] RPC: Registered tcp transport module.
[    0.303880] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.307238] kvm [1]: 8-bit VMID
[    0.307273] kvm [1]: Hyp mode initialized successfully
[    0.307713] kvm [1]: virtual timer IRQ18
[    0.312511] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.315230] workingset: timestamp_bits=28 max_order=17 bucket_order=0

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  5:57 KVM on ARM crashes with new VGIC v4.7-rc7 Stefan Agner
  2016-07-22  7:47 ` Marc Zyngier
@ 2016-07-22  9:15 ` Marc Zyngier
  2016-07-22 10:42 ` Andre Przywara
  2 siblings, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22  9:15 UTC (permalink / raw)
  To: Stefan Agner, christoffer.dall; +Cc: kvmarm

On 22/07/16 06:57, Stefan Agner wrote:
> Hi,
> 
> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> this stack trace immediately after invoking qemu-system-arm:
> 
> Unable to handle kernel paging request at virtual address ffffffe4
> pgd = 8ca52740
> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> Internal error: Oops: 207 [#1] SMP ARM
> Modules linked in:  
> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> 4.7.0-rc7-00094-gea3ed2c #109
> Hardware name: Freescale i.MX7 Dual (Device Tree)
> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> PC is at do_raw_spin_lock+0x8/0x1dc
> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> fec 30be0000.ethernet eth0: MDIO read timeout
> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> Stack: (0x8d2b1e38 to 0x8d2b2000)
> 1e20:                                                       ffffffe0
> 00000000
> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> 810074f8
> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> 8ca5f800
> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> 7ffbfeff
> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> ffffe000
> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> 8023f248
> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> 00000000
> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> 00000000
> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> 80bc2ec4
> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> 007c1e70
> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> 00000000
> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> 00000036
> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> 755feac0
> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> 755fec6c
> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> 00000000
> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> (kvm_vgic_flush_hwstate+0x8c/0x224)
> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> (do_vfs_ioctl+0xa0/0x8b8)
> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> ---[ end trace cb88537fdc8fa206 ]---
> 
> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> -nographic -serial stdio -kernel zImage).
> 
> Using a bit older Qemu version 2.4.0.
> 
> Is there something missing on my platform or is this a general KVM ARM
> issue?

Having compiled a 2.4.0 vintage QEMU, everything seems fine, and the
guest comes up:

maz@big-leg-emma:~$ ./qemu/build/arm-softmmu/qemu-system-arm -enable-kvm -M virt -m 512 -cpu host -nographic -serial mon:stdio -kernel /boot/zImage-test

(process:2867): GLib-WARNING **: /build/glib2.0-Ero3uS/glib2.0-2.48.0/./glib/gmem.c:483: custom memory allocation vtable not supported
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.7.0-rc7 (maz@approximate) (gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11) ) #6281 SMP PREEMPT Fri Jul 22 10:01:56 BST 2016
[    0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=30c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: linux,dummy-virt
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Forcing write-allocate cache policy for SMP
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv0.2 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] percpu: Embedded 14 pages/cpu @cfde4000 s27456 r8192 d21696 u57344
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

So something is amiss somewhere else. Are you sure about the qemu
version? Built from source or packaged by a distro?

Could you send me your config? Also, can you put some traces in 
kvm_vgic_dist_init and kvm_vgic_vcpu_init, and see if they are
getting called?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22  5:57 KVM on ARM crashes with new VGIC v4.7-rc7 Stefan Agner
  2016-07-22  7:47 ` Marc Zyngier
  2016-07-22  9:15 ` Marc Zyngier
@ 2016-07-22 10:42 ` Andre Przywara
  2016-07-22 14:35   ` Andrew Jones
  2 siblings, 1 reply; 45+ messages in thread
From: Andre Przywara @ 2016-07-22 10:42 UTC (permalink / raw)
  To: Stefan Agner, marc.zyngier, christoffer.dall; +Cc: kvmarm

Hi Stefan,

On 22/07/16 06:57, Stefan Agner wrote:
> Hi,
> 
> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> this stack trace immediately after invoking qemu-system-arm:
> 
> Unable to handle kernel paging request at virtual address ffffffe4
> pgd = 8ca52740
> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> Internal error: Oops: 207 [#1] SMP ARM
> Modules linked in:  
> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> 4.7.0-rc7-00094-gea3ed2c #109
> Hardware name: Freescale i.MX7 Dual (Device Tree)
> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> PC is at do_raw_spin_lock+0x8/0x1dc
> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> fec 30be0000.ethernet eth0: MDIO read timeout
> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> Stack: (0x8d2b1e38 to 0x8d2b2000)
> 1e20:                                                       ffffffe0
> 00000000
> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> 810074f8
> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> 8ca5f800
> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> 7ffbfeff
> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> ffffe000
> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> 8023f248
> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> 00000000
> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> 00000000
> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> 80bc2ec4
> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> 007c1e70
> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> 00000000
> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> 00000036
> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> 755feac0
> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> 755fec6c
> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> 00000000
> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> (kvm_vgic_flush_hwstate+0x8c/0x224)
> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> (do_vfs_ioctl+0xa0/0x8b8)
> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> ---[ end trace cb88537fdc8fa206 ]---
> 
> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> -nographic -serial stdio -kernel zImage).
> 
> Using a bit older Qemu version 2.4.0.

I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
on a Midway (Cortex-A15).

Can you try to disable the new VGIC, just to see if that's a regression?

Cheers,
Andre.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 10:42 ` Andre Przywara
@ 2016-07-22 14:35   ` Andrew Jones
  2016-07-22 15:40     ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Andrew Jones @ 2016-07-22 14:35 UTC (permalink / raw)
  To: Andre Przywara; +Cc: marc.zyngier, kvmarm

On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
> Hi Stefan,
> 
> On 22/07/16 06:57, Stefan Agner wrote:
> > Hi,
> > 
> > I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> > this stack trace immediately after invoking qemu-system-arm:
> > 
> > Unable to handle kernel paging request at virtual address ffffffe4
> > pgd = 8ca52740
> > [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> > Internal error: Oops: 207 [#1] SMP ARM
> > Modules linked in:  
> > CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> > 4.7.0-rc7-00094-gea3ed2c #109
> > Hardware name: Freescale i.MX7 Dual (Device Tree)
> > task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> > PC is at do_raw_spin_lock+0x8/0x1dc
> > LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> > pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> > sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> > r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> > fec 30be0000.ethernet eth0: MDIO read timeout
> > r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> > r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> > Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> > Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> > Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> > Stack: (0x8d2b1e38 to 0x8d2b2000)
> > 1e20:                                                       ffffffe0
> > 00000000
> > 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> > 810074f8
> > 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> > 8ca5f800
> > 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> > 7ffbfeff
> > 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> > ffffe000
> > 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> > 8023f248
> > 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> > 00000000
> > 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> > 00000000
> > 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> > 80bc2ec4
> > 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> > 007c1e70
> > 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> > 00000000
> > 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> > 00000036
> > 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> > 755feac0
> > 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> > 755fec6c
> > 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> > 00000000
> > [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> > (kvm_vgic_flush_hwstate+0x8c/0x224)
> > [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> > (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> > [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> > (kvm_vcpu_ioctl+0x2e0/0x6d4)
> > [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> > (do_vfs_ioctl+0xa0/0x8b8)
> > [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> > [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> > Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> > ---[ end trace cb88537fdc8fa206 ]---
> > 
> > I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> > qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> > -nographic -serial stdio -kernel zImage).
> > 
> > Using a bit older Qemu version 2.4.0.
> 
> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> on a Midway (Cortex-A15).

I can reproduce the issue with a latest QEMU build on AMD Seattle
(I haven't tried anywhere else yet)

> 
> Can you try to disable the new VGIC, just to see if that's a regression?

Disabling NEW_VGIC "fixes" guest boots.

I'm not using defconfig for my host kernel. I'll do a couple more
tests and provide a comparison of my config vs. a defconfig in
a few minutes.

drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 14:35   ` Andrew Jones
@ 2016-07-22 15:40     ` Marc Zyngier
  2016-07-22 15:42       ` Auger Eric
  2016-07-22 17:38       ` Andrew Jones
  0 siblings, 2 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22 15:40 UTC (permalink / raw)
  To: Andrew Jones, Andre Przywara; +Cc: kvmarm

On 22/07/16 15:35, Andrew Jones wrote:
> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> Hi Stefan,
>>
>> On 22/07/16 06:57, Stefan Agner wrote:
>>> Hi,
>>>
>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>> this stack trace immediately after invoking qemu-system-arm:
>>>
>>> Unable to handle kernel paging request at virtual address ffffffe4
>>> pgd = 8ca52740
>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>> Internal error: Oops: 207 [#1] SMP ARM
>>> Modules linked in:  
>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>> 4.7.0-rc7-00094-gea3ed2c #109
>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>> 1e20:                                                       ffffffe0
>>> 00000000
>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>> 810074f8
>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>> 8ca5f800
>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>> 7ffbfeff
>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>> ffffe000
>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>> 8023f248
>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>> 00000000
>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>> 00000000
>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>> 80bc2ec4
>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>> 007c1e70
>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>> 00000000
>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>> 00000036
>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>> 755feac0
>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>> 755fec6c
>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>> 00000000
>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>> (do_vfs_ioctl+0xa0/0x8b8)
>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>> ---[ end trace cb88537fdc8fa206 ]---
>>>
>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>> -nographic -serial stdio -kernel zImage).
>>>
>>> Using a bit older Qemu version 2.4.0.
>>
>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> on a Midway (Cortex-A15).
> 
> I can reproduce the issue with a latest QEMU build on AMD Seattle
> (I haven't tried anywhere else yet)
> 
>>
>> Can you try to disable the new VGIC, just to see if that's a regression?
> 
> Disabling NEW_VGIC "fixes" guest boots.
> 
> I'm not using defconfig for my host kernel. I'll do a couple more
> tests and provide a comparison of my config vs. a defconfig in
> a few minutes.

Damn. It is not failing for me, so it has to be a kernel config thing...
If you can narrow it down to the difference with defconfig, that'd be
tremendously helpful.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 15:40     ` Marc Zyngier
@ 2016-07-22 15:42       ` Auger Eric
  2016-07-22 17:38       ` Andrew Jones
  1 sibling, 0 replies; 45+ messages in thread
From: Auger Eric @ 2016-07-22 15:42 UTC (permalink / raw)
  To: Marc Zyngier, Andrew Jones, Andre Przywara; +Cc: kvmarm

Hi,

On 22/07/2016 17:40, Marc Zyngier wrote:
> On 22/07/16 15:35, Andrew Jones wrote:
>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>> Hi Stefan,
>>>
>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>> Hi,
>>>>
>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>
>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>> pgd = 8ca52740
>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>> Modules linked in:  
>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>> 1e20:                                                       ffffffe0
>>>> 00000000
>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>> 810074f8
>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>> 8ca5f800
>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>> 7ffbfeff
>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>> ffffe000
>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>> 8023f248
>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>> 00000000
>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>> 00000000
>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>> 80bc2ec4
>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>> 007c1e70
>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>> 00000000
>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>> 00000036
>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>> 755feac0
>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>> 755fec6c
>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>> 00000000
>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>
>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>> -nographic -serial stdio -kernel zImage).
>>>>
>>>> Using a bit older Qemu version 2.4.0.
>>>
>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>> on a Midway (Cortex-A15).
>>
>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>> (I haven't tried anywhere else yet)
>>
>>>
>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>
>> Disabling NEW_VGIC "fixes" guest boots.
>>
>> I'm not using defconfig for my host kernel. I'll do a couple more
>> tests and provide a comparison of my config vs. a defconfig in
>> a few minutes.
> 
> Damn. It is not failing for me, so it has to be a kernel config thing...
> If you can narrow it down to the difference with defconfig, that'd be
> tremendously helpful.
Yes I confirm I also use a defconfig based 4.7-rc7 host and I tried qemu
2.4.0 and latest and I can't reproduce either (AMD Overdrive).

Eric
> 
> Thanks,
> 
> 	M.
> 

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 15:40     ` Marc Zyngier
  2016-07-22 15:42       ` Auger Eric
@ 2016-07-22 17:38       ` Andrew Jones
  2016-07-22 17:47         ` Stefan Agner
                           ` (2 more replies)
  1 sibling, 3 replies; 45+ messages in thread
From: Andrew Jones @ 2016-07-22 17:38 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
> On 22/07/16 15:35, Andrew Jones wrote:
> > On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
> >> Hi Stefan,
> >>
> >> On 22/07/16 06:57, Stefan Agner wrote:
> >>> Hi,
> >>>
> >>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >>> this stack trace immediately after invoking qemu-system-arm:
> >>>
> >>> Unable to handle kernel paging request at virtual address ffffffe4
> >>> pgd = 8ca52740
> >>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >>> Internal error: Oops: 207 [#1] SMP ARM
> >>> Modules linked in:  
> >>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> >>> 4.7.0-rc7-00094-gea3ed2c #109
> >>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >>> PC is at do_raw_spin_lock+0x8/0x1dc
> >>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >>> fec 30be0000.ethernet eth0: MDIO read timeout
> >>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >>> 1e20:                                                       ffffffe0
> >>> 00000000
> >>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >>> 810074f8
> >>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >>> 8ca5f800
> >>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >>> 7ffbfeff
> >>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >>> ffffe000
> >>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >>> 8023f248
> >>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >>> 00000000
> >>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >>> 00000000
> >>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >>> 80bc2ec4
> >>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >>> 007c1e70
> >>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >>> 00000000
> >>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >>> 00000036
> >>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >>> 755feac0
> >>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >>> 755fec6c
> >>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >>> 00000000
> >>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >>> (do_vfs_ioctl+0xa0/0x8b8)
> >>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >>> ---[ end trace cb88537fdc8fa206 ]---
> >>>
> >>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >>> -nographic -serial stdio -kernel zImage).
> >>>
> >>> Using a bit older Qemu version 2.4.0.
> >>
> >> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >> on a Midway (Cortex-A15).
> > 
> > I can reproduce the issue with a latest QEMU build on AMD Seattle
> > (I haven't tried anywhere else yet)
> > 
> >>
> >> Can you try to disable the new VGIC, just to see if that's a regression?
> > 
> > Disabling NEW_VGIC "fixes" guest boots.
> > 
> > I'm not using defconfig for my host kernel. I'll do a couple more
> > tests and provide a comparison of my config vs. a defconfig in
> > a few minutes.
> 
> Damn. It is not failing for me, so it has to be a kernel config thing...
> If you can narrow it down to the difference with defconfig, that'd be
> tremendously helpful.

It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
selection.

Thanks,
drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:38       ` Andrew Jones
@ 2016-07-22 17:47         ` Stefan Agner
  2016-07-22 17:49         ` Marc Zyngier
  2016-07-22 18:06         ` Marc Zyngier
  2 siblings, 0 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-22 17:47 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Marc Zyngier, Andre Przywara, kvmarm

On 2016-07-22 10:38, Andrew Jones wrote:
> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> On 22/07/16 15:35, Andrew Jones wrote:
>> > On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> >> Hi Stefan,
>> >>
>> >> On 22/07/16 06:57, Stefan Agner wrote:
>> >>> Hi,
>> >>>
>> >>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> >>> this stack trace immediately after invoking qemu-system-arm:
>> >>>
>> >>> Unable to handle kernel paging request at virtual address ffffffe4
>> >>> pgd = 8ca52740
>> >>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> >>> Internal error: Oops: 207 [#1] SMP ARM
>> >>> Modules linked in:
>> >>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> >>> 4.7.0-rc7-00094-gea3ed2c #109
>> >>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> >>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> >>> PC is at do_raw_spin_lock+0x8/0x1dc
>> >>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> >>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> >>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> >>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> >>> fec 30be0000.ethernet eth0: MDIO read timeout
>> >>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> >>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> >>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> >>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> >>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> >>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> >>> 1e20:                                                       ffffffe0
>> >>> 00000000
>> >>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> >>> 810074f8
>> >>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> >>> 8ca5f800
>> >>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> >>> 7ffbfeff
>> >>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> >>> ffffe000
>> >>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> >>> 8023f248
>> >>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> >>> 00000000
>> >>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> >>> 00000000
>> >>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> >>> 80bc2ec4
>> >>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> >>> 007c1e70
>> >>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> >>> 00000000
>> >>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> >>> 00000036
>> >>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> >>> 755feac0
>> >>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> >>> 755fec6c
>> >>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> >>> 00000000
>> >>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> >>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> >>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> >>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> >>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> >>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> >>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> >>> (do_vfs_ioctl+0xa0/0x8b8)
>> >>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> >>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> >>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> >>> ---[ end trace cb88537fdc8fa206 ]---
>> >>>
>> >>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> >>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> >>> -nographic -serial stdio -kernel zImage).
>> >>>
>> >>> Using a bit older Qemu version 2.4.0.
>> >>
>> >> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> >> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> >> on a Midway (Cortex-A15).
>> >
>> > I can reproduce the issue with a latest QEMU build on AMD Seattle
>> > (I haven't tried anywhere else yet)
>> >
>> >>
>> >> Can you try to disable the new VGIC, just to see if that's a regression?
>> >
>> > Disabling NEW_VGIC "fixes" guest boots.

Same for me.

>> >
>> > I'm not using defconfig for my host kernel. I'll do a couple more
>> > tests and provide a comparison of my config vs. a defconfig in
>> > a few minutes.
>>
>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> If you can narrow it down to the difference with defconfig, that'd be
>> tremendously helpful.
> 
> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> selection.

Just built a mutli_v7_defconfig, fails for me too.

Isn't 32-bit ARM always using 4K pages?

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:38       ` Andrew Jones
  2016-07-22 17:47         ` Stefan Agner
@ 2016-07-22 17:49         ` Marc Zyngier
  2016-07-22 17:56           ` Stefan Agner
  2016-07-22 18:06         ` Marc Zyngier
  2 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22 17:49 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 22/07/16 18:38, Andrew Jones wrote:
> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> On 22/07/16 15:35, Andrew Jones wrote:
>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>> Hi Stefan,
>>>>
>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>> Hi,
>>>>>
>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>
>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>> pgd = 8ca52740
>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>> Modules linked in:  
>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>> 1e20:                                                       ffffffe0
>>>>> 00000000
>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>> 810074f8
>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>> 8ca5f800
>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>> 7ffbfeff
>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>> ffffe000
>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>> 8023f248
>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>> 00000000
>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>> 00000000
>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>> 80bc2ec4
>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>> 007c1e70
>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>> 00000000
>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>> 00000036
>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>> 755feac0
>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>> 755fec6c
>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>> 00000000
>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>
>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>> -nographic -serial stdio -kernel zImage).
>>>>>
>>>>> Using a bit older Qemu version 2.4.0.
>>>>
>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>> on a Midway (Cortex-A15).
>>>
>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>> (I haven't tried anywhere else yet)
>>>
>>>>
>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>
>>> Disabling NEW_VGIC "fixes" guest boots.
>>>
>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>> tests and provide a comparison of my config vs. a defconfig in
>>> a few minutes.
>>
>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> If you can narrow it down to the difference with defconfig, that'd be
>> tremendously helpful.
> 
> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> selection.

That definitely doesn't match Stefan's report (32bit only has 4k). I'll
give 64k a go in a minute (but I remember doing some 64k stuff a couple
of weeks ago and everything was OK).

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:49         ` Marc Zyngier
@ 2016-07-22 17:56           ` Stefan Agner
  2016-07-22 18:11             ` Marc Zyngier
  2016-07-24 12:22             ` Marc Zyngier
  0 siblings, 2 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-22 17:56 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-22 10:49, Marc Zyngier wrote:
> On 22/07/16 18:38, Andrew Jones wrote:
>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>> Hi Stefan,
>>>>>
>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>
>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>> pgd = 8ca52740
>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>> Modules linked in:
>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>> 1e20:                                                       ffffffe0
>>>>>> 00000000
>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>> 810074f8
>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>> 8ca5f800
>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>> 7ffbfeff
>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>> ffffe000
>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>> 8023f248
>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>> 00000000
>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>> 00000000
>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>> 80bc2ec4
>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>> 007c1e70
>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>> 00000000
>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>> 00000036
>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>> 755feac0
>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>> 755fec6c
>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>> 00000000
>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>
>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>
>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>
>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>> on a Midway (Cortex-A15).
>>>>
>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>> (I haven't tried anywhere else yet)
>>>>
>>>>>
>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>
>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>
>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>> tests and provide a comparison of my config vs. a defconfig in
>>>> a few minutes.
>>>
>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>> If you can narrow it down to the difference with defconfig, that'd be
>>> tremendously helpful.
>>
>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>> selection.
> 
> That definitely doesn't match Stefan's report (32bit only has 4k). I'll

Hehe, was just plowing through code and came to that conclusion, glad I
got that right :-)

What defconfig do you use? I could reproduce the issue also with
multi_v7_defconfig + ARM_LPAE + KVM.

Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
clock next to get to the bits and pieces required for my board...

That said, it works fine otherwise, and the stacktrace looks rather
platform independent...

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:38       ` Andrew Jones
  2016-07-22 17:47         ` Stefan Agner
  2016-07-22 17:49         ` Marc Zyngier
@ 2016-07-22 18:06         ` Marc Zyngier
  2016-07-22 19:45           ` Andrew Jones
  2 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22 18:06 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 22/07/16 18:38, Andrew Jones wrote:
> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> On 22/07/16 15:35, Andrew Jones wrote:
>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>> Hi Stefan,
>>>>
>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>> Hi,
>>>>>
>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>
>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>> pgd = 8ca52740
>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>> Modules linked in:  
>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>> 1e20:                                                       ffffffe0
>>>>> 00000000
>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>> 810074f8
>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>> 8ca5f800
>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>> 7ffbfeff
>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>> ffffe000
>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>> 8023f248
>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>> 00000000
>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>> 00000000
>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>> 80bc2ec4
>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>> 007c1e70
>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>> 00000000
>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>> 00000036
>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>> 755feac0
>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>> 755fec6c
>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>> 00000000
>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>
>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>> -nographic -serial stdio -kernel zImage).
>>>>>
>>>>> Using a bit older Qemu version 2.4.0.
>>>>
>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>> on a Midway (Cortex-A15).
>>>
>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>> (I haven't tried anywhere else yet)
>>>
>>>>
>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>
>>> Disabling NEW_VGIC "fixes" guest boots.
>>>
>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>> tests and provide a comparison of my config vs. a defconfig in
>>> a few minutes.
>>
>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> If you can narrow it down to the difference with defconfig, that'd be
>> tremendously helpful.
> 
> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> selection.

root@flakes:~# zgrep 64K /proc/config.gz
CONFIG_ARM64_64K_PAGES=y

VMs up and running. It is definitely something else, potentially
affected by the page size. This is going to be a fun weekend.

Thanks for having had a look!

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:56           ` Stefan Agner
@ 2016-07-22 18:11             ` Marc Zyngier
  2016-07-23  7:45               ` Stefan Agner
  2016-07-24 12:22             ` Marc Zyngier
  1 sibling, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22 18:11 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On 22/07/16 18:56, Stefan Agner wrote:
> On 2016-07-22 10:49, Marc Zyngier wrote:
>> On 22/07/16 18:38, Andrew Jones wrote:
>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>> Hi Stefan,
>>>>>>
>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>
>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>> pgd = 8ca52740
>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>> Modules linked in:
>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>> 1e20:                                                       ffffffe0
>>>>>>> 00000000
>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>> 810074f8
>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>> 8ca5f800
>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>> 7ffbfeff
>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>> ffffe000
>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>> 8023f248
>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>> 00000000
>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>> 00000000
>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>> 80bc2ec4
>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>> 007c1e70
>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>> 00000000
>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>> 00000036
>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>> 755feac0
>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>> 755fec6c
>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>> 00000000
>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>
>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>
>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>
>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>> on a Midway (Cortex-A15).
>>>>>
>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>> (I haven't tried anywhere else yet)
>>>>>
>>>>>>
>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>
>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>
>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>> a few minutes.
>>>>
>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>> tremendously helpful.
>>>
>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>> selection.
>>
>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
> 
> Hehe, was just plowing through code and came to that conclusion, glad I
> got that right :-)
> 
> What defconfig do you use? I could reproduce the issue also with
> multi_v7_defconfig + ARM_LPAE + KVM.

I have my own config file with the crap I need to make things work on
the various platforms I have around. If multi_v7_defconfig works on the
cubietruck, I'll give it a spin tomorrow. I need a beer now.

> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
> clock next to get to the bits and pieces required for my board...
> 
> That said, it works fine otherwise, and the stacktrace looks rather
> platform independent...

Yeah, and that's the worrying part.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 18:06         ` Marc Zyngier
@ 2016-07-22 19:45           ` Andrew Jones
  2016-07-22 19:54             ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Andrew Jones @ 2016-07-22 19:45 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Fri, Jul 22, 2016 at 07:06:36PM +0100, Marc Zyngier wrote:
> On 22/07/16 18:38, Andrew Jones wrote:
> > On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
> >> On 22/07/16 15:35, Andrew Jones wrote:
> >>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
> >>>> Hi Stefan,
> >>>>
> >>>> On 22/07/16 06:57, Stefan Agner wrote:
> >>>>> Hi,
> >>>>>
> >>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >>>>> this stack trace immediately after invoking qemu-system-arm:
> >>>>>
> >>>>> Unable to handle kernel paging request at virtual address ffffffe4
> >>>>> pgd = 8ca52740
> >>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >>>>> Internal error: Oops: 207 [#1] SMP ARM
> >>>>> Modules linked in:  
> >>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> >>>>> 4.7.0-rc7-00094-gea3ed2c #109
> >>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> >>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> >>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >>>>> 1e20:                                                       ffffffe0
> >>>>> 00000000
> >>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >>>>> 810074f8
> >>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >>>>> 8ca5f800
> >>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >>>>> 7ffbfeff
> >>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >>>>> ffffe000
> >>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >>>>> 8023f248
> >>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >>>>> 00000000
> >>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >>>>> 00000000
> >>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >>>>> 80bc2ec4
> >>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >>>>> 007c1e70
> >>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >>>>> 00000000
> >>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >>>>> 00000036
> >>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >>>>> 755feac0
> >>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >>>>> 755fec6c
> >>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >>>>> 00000000
> >>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >>>>> (do_vfs_ioctl+0xa0/0x8b8)
> >>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >>>>> ---[ end trace cb88537fdc8fa206 ]---
> >>>>>
> >>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >>>>> -nographic -serial stdio -kernel zImage).
> >>>>>
> >>>>> Using a bit older Qemu version 2.4.0.
> >>>>
> >>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >>>> on a Midway (Cortex-A15).
> >>>
> >>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> >>> (I haven't tried anywhere else yet)
> >>>
> >>>>
> >>>> Can you try to disable the new VGIC, just to see if that's a regression?
> >>>
> >>> Disabling NEW_VGIC "fixes" guest boots.
> >>>
> >>> I'm not using defconfig for my host kernel. I'll do a couple more
> >>> tests and provide a comparison of my config vs. a defconfig in
> >>> a few minutes.
> >>
> >> Damn. It is not failing for me, so it has to be a kernel config thing...
> >> If you can narrow it down to the difference with defconfig, that'd be
> >> tremendously helpful.
> > 
> > It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> > selection.
> 
> root@flakes:~# zgrep 64K /proc/config.gz
> CONFIG_ARM64_64K_PAGES=y
> 
> VMs up and running. It is definitely something else, potentially
> affected by the page size. This is going to be a fun weekend.
> 
> Thanks for having had a look!

Ah... I didn't even notice the 32-bit addresses above, only the

 PC is at do_raw_spin_lock+0x8/0x1dc
 LR is at kvm_vgic_flush_hwstate+0x8c/0x224

which matches the backtrace I get with a 64-bit guest. And I really
only change PAGE_SIZE between a host kernel that works and doesn't,
which does also change ARM64_CONT_SHIFT and PGTABLE_LEVELS, but
nothing else, as far as config goes...

I have more information now too, to help throw gas on the fire.

I've now built the same kernel, but with old-vgic and 64K pages. Guests
don't boot with that either. kvm-unit-tests tests pass, except for the
smp test. The secondary does nothing, the primary waits on it (wfe)
forever. Unit tests all pass and guests (even smp) boot with the same
kernel built with both new and old vgic, but with 4K pages.

I checked where the guest was when it wasn't booting. It's wfi in
cpu_do_idle. So now we have do_raw_spin_lock (wfe related), an wfe
related issue with kvm-unit-tests, and a wfi issue with guest boot.
This makes me think that this issue is not strictly new-vgic related,
but rather wfx (and somehow 64K pages) related.

Thanks,
drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 19:45           ` Andrew Jones
@ 2016-07-22 19:54             ` Marc Zyngier
  2016-07-25  9:00               ` Andrew Jones
  0 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-22 19:54 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On Fri, 22 Jul 2016 21:45:00 +0200
Andrew Jones <drjones@redhat.com> wrote:

> On Fri, Jul 22, 2016 at 07:06:36PM +0100, Marc Zyngier wrote:
> > On 22/07/16 18:38, Andrew Jones wrote:  
> > > On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> > >> On 22/07/16 15:35, Andrew Jones wrote:  
> > >>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> > >>>> Hi Stefan,
> > >>>>
> > >>>> On 22/07/16 06:57, Stefan Agner wrote:  
> > >>>>> Hi,
> > >>>>>
> > >>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> > >>>>> this stack trace immediately after invoking qemu-system-arm:
> > >>>>>
> > >>>>> Unable to handle kernel paging request at virtual address ffffffe4
> > >>>>> pgd = 8ca52740
> > >>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> > >>>>> Internal error: Oops: 207 [#1] SMP ARM
> > >>>>> Modules linked in:  
> > >>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> > >>>>> 4.7.0-rc7-00094-gea3ed2c #109
> > >>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> > >>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> > >>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> > >>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> > >>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> > >>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> > >>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> > >>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> > >>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> > >>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> > >>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> > >>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> > >>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> > >>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> > >>>>> 1e20:                                                       ffffffe0
> > >>>>> 00000000
> > >>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> > >>>>> 810074f8
> > >>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> > >>>>> 8ca5f800
> > >>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> > >>>>> 7ffbfeff
> > >>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> > >>>>> ffffe000
> > >>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> > >>>>> 8023f248
> > >>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> > >>>>> 00000000
> > >>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> > >>>>> 00000000
> > >>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> > >>>>> 80bc2ec4
> > >>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> > >>>>> 007c1e70
> > >>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> > >>>>> 00000000
> > >>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> > >>>>> 00000036
> > >>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> > >>>>> 755feac0
> > >>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> > >>>>> 755fec6c
> > >>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> > >>>>> 00000000
> > >>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> > >>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> > >>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> > >>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> > >>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> > >>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> > >>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> > >>>>> (do_vfs_ioctl+0xa0/0x8b8)
> > >>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> > >>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> > >>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> > >>>>> ---[ end trace cb88537fdc8fa206 ]---
> > >>>>>
> > >>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> > >>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> > >>>>> -nographic -serial stdio -kernel zImage).
> > >>>>>
> > >>>>> Using a bit older Qemu version 2.4.0.  
> > >>>>
> > >>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> > >>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> > >>>> on a Midway (Cortex-A15).  
> > >>>
> > >>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> > >>> (I haven't tried anywhere else yet)
> > >>>  
> > >>>>
> > >>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> > >>>
> > >>> Disabling NEW_VGIC "fixes" guest boots.
> > >>>
> > >>> I'm not using defconfig for my host kernel. I'll do a couple more
> > >>> tests and provide a comparison of my config vs. a defconfig in
> > >>> a few minutes.  
> > >>
> > >> Damn. It is not failing for me, so it has to be a kernel config thing...
> > >> If you can narrow it down to the difference with defconfig, that'd be
> > >> tremendously helpful.  
> > > 
> > > It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> > > selection.  
> > 
> > root@flakes:~# zgrep 64K /proc/config.gz
> > CONFIG_ARM64_64K_PAGES=y
> > 
> > VMs up and running. It is definitely something else, potentially
> > affected by the page size. This is going to be a fun weekend.
> > 
> > Thanks for having had a look!  
> 
> Ah... I didn't even notice the 32-bit addresses above, only the
> 
>  PC is at do_raw_spin_lock+0x8/0x1dc
>  LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> 
> which matches the backtrace I get with a 64-bit guest. And I really
> only change PAGE_SIZE between a host kernel that works and doesn't,
> which does also change ARM64_CONT_SHIFT and PGTABLE_LEVELS, but
> nothing else, as far as config goes...
> 
> I have more information now too, to help throw gas on the fire.
> 
> I've now built the same kernel, but with old-vgic and 64K pages. Guests
> don't boot with that either. kvm-unit-tests tests pass, except for the
> smp test. The secondary does nothing, the primary waits on it (wfe)
> forever. Unit tests all pass and guests (even smp) boot with the same
> kernel built with both new and old vgic, but with 4K pages.
> 
> I checked where the guest was when it wasn't booting. It's wfi in
> cpu_do_idle. So now we have do_raw_spin_lock (wfe related), an wfe
> related issue with kvm-unit-tests, and a wfi issue with guest boot.
> This makes me think that this issue is not strictly new-vgic related,
> but rather wfx (and somehow 64K pages) related.

The guest locked in WFI is quite typical of waiting for an interrupt to
be delivered (usually a timer). Being locked there tends to indicate
that we're not making progress on that front.

Would you, by any chance, be booting with ACPI? If so, could you dump
which addresses your GIC is reported at? I'll be able to compare that
with my Seattle on Monday.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 18:11             ` Marc Zyngier
@ 2016-07-23  7:45               ` Stefan Agner
  2016-07-23 10:20                 ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Stefan Agner @ 2016-07-23  7:45 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-22 11:11, Marc Zyngier wrote:
> On 22/07/16 18:56, Stefan Agner wrote:
>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>> Hi Stefan,
>>>>>>>
>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>
>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>> pgd = 8ca52740
>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>> Modules linked in:
>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>> 00000000
>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>> 810074f8
>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>> 8ca5f800
>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>> 7ffbfeff
>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>> ffffe000
>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>> 8023f248
>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>> 00000000
>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>> 00000000
>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>> 80bc2ec4
>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>> 007c1e70
>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>> 00000000
>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>> 00000036
>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>> 755feac0
>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>> 755fec6c
>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>> 00000000
>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>
>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>
>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>
>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>> on a Midway (Cortex-A15).
>>>>>>
>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>> (I haven't tried anywhere else yet)
>>>>>>
>>>>>>>
>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>
>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>
>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>> a few minutes.
>>>>>
>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>> tremendously helpful.
>>>>
>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>> selection.
>>>
>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>
>> Hehe, was just plowing through code and came to that conclusion, glad I
>> got that right :-)
>>
>> What defconfig do you use? I could reproduce the issue also with
>> multi_v7_defconfig + ARM_LPAE + KVM.
> 
> I have my own config file with the crap I need to make things work on
> the various platforms I have around. If multi_v7_defconfig works on the
> cubietruck, I'll give it a spin tomorrow. I need a beer now.
> 
>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>> clock next to get to the bits and pieces required for my board...
>>
>> That said, it works fine otherwise, and the stacktrace looks rather
>> platform independent...
> 
> Yeah, and that's the worrying part.


FWIW, I tried here with Qemu 2.6.0, same stack trace...

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-23  7:45               ` Stefan Agner
@ 2016-07-23 10:20                 ` Marc Zyngier
  2016-07-23 16:33                   ` Stefan Agner
  0 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-23 10:20 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On Sat, 23 Jul 2016 00:45:50 -0700
Stefan Agner <stefan@agner.ch> wrote:

> On 2016-07-22 11:11, Marc Zyngier wrote:
> > On 22/07/16 18:56, Stefan Agner wrote:  
> >> On 2016-07-22 10:49, Marc Zyngier wrote:  
> >>> On 22/07/16 18:38, Andrew Jones wrote:  
> >>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> >>>>> On 22/07/16 15:35, Andrew Jones wrote:  
> >>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> >>>>>>> Hi Stefan,
> >>>>>>>
> >>>>>>> On 22/07/16 06:57, Stefan Agner wrote:  
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >>>>>>>> this stack trace immediately after invoking qemu-system-arm:
> >>>>>>>>
> >>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
> >>>>>>>> pgd = 8ca52740
> >>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
> >>>>>>>> Modules linked in:
> >>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
> >>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
> >>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> >>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> >>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >>>>>>>> 1e20:                                                       ffffffe0
> >>>>>>>> 00000000
> >>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >>>>>>>> 810074f8
> >>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >>>>>>>> 8ca5f800
> >>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >>>>>>>> 7ffbfeff
> >>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >>>>>>>> ffffe000
> >>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >>>>>>>> 8023f248
> >>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >>>>>>>> 00000000
> >>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >>>>>>>> 00000000
> >>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >>>>>>>> 80bc2ec4
> >>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >>>>>>>> 007c1e70
> >>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >>>>>>>> 00000000
> >>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >>>>>>>> 00000036
> >>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >>>>>>>> 755feac0
> >>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >>>>>>>> 755fec6c
> >>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >>>>>>>> 00000000
> >>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
> >>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
> >>>>>>>>
> >>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >>>>>>>> -nographic -serial stdio -kernel zImage).
> >>>>>>>>
> >>>>>>>> Using a bit older Qemu version 2.4.0.  
> >>>>>>>
> >>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >>>>>>> on a Midway (Cortex-A15).  
> >>>>>>
> >>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> >>>>>> (I haven't tried anywhere else yet)
> >>>>>>  
> >>>>>>>
> >>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> >>>>>>
> >>>>>> Disabling NEW_VGIC "fixes" guest boots.
> >>>>>>
> >>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
> >>>>>> tests and provide a comparison of my config vs. a defconfig in
> >>>>>> a few minutes.  
> >>>>>
> >>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
> >>>>> If you can narrow it down to the difference with defconfig, that'd be
> >>>>> tremendously helpful.  
> >>>>
> >>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> >>>> selection.  
> >>>
> >>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll  
> >>
> >> Hehe, was just plowing through code and came to that conclusion, glad I
> >> got that right :-)
> >>
> >> What defconfig do you use? I could reproduce the issue also with
> >> multi_v7_defconfig + ARM_LPAE + KVM.  
> > 
> > I have my own config file with the crap I need to make things work on
> > the various platforms I have around. If multi_v7_defconfig works on the
> > cubietruck, I'll give it a spin tomorrow. I need a beer now.
> >   
> >> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
> >> clock next to get to the bits and pieces required for my board...
> >>
> >> That said, it works fine otherwise, and the stacktrace looks rather
> >> platform independent...  
> > 
> > Yeah, and that's the worrying part.  
> 
> 
> FWIW, I tried here with Qemu 2.6.0, same stack trace...

I don't think this is userspace related, specially given that Andrew
managed to trigger it on arm64 as well. I guess we're looking at
something that changes the layout of memory (page size in Drew's case),
and exposes another latent bug. I'll try to get multi_v7_defconfig
running on my CT later today, and hopefully the thing will explode.
Fingers crossed.

	M.
-- 
Jazz is not dead. It just smells funny.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-23 10:20                 ` Marc Zyngier
@ 2016-07-23 16:33                   ` Stefan Agner
  2016-07-24  9:30                     ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Stefan Agner @ 2016-07-23 16:33 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-23 03:20, Marc Zyngier wrote:
> On Sat, 23 Jul 2016 00:45:50 -0700
> Stefan Agner <stefan@agner.ch> wrote:
> 
>> On 2016-07-22 11:11, Marc Zyngier wrote:
>> > On 22/07/16 18:56, Stefan Agner wrote:
>> >> On 2016-07-22 10:49, Marc Zyngier wrote:
>> >>> On 22/07/16 18:38, Andrew Jones wrote:
>> >>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> >>>>> On 22/07/16 15:35, Andrew Jones wrote:
>> >>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> >>>>>>> Hi Stefan,
>> >>>>>>>
>> >>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>> >>>>>>>> Hi,
>> >>>>>>>>
>> >>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> >>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>> >>>>>>>>
>> >>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>> >>>>>>>> pgd = 8ca52740
>> >>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> >>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>> >>>>>>>> Modules linked in:
>> >>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> >>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>> >>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> >>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> >>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>> >>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> >>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> >>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> >>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> >>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>> >>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> >>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> >>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> >>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> >>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> >>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> >>>>>>>> 1e20:                                                       ffffffe0
>> >>>>>>>> 00000000
>> >>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> >>>>>>>> 810074f8
>> >>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> >>>>>>>> 8ca5f800
>> >>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> >>>>>>>> 7ffbfeff
>> >>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> >>>>>>>> ffffe000
>> >>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> >>>>>>>> 8023f248
>> >>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> >>>>>>>> 00000000
>> >>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> >>>>>>>> 00000000
>> >>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> >>>>>>>> 80bc2ec4
>> >>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> >>>>>>>> 007c1e70
>> >>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> >>>>>>>> 00000000
>> >>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> >>>>>>>> 00000036
>> >>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> >>>>>>>> 755feac0
>> >>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> >>>>>>>> 755fec6c
>> >>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> >>>>>>>> 00000000
>> >>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> >>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> >>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> >>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> >>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> >>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> >>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> >>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>> >>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> >>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> >>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> >>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>> >>>>>>>>
>> >>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> >>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> >>>>>>>> -nographic -serial stdio -kernel zImage).
>> >>>>>>>>
>> >>>>>>>> Using a bit older Qemu version 2.4.0.
>> >>>>>>>
>> >>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> >>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> >>>>>>> on a Midway (Cortex-A15).
>> >>>>>>
>> >>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>> >>>>>> (I haven't tried anywhere else yet)
>> >>>>>>
>> >>>>>>>
>> >>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>> >>>>>>
>> >>>>>> Disabling NEW_VGIC "fixes" guest boots.
>> >>>>>>
>> >>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>> >>>>>> tests and provide a comparison of my config vs. a defconfig in
>> >>>>>> a few minutes.
>> >>>>>
>> >>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> >>>>> If you can narrow it down to the difference with defconfig, that'd be
>> >>>>> tremendously helpful.
>> >>>>
>> >>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>> >>>> selection.
>> >>>
>> >>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>> >>
>> >> Hehe, was just plowing through code and came to that conclusion, glad I
>> >> got that right :-)
>> >>
>> >> What defconfig do you use? I could reproduce the issue also with
>> >> multi_v7_defconfig + ARM_LPAE + KVM.
>> >
>> > I have my own config file with the crap I need to make things work on
>> > the various platforms I have around. If multi_v7_defconfig works on the
>> > cubietruck, I'll give it a spin tomorrow. I need a beer now.
>> >
>> >> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>> >> clock next to get to the bits and pieces required for my board...
>> >>
>> >> That said, it works fine otherwise, and the stacktrace looks rather
>> >> platform independent...
>> >
>> > Yeah, and that's the worrying part.
>>
>>
>> FWIW, I tried here with Qemu 2.6.0, same stack trace...
> 
> I don't think this is userspace related, specially given that Andrew
> managed to trigger it on arm64 as well. I guess we're looking at
> something that changes the layout of memory (page size in Drew's case),
> and exposes another latent bug. I'll try to get multi_v7_defconfig
> running on my CT later today, and hopefully the thing will explode.
> Fingers crossed.
> 

I hit another issue, this time in the guest. At times, it seemed as if
qemu-system-arm freezed (no console output). I then enabled earlyprintk
for PL01X UART, and got this:

Architected timer frequency not available
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at kernel/time/clockevents.c:44
cev_delta2ns+0x114/0x128
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc7 #5
Hardware name: Generic DT based system
[<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
[<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
[<8030e734>] (dump_stack) from [<8011a718>] (__warn+0xe8/0x100)
[<8011a718>] (__warn) from [<8011a7e0>] (warn_slowpath_null+0x20/0x28)
[<8011a7e0>] (warn_slowpath_null) from [<8017503c>]
(cev_delta2ns+0x114/0x128)
[<8017503c>] (cev_delta2ns) from [<8017548c>]
(clockevents_config.part.2+0x4c/0x6c)
[<8017548c>] (clockevents_config.part.2) from [<801754cc>]
(clockevents_config_and_register+0x20/0x2c)
[<801754cc>] (clockevents_config_and_register) from [<80435d9c>]
(arch_timer_setup+0xd8/0x1b4)
[<80435d9c>] (arch_timer_setup) from [<8081c118>]
(arch_timer_of_init+0x2a0/0x2c8)
[<8081c118>] (arch_timer_of_init) from [<8081bb14>]
(clocksource_probe+0x54/0x90)
[<8081bb14>] (clocksource_probe) from [<80800b30>]
(start_kernel+0x240/0x378)
[<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
---[ end trace cb88537fdc8fa200 ]---
Architected cp15 timer(s) running at 0.00MHz (virt).
Division by zero in kernel.
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
Hardware name: Generic DT based system
[<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
[<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
[<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
[<8030c764>] (Ldiv0_64) from [<80172360>]
(clocks_calc_max_nsecs+0x24/0x78)
[<80172360>] (clocks_calc_max_nsecs) from [<801725d8>]
(__clocksource_update_freq_scale+0x224/0x2fc)
[<801725d8>] (__clocksource_update_freq_scale) from [<801726c4>]
(__clocksource_register_scale+0x14/0xa8)
[<801726c4>] (__clocksource_register_scale) from [<8081be20>]
(arch_timer_common_init+0x1d8/0x230)
[<8081be20>] (arch_timer_common_init) from [<8081c0dc>]
(arch_timer_of_init+0x264/0x2c8)
[<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
(clocksource_probe+0x54/0x90)
[<8081bb14>] (clocksource_probe) from [<80800b30>]
(start_kernel+0x240/0x378)
[<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x0,
max_idle_ns: 0 ns
Division by zero in kernel.
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
Hardware name: Generic DT based system
[<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
[<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
[<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
[<8030c764>] (Ldiv0_64) from [<80172288>]
(clocks_calc_mult_shift+0x11c/0x13c)
[<80172288>] (clocks_calc_mult_shift) from [<8080a388>]
(sched_clock_register+0x64/0x1d8)
[<8080a388>] (sched_clock_register) from [<8081be54>]
(arch_timer_common_init+0x20c/0x230)
[<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
(arch_timer_of_init+0x264/0x2c8)
[<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
(clocksource_probe+0x54/0x90)
[<8081bb14>] (clocksource_probe) from [<80800b30>]
(start_kernel+0x240/0x378)
[<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
Division by zero in kernel.
CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
Hardware name: Generic DT based system
[<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
[<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
[<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
[<8030c764>] (Ldiv0_64) from [<80172360>]
(clocks_calc_max_nsecs+0x24/0x78)
[<80172360>] (clocks_calc_max_nsecs) from [<8080a3cc>]
(sched_clock_register+0xa8/0x1d8)
[<8080a3cc>] (sched_clock_register) from [<8081be54>]
(arch_timer_common_init+0x20c/0x230)
[<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
(arch_timer_of_init+0x264/0x2c8)
[<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
(clocksource_probe+0x54/0x90)
[<8081bb14>] (clocksource_probe) from [<80800b30>]
(start_kernel+0x240/0x378)
[<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
sched_clock: 56 bits at 0 Hz, resolution 0ns, wraps every 0ns
Console: colour dummy device 80x30
Calibrating delay loop... 


When it works (which tends to be around every 5. try), then the clock of
the Architected timer seems to be correctly identified:
Architected cp15 timer(s) running at 8.00MHz (virt).

Host looks good:
# dmesg | grep Architected
[    0.000000] Architected cp15 timer(s) running at 8.00MHz (phys).

Afaict, U-Boot correctly initializes the timers frequency in
arch/arm/imx-common/syscounter.c.

The guest is using a vanilla v4.7-rc7 kernel. 

The host is running without CONFIG_KVM_NEW_VGIC.

Looks like some kind of race during initialization...? Related to the
new VGIC issue?

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-23 16:33                   ` Stefan Agner
@ 2016-07-24  9:30                     ` Marc Zyngier
  2016-07-25  6:28                       ` Stefan Agner
  0 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-24  9:30 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On Sat, 23 Jul 2016 09:33:54 -0700
Stefan Agner <stefan@agner.ch> wrote:

> On 2016-07-23 03:20, Marc Zyngier wrote:
> > On Sat, 23 Jul 2016 00:45:50 -0700
> > Stefan Agner <stefan@agner.ch> wrote:
> >   
> >> On 2016-07-22 11:11, Marc Zyngier wrote:  
> >> > On 22/07/16 18:56, Stefan Agner wrote:  
> >> >> On 2016-07-22 10:49, Marc Zyngier wrote:  
> >> >>> On 22/07/16 18:38, Andrew Jones wrote:  
> >> >>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> >> >>>>> On 22/07/16 15:35, Andrew Jones wrote:  
> >> >>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> >> >>>>>>> Hi Stefan,
> >> >>>>>>>
> >> >>>>>>> On 22/07/16 06:57, Stefan Agner wrote:  
> >> >>>>>>>> Hi,
> >> >>>>>>>>
> >> >>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >> >>>>>>>> this stack trace immediately after invoking qemu-system-arm:
> >> >>>>>>>>
> >> >>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
> >> >>>>>>>> pgd = 8ca52740
> >> >>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >> >>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
> >> >>>>>>>> Modules linked in:
> >> >>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
> >> >>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
> >> >>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >> >>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >> >>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> >> >>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >> >>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >> >>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >> >>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >> >>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> >> >>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >> >>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >> >>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >> >>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >> >>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >> >>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >> >>>>>>>> 1e20:                                                       ffffffe0
> >> >>>>>>>> 00000000
> >> >>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >> >>>>>>>> 810074f8
> >> >>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >> >>>>>>>> 8ca5f800
> >> >>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >> >>>>>>>> 7ffbfeff
> >> >>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >> >>>>>>>> ffffe000
> >> >>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >> >>>>>>>> 8023f248
> >> >>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >> >>>>>>>> 00000000
> >> >>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >> >>>>>>>> 00000000
> >> >>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >> >>>>>>>> 80bc2ec4
> >> >>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >> >>>>>>>> 007c1e70
> >> >>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >> >>>>>>>> 00000000
> >> >>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >> >>>>>>>> 00000036
> >> >>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >> >>>>>>>> 755feac0
> >> >>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >> >>>>>>>> 755fec6c
> >> >>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >> >>>>>>>> 00000000
> >> >>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >> >>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >> >>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >> >>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >> >>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >> >>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >> >>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >> >>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
> >> >>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >> >>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >> >>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >> >>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
> >> >>>>>>>>
> >> >>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >> >>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >> >>>>>>>> -nographic -serial stdio -kernel zImage).
> >> >>>>>>>>
> >> >>>>>>>> Using a bit older Qemu version 2.4.0.  
> >> >>>>>>>
> >> >>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >> >>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >> >>>>>>> on a Midway (Cortex-A15).  
> >> >>>>>>
> >> >>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> >> >>>>>> (I haven't tried anywhere else yet)
> >> >>>>>>  
> >> >>>>>>>
> >> >>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> >> >>>>>>
> >> >>>>>> Disabling NEW_VGIC "fixes" guest boots.
> >> >>>>>>
> >> >>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
> >> >>>>>> tests and provide a comparison of my config vs. a defconfig in
> >> >>>>>> a few minutes.  
> >> >>>>>
> >> >>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
> >> >>>>> If you can narrow it down to the difference with defconfig, that'd be
> >> >>>>> tremendously helpful.  
> >> >>>>
> >> >>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> >> >>>> selection.  
> >> >>>
> >> >>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll  
> >> >>
> >> >> Hehe, was just plowing through code and came to that conclusion, glad I
> >> >> got that right :-)
> >> >>
> >> >> What defconfig do you use? I could reproduce the issue also with
> >> >> multi_v7_defconfig + ARM_LPAE + KVM.  
> >> >
> >> > I have my own config file with the crap I need to make things work on
> >> > the various platforms I have around. If multi_v7_defconfig works on the
> >> > cubietruck, I'll give it a spin tomorrow. I need a beer now.
> >> >  
> >> >> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
> >> >> clock next to get to the bits and pieces required for my board...
> >> >>
> >> >> That said, it works fine otherwise, and the stacktrace looks rather
> >> >> platform independent...  
> >> >
> >> > Yeah, and that's the worrying part.  
> >>
> >>
> >> FWIW, I tried here with Qemu 2.6.0, same stack trace...  
> > 
> > I don't think this is userspace related, specially given that Andrew
> > managed to trigger it on arm64 as well. I guess we're looking at
> > something that changes the layout of memory (page size in Drew's case),
> > and exposes another latent bug. I'll try to get multi_v7_defconfig
> > running on my CT later today, and hopefully the thing will explode.
> > Fingers crossed.
> >   
> 
> I hit another issue, this time in the guest. At times, it seemed as if
> qemu-system-arm freezed (no console output). I then enabled earlyprintk
> for PL01X UART, and got this:
> 
> Architected timer frequency not available
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 0 at kernel/time/clockevents.c:44
> cev_delta2ns+0x114/0x128
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc7 #5
> Hardware name: Generic DT based system
> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
> [<8030e734>] (dump_stack) from [<8011a718>] (__warn+0xe8/0x100)
> [<8011a718>] (__warn) from [<8011a7e0>] (warn_slowpath_null+0x20/0x28)
> [<8011a7e0>] (warn_slowpath_null) from [<8017503c>]
> (cev_delta2ns+0x114/0x128)
> [<8017503c>] (cev_delta2ns) from [<8017548c>]
> (clockevents_config.part.2+0x4c/0x6c)
> [<8017548c>] (clockevents_config.part.2) from [<801754cc>]
> (clockevents_config_and_register+0x20/0x2c)
> [<801754cc>] (clockevents_config_and_register) from [<80435d9c>]
> (arch_timer_setup+0xd8/0x1b4)
> [<80435d9c>] (arch_timer_setup) from [<8081c118>]
> (arch_timer_of_init+0x2a0/0x2c8)
> [<8081c118>] (arch_timer_of_init) from [<8081bb14>]
> (clocksource_probe+0x54/0x90)
> [<8081bb14>] (clocksource_probe) from [<80800b30>]
> (start_kernel+0x240/0x378)
> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
> ---[ end trace cb88537fdc8fa200 ]---
> Architected cp15 timer(s) running at 0.00MHz (virt).
> Division by zero in kernel.
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
> Hardware name: Generic DT based system
> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
> [<8030c764>] (Ldiv0_64) from [<80172360>]
> (clocks_calc_max_nsecs+0x24/0x78)
> [<80172360>] (clocks_calc_max_nsecs) from [<801725d8>]
> (__clocksource_update_freq_scale+0x224/0x2fc)
> [<801725d8>] (__clocksource_update_freq_scale) from [<801726c4>]
> (__clocksource_register_scale+0x14/0xa8)
> [<801726c4>] (__clocksource_register_scale) from [<8081be20>]
> (arch_timer_common_init+0x1d8/0x230)
> [<8081be20>] (arch_timer_common_init) from [<8081c0dc>]
> (arch_timer_of_init+0x264/0x2c8)
> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
> (clocksource_probe+0x54/0x90)
> [<8081bb14>] (clocksource_probe) from [<80800b30>]
> (start_kernel+0x240/0x378)
> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
> clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x0,
> max_idle_ns: 0 ns
> Division by zero in kernel.
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
> Hardware name: Generic DT based system
> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
> [<8030c764>] (Ldiv0_64) from [<80172288>]
> (clocks_calc_mult_shift+0x11c/0x13c)
> [<80172288>] (clocks_calc_mult_shift) from [<8080a388>]
> (sched_clock_register+0x64/0x1d8)
> [<8080a388>] (sched_clock_register) from [<8081be54>]
> (arch_timer_common_init+0x20c/0x230)
> [<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
> (arch_timer_of_init+0x264/0x2c8)
> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
> (clocksource_probe+0x54/0x90)
> [<8081bb14>] (clocksource_probe) from [<80800b30>]
> (start_kernel+0x240/0x378)
> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
> Division by zero in kernel.
> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
> Hardware name: Generic DT based system
> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
> [<8030c764>] (Ldiv0_64) from [<80172360>]
> (clocks_calc_max_nsecs+0x24/0x78)
> [<80172360>] (clocks_calc_max_nsecs) from [<8080a3cc>]
> (sched_clock_register+0xa8/0x1d8)
> [<8080a3cc>] (sched_clock_register) from [<8081be54>]
> (arch_timer_common_init+0x20c/0x230)
> [<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
> (arch_timer_of_init+0x264/0x2c8)
> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
> (clocksource_probe+0x54/0x90)
> [<8081bb14>] (clocksource_probe) from [<80800b30>]
> (start_kernel+0x240/0x378)
> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
> sched_clock: 56 bits at 0 Hz, resolution 0ns, wraps every 0ns
> Console: colour dummy device 80x30
> Calibrating delay loop... 
> 
> 
> When it works (which tends to be around every 5. try), then the clock of
> the Architected timer seems to be correctly identified:
> Architected cp15 timer(s) running at 8.00MHz (virt).
> 
> Host looks good:
> # dmesg | grep Architected
> [    0.000000] Architected cp15 timer(s) running at 8.00MHz (phys).
> 
> Afaict, U-Boot correctly initializes the timers frequency in
> arch/arm/imx-common/syscounter.c.

It certainly does, but probably only on the boot CPU, whereas it should
be set on all CPUs (this is a per-CPU register). If your guest boots on
a secondary CPU, it will find zero as its CNTFRQ, and barf.

> 
> The guest is using a vanilla v4.7-rc7 kernel. 
> 
> The host is running without CONFIG_KVM_NEW_VGIC.
> 
> Looks like some kind of race during initialization...? Related to the
> new VGIC issue?

Completely unrelated. Clearly, u-boot is bogus on your system. This bit
of code:

http://git.denx.de/?p=u-boot.git;a=blob;f=arch/arm/cpu/armv7/nonsec_virt.S;h=95ce9387b83e972414b6de2d5711a9f40fe097df;hb=HEAD#l185

is what should be doing the job. It must be called on each CPU, before
switching to non-secure mode.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 17:56           ` Stefan Agner
  2016-07-22 18:11             ` Marc Zyngier
@ 2016-07-24 12:22             ` Marc Zyngier
  2016-07-24 12:36               ` Marc Zyngier
  1 sibling, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-24 12:22 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On Fri, 22 Jul 2016 10:56:44 -0700
Stefan Agner <stefan@agner.ch> wrote:

> On 2016-07-22 10:49, Marc Zyngier wrote:
> > On 22/07/16 18:38, Andrew Jones wrote:  
> >> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> >>> On 22/07/16 15:35, Andrew Jones wrote:  
> >>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> >>>>> Hi Stefan,
> >>>>>
> >>>>> On 22/07/16 06:57, Stefan Agner wrote:  
> >>>>>> Hi,
> >>>>>>
> >>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >>>>>> this stack trace immediately after invoking qemu-system-arm:
> >>>>>>
> >>>>>> Unable to handle kernel paging request at virtual address ffffffe4
> >>>>>> pgd = 8ca52740
> >>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >>>>>> Internal error: Oops: 207 [#1] SMP ARM
> >>>>>> Modules linked in:
> >>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
> >>>>>> 4.7.0-rc7-00094-gea3ed2c #109
> >>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> >>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> >>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >>>>>> 1e20:                                                       ffffffe0
> >>>>>> 00000000
> >>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >>>>>> 810074f8
> >>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >>>>>> 8ca5f800
> >>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >>>>>> 7ffbfeff
> >>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >>>>>> ffffe000
> >>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >>>>>> 8023f248
> >>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >>>>>> 00000000
> >>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >>>>>> 00000000
> >>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >>>>>> 80bc2ec4
> >>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >>>>>> 007c1e70
> >>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >>>>>> 00000000
> >>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >>>>>> 00000036
> >>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >>>>>> 755feac0
> >>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >>>>>> 755fec6c
> >>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >>>>>> 00000000
> >>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >>>>>> (do_vfs_ioctl+0xa0/0x8b8)
> >>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >>>>>> ---[ end trace cb88537fdc8fa206 ]---
> >>>>>>
> >>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >>>>>> -nographic -serial stdio -kernel zImage).
> >>>>>>
> >>>>>> Using a bit older Qemu version 2.4.0.  
> >>>>>
> >>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >>>>> on a Midway (Cortex-A15).  
> >>>>
> >>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> >>>> (I haven't tried anywhere else yet)
> >>>>  
> >>>>>
> >>>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> >>>>
> >>>> Disabling NEW_VGIC "fixes" guest boots.
> >>>>
> >>>> I'm not using defconfig for my host kernel. I'll do a couple more
> >>>> tests and provide a comparison of my config vs. a defconfig in
> >>>> a few minutes.  
> >>>
> >>> Damn. It is not failing for me, so it has to be a kernel config thing...
> >>> If you can narrow it down to the difference with defconfig, that'd be
> >>> tremendously helpful.  
> >>
> >> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> >> selection.  
> > 
> > That definitely doesn't match Stefan's report (32bit only has 4k). I'll  
> 
> Hehe, was just plowing through code and came to that conclusion, glad I
> got that right :-)
> 
> What defconfig do you use? I could reproduce the issue also with
> multi_v7_defconfig + ARM_LPAE + KVM.

I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
built-in to make my life simpler). The host works perfectly, and I can
spawn VMs without any issue.

I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
as packaged with Jessie from a while ago. I've also upgraded the box to
something more recent (2.5), same effect.

>
> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
> clock next to get to the bits and pieces required for my board...
> 
> That said, it works fine otherwise, and the stacktrace looks rather
> platform independent...

Indeed, and if these clocks were doing anything unsavoury, we'd
probably see other things exploding. So we need to find out where we
are diverging.

What compiler are you using? I just noticed that my build
infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
going to upgrade that to gcc 5.3 and retest.

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-24 12:22             ` Marc Zyngier
@ 2016-07-24 12:36               ` Marc Zyngier
  2016-07-25  6:14                 ` Stefan Agner
  2016-07-25  6:36                 ` Stefan Agner
  0 siblings, 2 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-24 12:36 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On Sun, 24 Jul 2016 13:22:55 +0100
Marc Zyngier <marc.zyngier@arm.com> wrote:

> On Fri, 22 Jul 2016 10:56:44 -0700
> Stefan Agner <stefan@agner.ch> wrote:
> 
> > On 2016-07-22 10:49, Marc Zyngier wrote:  
> > > On 22/07/16 18:38, Andrew Jones wrote:    
> > >> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:    
> > >>> On 22/07/16 15:35, Andrew Jones wrote:    
> > >>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:    
> > >>>>> Hi Stefan,
> > >>>>>
> > >>>>> On 22/07/16 06:57, Stefan Agner wrote:    
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> > >>>>>> this stack trace immediately after invoking qemu-system-arm:
> > >>>>>>
> > >>>>>> Unable to handle kernel paging request at virtual address ffffffe4
> > >>>>>> pgd = 8ca52740
> > >>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> > >>>>>> Internal error: Oops: 207 [#1] SMP ARM
> > >>>>>> Modules linked in:
> > >>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
> > >>>>>> 4.7.0-rc7-00094-gea3ed2c #109
> > >>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> > >>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> > >>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> > >>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> > >>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> > >>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> > >>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> > >>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> > >>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> > >>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> > >>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> > >>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> > >>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> > >>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> > >>>>>> 1e20:                                                       ffffffe0
> > >>>>>> 00000000
> > >>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> > >>>>>> 810074f8
> > >>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> > >>>>>> 8ca5f800
> > >>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> > >>>>>> 7ffbfeff
> > >>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> > >>>>>> ffffe000
> > >>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> > >>>>>> 8023f248
> > >>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> > >>>>>> 00000000
> > >>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> > >>>>>> 00000000
> > >>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> > >>>>>> 80bc2ec4
> > >>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> > >>>>>> 007c1e70
> > >>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> > >>>>>> 00000000
> > >>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> > >>>>>> 00000036
> > >>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> > >>>>>> 755feac0
> > >>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> > >>>>>> 755fec6c
> > >>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> > >>>>>> 00000000
> > >>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> > >>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> > >>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> > >>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> > >>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> > >>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> > >>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> > >>>>>> (do_vfs_ioctl+0xa0/0x8b8)
> > >>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> > >>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> > >>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> > >>>>>> ---[ end trace cb88537fdc8fa206 ]---
> > >>>>>>
> > >>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> > >>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> > >>>>>> -nographic -serial stdio -kernel zImage).
> > >>>>>>
> > >>>>>> Using a bit older Qemu version 2.4.0.    
> > >>>>>
> > >>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> > >>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> > >>>>> on a Midway (Cortex-A15).    
> > >>>>
> > >>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> > >>>> (I haven't tried anywhere else yet)
> > >>>>    
> > >>>>>
> > >>>>> Can you try to disable the new VGIC, just to see if that's a regression?    
> > >>>>
> > >>>> Disabling NEW_VGIC "fixes" guest boots.
> > >>>>
> > >>>> I'm not using defconfig for my host kernel. I'll do a couple more
> > >>>> tests and provide a comparison of my config vs. a defconfig in
> > >>>> a few minutes.    
> > >>>
> > >>> Damn. It is not failing for me, so it has to be a kernel config thing...
> > >>> If you can narrow it down to the difference with defconfig, that'd be
> > >>> tremendously helpful.    
> > >>
> > >> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> > >> selection.    
> > > 
> > > That definitely doesn't match Stefan's report (32bit only has 4k). I'll    
> > 
> > Hehe, was just plowing through code and came to that conclusion, glad I
> > got that right :-)
> > 
> > What defconfig do you use? I could reproduce the issue also with
> > multi_v7_defconfig + ARM_LPAE + KVM.  
> 
> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
> built-in to make my life simpler). The host works perfectly, and I can
> spawn VMs without any issue.
> 
> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
> as packaged with Jessie from a while ago. I've also upgraded the box to
> something more recent (2.5), same effect.
> 
> >
> > Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
> > clock next to get to the bits and pieces required for my board...
> > 
> > That said, it works fine otherwise, and the stacktrace looks rather
> > platform independent...  
> 
> Indeed, and if these clocks were doing anything unsavoury, we'd
> probably see other things exploding. So we need to find out where we
> are diverging.
> 
> What compiler are you using? I just noticed that my build
> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
> going to upgrade that to gcc 5.3 and retest.

Same thing. The damn thing stubbornly works.

Please send your full configuration, compiler version, exact QEMU
command line, and any other detail that could be vaguely relevant. As
the old VGIC gets removed in 4.8, we definitely need to nail that
sucker right now.

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-24 12:36               ` Marc Zyngier
@ 2016-07-25  6:14                 ` Stefan Agner
  2016-07-25  8:11                   ` Marc Zyngier
  2016-07-25  8:42                   ` Marc Zyngier
  2016-07-25  6:36                 ` Stefan Agner
  1 sibling, 2 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-25  6:14 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

[-- Attachment #1: Type: text/plain, Size: 7817 bytes --]

On 2016-07-24 05:36, Marc Zyngier wrote:
> On Sun, 24 Jul 2016 13:22:55 +0100
> Marc Zyngier <marc.zyngier@arm.com> wrote:
> 
>> On Fri, 22 Jul 2016 10:56:44 -0700
>> Stefan Agner <stefan@agner.ch> wrote:
>>
>> > On 2016-07-22 10:49, Marc Zyngier wrote:
>> > > On 22/07/16 18:38, Andrew Jones wrote:
>> > >> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> > >>> On 22/07/16 15:35, Andrew Jones wrote:
>> > >>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> > >>>>> Hi Stefan,
>> > >>>>>
>> > >>>>> On 22/07/16 06:57, Stefan Agner wrote:
>> > >>>>>> Hi,
>> > >>>>>>
>> > >>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> > >>>>>> this stack trace immediately after invoking qemu-system-arm:
>> > >>>>>>
>> > >>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>> > >>>>>> pgd = 8ca52740
>> > >>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> > >>>>>> Internal error: Oops: 207 [#1] SMP ARM
>> > >>>>>> Modules linked in:
>> > >>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> > >>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>> > >>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> > >>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> > >>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>> > >>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> > >>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> > >>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> > >>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> > >>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>> > >>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> > >>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> > >>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> > >>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> > >>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> > >>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> > >>>>>> 1e20:                                                       ffffffe0
>> > >>>>>> 00000000
>> > >>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> > >>>>>> 810074f8
>> > >>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> > >>>>>> 8ca5f800
>> > >>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> > >>>>>> 7ffbfeff
>> > >>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> > >>>>>> ffffe000
>> > >>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> > >>>>>> 8023f248
>> > >>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> > >>>>>> 00000000
>> > >>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> > >>>>>> 00000000
>> > >>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> > >>>>>> 80bc2ec4
>> > >>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> > >>>>>> 007c1e70
>> > >>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> > >>>>>> 00000000
>> > >>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> > >>>>>> 00000036
>> > >>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> > >>>>>> 755feac0
>> > >>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> > >>>>>> 755fec6c
>> > >>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> > >>>>>> 00000000
>> > >>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> > >>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> > >>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> > >>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> > >>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> > >>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> > >>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> > >>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>> > >>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> > >>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> > >>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> > >>>>>> ---[ end trace cb88537fdc8fa206 ]---
>> > >>>>>>
>> > >>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> > >>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> > >>>>>> -nographic -serial stdio -kernel zImage).
>> > >>>>>>
>> > >>>>>> Using a bit older Qemu version 2.4.0.
>> > >>>>>
>> > >>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> > >>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> > >>>>> on a Midway (Cortex-A15).
>> > >>>>
>> > >>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>> > >>>> (I haven't tried anywhere else yet)
>> > >>>>
>> > >>>>>
>> > >>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>> > >>>>
>> > >>>> Disabling NEW_VGIC "fixes" guest boots.
>> > >>>>
>> > >>>> I'm not using defconfig for my host kernel. I'll do a couple more
>> > >>>> tests and provide a comparison of my config vs. a defconfig in
>> > >>>> a few minutes.
>> > >>>
>> > >>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> > >>> If you can narrow it down to the difference with defconfig, that'd be
>> > >>> tremendously helpful.
>> > >>
>> > >> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>> > >> selection.
>> > >
>> > > That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>> >
>> > Hehe, was just plowing through code and came to that conclusion, glad I
>> > got that right :-)
>> >
>> > What defconfig do you use? I could reproduce the issue also with
>> > multi_v7_defconfig + ARM_LPAE + KVM.
>>
>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>> built-in to make my life simpler). The host works perfectly, and I can
>> spawn VMs without any issue.
>>
>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>> as packaged with Jessie from a while ago. I've also upgraded the box to
>> something more recent (2.5), same effect.
>>
>> >
>> > Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>> > clock next to get to the bits and pieces required for my board...
>> >
>> > That said, it works fine otherwise, and the stacktrace looks rather
>> > platform independent...
>>
>> Indeed, and if these clocks were doing anything unsavoury, we'd
>> probably see other things exploding. So we need to find out where we
>> are diverging.
>>
>> What compiler are you using? I just noticed that my build
>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>> going to upgrade that to gcc 5.3 and retest.
> 
> Same thing. The damn thing stubbornly works.
> 
> Please send your full configuration, compiler version, exact QEMU
> command line, and any other detail that could be vaguely relevant. As
> the old VGIC gets removed in 4.8, we definitely need to nail that
> sucker right now.

I built the kernel with
gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
by Linaro (full config attached). For the Rootfs (and Qemu) I did use
the same compiler version, but built using OpenEmbedded.

Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
that much on mainline but it seems to be rather stable so far.

I can reproduce the issue with a minimal command such as this:
qemu-system-arm -enable-kvm -M virt -cpu host

[  179.430694] Unable to handle kernel paging request at virtual address
fffffffc
What is puzzling me a bit that the address the kernel tries to access is
constantly 0xfffffffc. This would be -4, which would be -EINTR? A
unhandled error return?

--
Stefan

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 162820 bytes --]

#
# Automatically generated file; DO NOT EDIT.
# Linux/arm 4.7.0-rc7 Kernel Configuration
#
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARM_DMA_USE_IOMMU=y
CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
CONFIG_MIGHT_HAVE_PCI=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_NO_IOPORT_MAP=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_BANDGAP=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ZONE_DMA=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=3
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
CONFIG_HANDLE_DOMAIN_IRQ=y
CONFIG_IRQ_DOMAIN_DEBUG=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
# CONFIG_BUILD_BIN2C is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_NMI_LOG_BUF_SHIFT=13
CONFIG_GENERIC_SCHED_CLOCK=y
CONFIG_CGROUPS=y
# CONFIG_MEMCG is not set
# CONFIG_BLK_CGROUP is not set
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CPUSETS is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_NAMESPACES is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
# CONFIG_USERFAULTFD is not set
CONFIG_PCI_QUIRKS=y
CONFIG_MEMBARRIER=y
CONFIG_EMBEDDED=y
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
CONFIG_COMPAT_BRK=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLUB_CPU_PARTIAL=y
# CONFIG_SYSTEM_DATA_VERIFICATION is not set
# CONFIG_PROFILING is not set
CONFIG_KEXEC_CORE=y
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
# CONFIG_JUMP_LABEL is not set
# CONFIG_UPROBES is not set
# CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_IDLE_POLL_SETUP=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_CLK=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_HAVE_RCU_TABLE_FREE=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR is not set
CONFIG_CC_STACKPROTECTOR_NONE=y
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
CONFIG_ARCH_MMAP_RND_BITS=8
# CONFIG_HAVE_ARCH_HASH is not set
# CONFIG_ISA_BUS_API is not set
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_OLD_SIGACTION=y
# CONFIG_CPU_NO_EFFICIENT_FFS is not set

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_TRIM_UNUSED_KSYMS is not set
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_LBDAF=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLK_CMDLINE_PARSER=y

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_AIX_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_CMDLINE_PARTITION=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
CONFIG_FREEZER=y

#
# System Type
#
CONFIG_MMU=y
CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_GEMINI is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_W90X900 is not set
# CONFIG_ARCH_LPC32XX is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_ARCH_OMAP1 is not set

#
# Multiple platform selection
#

#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not set
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_MULTI_V6_V7=y
# CONFIG_ARCH_MULTI_CPU_AUTO is not set
CONFIG_ARCH_VIRT=y
CONFIG_ARCH_MVEBU=y
CONFIG_MACH_MVEBU_ANY=y
CONFIG_MACH_MVEBU_V7=y
CONFIG_MACH_ARMADA_370=y
CONFIG_MACH_ARMADA_375=y
CONFIG_MACH_ARMADA_38X=y
CONFIG_MACH_ARMADA_39X=y
CONFIG_MACH_ARMADA_XP=y
CONFIG_MACH_DOVE=y
CONFIG_ARCH_ALPINE=y
CONFIG_ARCH_ARTPEC=y
CONFIG_MACH_ARTPEC6=y
CONFIG_ARCH_AT91=y
CONFIG_SOC_SAMA5D2=y
CONFIG_SOC_SAMA5D3=y
CONFIG_SOC_SAMA5D4=y
CONFIG_HAVE_AT91_UTMI=y
CONFIG_HAVE_AT91_USB_CLK=y
CONFIG_COMMON_CLK_AT91=y
CONFIG_HAVE_AT91_SMD=y
CONFIG_HAVE_AT91_H32MX=y
CONFIG_HAVE_AT91_GENERATED_CLK=y
CONFIG_SOC_SAM_V7=y
CONFIG_SOC_SAMA5=y
# CONFIG_ARCH_AXXIA is not set
CONFIG_ARCH_BCM=y

#
# IPROC architected SoCs
#
CONFIG_ARCH_BCM_IPROC=y
CONFIG_ARCH_BCM_CYGNUS=y
CONFIG_ARCH_BCM_NSP=y
CONFIG_ARCH_BCM_5301X=y

#
# KONA architected SoCs
#
CONFIG_ARCH_BCM_MOBILE=y
CONFIG_ARCH_BCM_281XX=y
CONFIG_ARCH_BCM_21664=y
CONFIG_ARCH_BCM_MOBILE_L2_CACHE=y
CONFIG_ARCH_BCM_MOBILE_SMC=y
CONFIG_ARCH_BCM_MOBILE_SMP=y

#
# Other Architectures
#
CONFIG_ARCH_BCM2835=y
# CONFIG_ARCH_BCM_63XX is not set
CONFIG_ARCH_BRCMSTB=y
CONFIG_ARCH_BERLIN=y
CONFIG_MACH_BERLIN_BG2=y
CONFIG_MACH_BERLIN_BG2CD=y
CONFIG_MACH_BERLIN_BG2Q=y
CONFIG_ARCH_DIGICOLOR=y
CONFIG_ARCH_HIGHBANK=y
CONFIG_ARCH_HISI=y

#
# Hisilicon platform type
#
CONFIG_ARCH_HI3xxx=y
CONFIG_ARCH_HIP01=y
CONFIG_ARCH_HIP04=y
CONFIG_ARCH_HIX5HD2=y
CONFIG_ARCH_KEYSTONE=y
CONFIG_ARCH_MESON=y
CONFIG_MACH_MESON6=y
CONFIG_MACH_MESON8=y
CONFIG_MACH_MESON8B=y
CONFIG_ARCH_MXC=y
CONFIG_MXC_TZIC=y
CONFIG_HAVE_IMX_ANATOP=y
CONFIG_HAVE_IMX_GPC=y
CONFIG_HAVE_IMX_MMDC=y
CONFIG_HAVE_IMX_SRC=y

#
# Device tree only
#

#
# Cortex-A platforms
#
CONFIG_SOC_IMX5=y
CONFIG_SOC_IMX50=y
CONFIG_SOC_IMX51=y
CONFIG_SOC_IMX53=y
CONFIG_SOC_IMX6=y
CONFIG_SOC_IMX6Q=y
CONFIG_SOC_IMX6SL=y
CONFIG_SOC_IMX6SX=y
CONFIG_SOC_IMX6UL=y
CONFIG_SOC_IMX7D=y
CONFIG_SOC_LS1021A=y

#
# Cortex-A/Cortex-M asymmetric multiprocessing platforms
#
CONFIG_SOC_VF610=y
CONFIG_VF_USE_ARM_GLOBAL_TIMER=y
# CONFIG_VF_USE_PIT_TIMER is not set
CONFIG_ARCH_MEDIATEK=y
CONFIG_MACH_MT2701=y
CONFIG_MACH_MT6589=y
CONFIG_MACH_MT6592=y
CONFIG_MACH_MT7623=y
CONFIG_MACH_MT8127=y
CONFIG_MACH_MT8135=y
CONFIG_ARCH_OMAP=y

#
# TI OMAP Common Features
#

#
# OMAP Feature Selections
#
# CONFIG_POWER_AVS_OMAP is not set
# CONFIG_OMAP_RESET_CLOCKS is not set
CONFIG_OMAP_MUX=y
# CONFIG_OMAP_MUX_DEBUG is not set
CONFIG_OMAP_MUX_WARNINGS=y
CONFIG_OMAP_32K_TIMER=y
# CONFIG_OMAP3_L2_AUX_SECURE_SAVE_RESTORE is not set
CONFIG_OMAP_DM_TIMER=y
CONFIG_OMAP_PM_NOOP=y
CONFIG_MACH_OMAP_GENERIC=y

#
# TI OMAP/AM/DM/DRA Family
#
CONFIG_ARCH_OMAP3=y
CONFIG_ARCH_OMAP4=y
CONFIG_SOC_OMAP5=y
CONFIG_SOC_AM33XX=y
CONFIG_SOC_AM43XX=y
CONFIG_SOC_DRA7XX=y
CONFIG_ARCH_OMAP2PLUS=y
CONFIG_OMAP_INTERCONNECT_BARRIER=y

#
# TI OMAP2/3/4 Specific Features
#
CONFIG_ARCH_OMAP2PLUS_TYPICAL=y
CONFIG_SOC_HAS_OMAP2_SDRC=y
CONFIG_SOC_HAS_REALTIME_COUNTER=y
CONFIG_SOC_OMAP3430=y
CONFIG_SOC_TI81XX=y
CONFIG_OMAP_PACKAGE_CBB=y

#
# OMAP Legacy Platform Data Board Type
#
CONFIG_MACH_OMAP_LDP=y
CONFIG_MACH_OMAP3517EVM=y
CONFIG_MACH_OMAP3_PANDORA=y
CONFIG_MACH_NOKIA_RX51=y
# CONFIG_OMAP3_SDRC_AC_TIMING is not set
# CONFIG_OMAP5_ERRATA_801819 is not set
# CONFIG_ARCH_MMP is not set
CONFIG_ARCH_QCOM=y
CONFIG_ARCH_MSM8X60=y
CONFIG_ARCH_MSM8960=y
CONFIG_ARCH_MSM8974=y
# CONFIG_ARCH_REALVIEW is not set
CONFIG_ARCH_ROCKCHIP=y
CONFIG_ARCH_SOCFPGA=y
# CONFIG_SOCFPGA_SUSPEND is not set
CONFIG_PLAT_SPEAR=y
CONFIG_ARCH_SPEAR13XX=y
CONFIG_MACH_SPEAR1310=y
CONFIG_MACH_SPEAR1340=y
CONFIG_ARCH_STI=y
CONFIG_SOC_STIH415=y
CONFIG_SOC_STIH416=y
CONFIG_SOC_STIH407=y
# CONFIG_ARCH_S5PV210 is not set
CONFIG_ARCH_EXYNOS=y
CONFIG_S5P_DEV_MFC=y
# CONFIG_ARCH_EXYNOS3 is not set
CONFIG_ARCH_EXYNOS4=y
CONFIG_ARCH_EXYNOS5=y

#
# EXYNOS SoCs
#
CONFIG_CPU_EXYNOS4210=y
CONFIG_SOC_EXYNOS4212=y
CONFIG_SOC_EXYNOS4412=y
CONFIG_SOC_EXYNOS4415=y
CONFIG_SOC_EXYNOS5250=y
CONFIG_SOC_EXYNOS5260=y
CONFIG_SOC_EXYNOS5410=y
CONFIG_SOC_EXYNOS5420=y
CONFIG_SOC_EXYNOS5440=y
CONFIG_SOC_EXYNOS5800=y
CONFIG_EXYNOS5420_MCPM=y
CONFIG_EXYNOS_CPU_SUSPEND=y
CONFIG_PLAT_SAMSUNG=y

#
# Samsung Common options
#

#
# Boot options
#
# CONFIG_SAMSUNG_ATAGS is not set

#
# Power management
#
# CONFIG_SAMSUNG_PM_CHECK is not set
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_SHMOBILE_MULTI=y
CONFIG_PM_RMOBILE=y
CONFIG_ARCH_RCAR_GEN1=y
CONFIG_ARCH_RCAR_GEN2=y
CONFIG_ARCH_RMOBILE=y
CONFIG_ARCH_RENESAS=y
CONFIG_ARCH_EMEV2=y
CONFIG_ARCH_R7S72100=y
CONFIG_ARCH_R8A73A4=y
CONFIG_ARCH_R8A7740=y
CONFIG_ARCH_R8A7778=y
CONFIG_ARCH_R8A7779=y
CONFIG_ARCH_R8A7790=y
CONFIG_ARCH_R8A7791=y
CONFIG_ARCH_R8A7793=y
CONFIG_ARCH_R8A7794=y
CONFIG_ARCH_SH73A0=y
CONFIG_ARCH_SUNXI=y
CONFIG_MACH_SUN4I=y
CONFIG_MACH_SUN5I=y
CONFIG_MACH_SUN6I=y
CONFIG_MACH_SUN7I=y
CONFIG_MACH_SUN8I=y
CONFIG_MACH_SUN9I=y
CONFIG_ARCH_SIRF=y

#
# CSR SiRF atlas6/primaII/Atlas7 Specific Features
#
CONFIG_ARCH_ATLAS6=y
CONFIG_ARCH_ATLAS7=y
CONFIG_ARCH_PRIMA2=y
CONFIG_SIRF_IRQ=y
# CONFIG_ARCH_TANGO is not set
CONFIG_ARCH_TEGRA=y
CONFIG_ARCH_UNIPHIER=y
CONFIG_ARCH_U8500=y
CONFIG_UX500_SOC_DB8500=y
CONFIG_MACH_MOP500=y
CONFIG_MACH_HREFV60=y
CONFIG_MACH_SNOWBALL=y
CONFIG_UX500_AUTO_PLATFORM=y
CONFIG_UX500_DEBUG_UART=2
CONFIG_ARCH_VEXPRESS=y
CONFIG_ARCH_VEXPRESS_CORTEX_A5_A9_ERRATA=y
# CONFIG_ARCH_VEXPRESS_DCSCB is not set
CONFIG_ARCH_VEXPRESS_SPC=y
CONFIG_ARCH_VEXPRESS_TC2_PM=y
CONFIG_ARCH_VT8500=y
CONFIG_ARCH_WM8850=y
# CONFIG_ARCH_ZX is not set
CONFIG_ARCH_ZYNQ=y
CONFIG_PLAT_ORION=y
CONFIG_PLAT_VERSATILE=y
CONFIG_ARCH_SUPPORTS_FIRMWARE=y
CONFIG_ARCH_SUPPORTS_TRUSTED_FOUNDATIONS=y

#
# Firmware options
#
CONFIG_TRUSTED_FOUNDATIONS=y

#
# Processor Type
#
CONFIG_CPU_PJ4=y
CONFIG_CPU_PJ4B=y
CONFIG_CPU_V7=y
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y

#
# Processor Features
#
CONFIG_ARM_LPAE=y
CONFIG_ARM_PV_FIXUP=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_ARM_THUMB=y
CONFIG_ARM_THUMBEE=y
CONFIG_ARM_VIRT_EXT=y
CONFIG_SWP_EMULATE=y
# CONFIG_CPU_BIG_ENDIAN is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_BPREDICT_DISABLE is not set
CONFIG_KUSER_HELPERS=y
CONFIG_VDSO=y
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_CACHE_FEROCEON_L2=y
# CONFIG_CACHE_FEROCEON_L2_WRITETHROUGH is not set
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_CACHE_L2X0=y
CONFIG_PL310_ERRATA_588369=y
CONFIG_PL310_ERRATA_727915=y
CONFIG_PL310_ERRATA_753970=y
CONFIG_PL310_ERRATA_769419=y
CONFIG_CACHE_TAUROS2=y
CONFIG_CACHE_UNIPHIER=y
CONFIG_ARM_L1_CACHE_SHIFT_6=y
CONFIG_ARM_L1_CACHE_SHIFT=6
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
CONFIG_ARM_HEAVY_MB=y
CONFIG_ARCH_SUPPORTS_BIG_ENDIAN=y
CONFIG_DEBUG_RODATA=y
CONFIG_DEBUG_ALIGN_RODATA=y
CONFIG_IWMMXT=y
CONFIG_MULTI_IRQ_HANDLER=y
CONFIG_PJ4B_ERRATA_4742=y
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_ERRATA_643719=y
CONFIG_ARM_ERRATA_720789=y
CONFIG_ARM_ERRATA_754322=y
CONFIG_ARM_ERRATA_754327=y
CONFIG_ARM_ERRATA_764369=y
CONFIG_ARM_ERRATA_775420=y
CONFIG_ARM_ERRATA_798181=y
# CONFIG_ARM_ERRATA_773022 is not set
CONFIG_ICST=y

#
# Bus support
#
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_DOMAINS_GENERIC=y
CONFIG_PCI_SYSCALL=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_PCIE_PME=y
# CONFIG_PCIE_DPC is not set
CONFIG_PCI_BUS_ADDR_T_64BIT=y
CONFIG_PCI_MSI=y
CONFIG_PCI_MSI_IRQ_DOMAIN=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
# CONFIG_PCI_STUB is not set
CONFIG_PCI_ECAM=y
# CONFIG_PCI_IOV is not set
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not set
# CONFIG_HOTPLUG_PCI is not set

#
# PCI host controller drivers
#
# CONFIG_PCI_DRA7XX is not set
CONFIG_PCI_MVEBU=y
# CONFIG_PCIE_DW_PLAT is not set
CONFIG_PCIE_DW=y
# CONFIG_PCI_EXYNOS is not set
# CONFIG_PCI_IMX6 is not set
CONFIG_PCI_TEGRA=y
CONFIG_PCI_RCAR_GEN2=y
CONFIG_PCIE_RCAR=y
CONFIG_PCI_HOST_COMMON=y
CONFIG_PCI_HOST_GENERIC=y
# CONFIG_PCIE_SPEAR13XX is not set
CONFIG_PCI_KEYSTONE=y
# CONFIG_PCIE_XILINX is not set
# CONFIG_PCI_LAYERSCAPE is not set
CONFIG_PCIE_IPROC=y
CONFIG_PCIE_IPROC_PLATFORM=y
CONFIG_PCIE_IPROC_BCMA=y
CONFIG_PCIE_IPROC_MSI=y
# CONFIG_PCIE_ALTERA is not set
# CONFIG_PCIE_QCOM is not set
# CONFIG_PCIE_ARMADA_8K is not set
# CONFIG_PCCARD is not set

#
# Kernel Features
#
CONFIG_HAVE_SMP=y
CONFIG_SMP=y
CONFIG_SMP_ON_UP=y
CONFIG_ARM_CPU_TOPOLOGY=y
# CONFIG_SCHED_MC is not set
# CONFIG_SCHED_SMT is not set
CONFIG_HAVE_ARM_SCU=y
CONFIG_HAVE_ARM_ARCH_TIMER=y
CONFIG_HAVE_ARM_TWD=y
CONFIG_MCPM=y
CONFIG_MCPM_QUAD_CLUSTER=y
# CONFIG_BIG_LITTLE is not set
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_NR_CPUS=16
CONFIG_HOTPLUG_CPU=y
CONFIG_ARM_PSCI=y
CONFIG_ARCH_NR_GPIO=1024
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_HZ_FIXED=200
CONFIG_HZ=200
CONFIG_SCHED_HRTICK=y
# CONFIG_THUMB2_KERNEL is not set
CONFIG_ARM_PATCH_IDIV=y
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
CONFIG_HAVE_ARCH_PFN_VALID=y
CONFIG_HAVE_GENERIC_RCU_GUP=y
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
CONFIG_HW_PERF_EVENTS=y
CONFIG_SYS_SUPPORTS_HUGETLBFS=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
# CONFIG_ARM_MODULE_PLTS is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_NO_BOOTMEM=y
CONFIG_MEMORY_ISOLATION=y
# CONFIG_HAVE_BOOTMEM_INFO_NODE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_BOUNCE=y
CONFIG_MMU_NOTIFIER=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_TRANSPARENT_HUGEPAGE is not set
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not set
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set
CONFIG_CMA_AREAS=7
# CONFIG_ZPOOL is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSMALLOC is not set
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_IDLE_PAGE_TRACKING is not set
CONFIG_FRAME_VECTOR=y
CONFIG_FORCE_MAX_ZONEORDER=12
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
# CONFIG_SECCOMP is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_PARAVIRT is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
# CONFIG_XEN is not set

#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_ATAGS=y
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
CONFIG_ZBOOT_ROM_TEXT=0
CONFIG_ZBOOT_ROM_BSS=0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
# CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND is not set
CONFIG_CMDLINE=""
CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y
# CONFIG_CRASH_DUMP is not set
CONFIG_AUTO_ZRELADDR=y
# CONFIG_EFI is not set

#
# CPU Power Management
#

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=m

#
# CPU frequency scaling drivers
#
CONFIG_CPUFREQ_DT=y
CONFIG_CPUFREQ_DT_PLATDEV=y
# CONFIG_ARM_BIG_LITTLE_CPUFREQ is not set
CONFIG_ARM_EXYNOS5440_CPUFREQ=y
CONFIG_ARM_HIGHBANK_CPUFREQ=m
# CONFIG_ARM_KIRKWOOD_CPUFREQ is not set
CONFIG_ARM_OMAP2PLUS_CPUFREQ=y
CONFIG_ARM_SPEAR_CPUFREQ=y
# CONFIG_ARM_STI_CPUFREQ is not set
CONFIG_ARM_TEGRA20_CPUFREQ=y
CONFIG_ARM_TEGRA124_CPUFREQ=y
CONFIG_QORIQ_CPUFREQ=y

#
# CPU Idle
#
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y
CONFIG_DT_IDLE_STATES=y

#
# ARM CPU Idle Drivers
#
CONFIG_ARM_CPUIDLE=y
# CONFIG_ARM_BIG_LITTLE_CPUIDLE is not set
# CONFIG_ARM_HIGHBANK_CPUIDLE is not set
CONFIG_ARM_ZYNQ_CPUIDLE=y
# CONFIG_ARM_U8500_CPUIDLE is not set
CONFIG_ARM_AT91_CPUIDLE=y
CONFIG_ARM_EXYNOS_CPUIDLE=y
# CONFIG_ARM_MVEBU_V7_CPUIDLE is not set
CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED=y

#
# Floating point emulation
#

#
# At least one emulation must be selected
#
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
CONFIG_KERNEL_MODE_NEON=y

#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
# CONFIG_HAVE_AOUT is not set
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y

#
# Power management options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not set
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_APM_EMULATION is not set
CONFIG_PM_OPP=y
CONFIG_PM_CLK=y
CONFIG_PM_GENERIC_DOMAINS=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
CONFIG_PM_GENERIC_DOMAINS_SLEEP=y
CONFIG_PM_GENERIC_DOMAINS_OF=y
CONFIG_CPU_PM=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARM_CPU_SUSPEND=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
# CONFIG_UNIX_DIAG is not set
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=m
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=m
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
CONFIG_NET_IP_TUNNEL=y
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_UDP_TUNNEL is not set
# CONFIG_NET_FOU is not set
# CONFIG_NET_FOU_IP_TUNNELS is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
# CONFIG_IPV6_ROUTE_INFO is not set
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_VTI is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_SIT_6RD is not set
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=m
# CONFIG_IPV6_FOU is not set
# CONFIG_IPV6_FOU_TUNNEL is not set
CONFIG_IPV6_MULTIPLE_TABLES=y
# CONFIG_IPV6_SUBTREES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NET_PTP_CLASSIFY=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
CONFIG_HAVE_NET_DSA=y
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_6LOWPAN is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
CONFIG_DNS_RESOLVER=y
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_HSR is not set
# CONFIG_NET_SWITCHDEV is not set
# CONFIG_NET_L3_MASTER_DEV is not set
# CONFIG_QRTR is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
# CONFIG_SOCK_CGROUP_DATA is not set
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
# CONFIG_BPF_JIT is not set
CONFIG_NET_FLOW_LIMIT=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y

#
# CAN Device Drivers
#
# CONFIG_CAN_VCAN is not set
# CONFIG_CAN_SLCAN is not set
CONFIG_CAN_DEV=y
CONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_LEDS is not set
CONFIG_CAN_AT91=m
# CONFIG_CAN_FLEXCAN is not set
# CONFIG_CAN_GRCAN is not set
CONFIG_CAN_RCAR=m
CONFIG_CAN_SUN4I=y
# CONFIG_CAN_TI_HECC is not set
CONFIG_CAN_XILINXCAN=y
# CONFIG_CAN_C_CAN is not set
# CONFIG_CAN_CC770 is not set
# CONFIG_CAN_IFI_CANFD is not set
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_SJA1000 is not set
# CONFIG_CAN_SOFTING is not set

#
# CAN SPI interfaces
#
CONFIG_CAN_MCP251X=y

#
# CAN USB interfaces
#
# CONFIG_CAN_EMS_USB is not set
# CONFIG_CAN_ESD_USB2 is not set
# CONFIG_CAN_GS_USB is not set
# CONFIG_CAN_KVASER_USB is not set
# CONFIG_CAN_PEAK_USB is not set
# CONFIG_CAN_8DEV_USB is not set
# CONFIG_CAN_DEBUG_DEVICES is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_BREDR=y
# CONFIG_BT_RFCOMM is not set
# CONFIG_BT_BNEP is not set
# CONFIG_BT_HIDP is not set
CONFIG_BT_HS=y
CONFIG_BT_LE=y
# CONFIG_BT_LEDS is not set
# CONFIG_BT_SELFTEST is not set
CONFIG_BT_DEBUGFS=y

#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
CONFIG_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not set
# CONFIG_LIB80211 is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_MINSTREL_HT=y
# CONFIG_MAC80211_RC_MINSTREL_VHT is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_REGULATOR is not set
CONFIG_RFKILL_GPIO=y
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
# CONFIG_LWTUNNEL is not set
CONFIG_DST_CACHE=y
# CONFIG_NET_DEVLINK is not set
CONFIG_MAY_USE_DEVLINK=y
CONFIG_HAVE_CBPF_JIT=y

#
# Device Drivers
#
CONFIG_ARM_AMBA=y
CONFIG_TEGRA_AHB=y

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
CONFIG_WANT_DEV_COREDUMP=y
CONFIG_ALLOW_DEV_COREDUMP=y
CONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_GENERIC_CPU_DEVICES is not set
CONFIG_SOC_BUS=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_SPI=y
CONFIG_REGMAP_SPMI=y
CONFIG_REGMAP_MMIO=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_FENCE_TRACE is not set
CONFIG_DMA_CMA=y

#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=64
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8

#
# Bus devices
#
CONFIG_ARM_CCI=y
CONFIG_ARM_CCI400_COMMON=y
# CONFIG_ARM_CCI400_PMU is not set
CONFIG_ARM_CCI400_PORT_CTRL=y
# CONFIG_ARM_CCI5xx_PMU is not set
# CONFIG_ARM_CCN is not set
CONFIG_BRCMSTB_GISB_ARB=y
# CONFIG_IMX_WEIM is not set
CONFIG_MVEBU_MBUS=y
CONFIG_OMAP_INTERCONNECT=y
CONFIG_OMAP_OCP2SCP=y
CONFIG_SIMPLE_PM_BUS=y
CONFIG_SUNXI_RSB=m
CONFIG_UNIPHIER_SYSTEM_BUS=y
CONFIG_VEXPRESS_CONFIG=y
# CONFIG_CONNECTOR is not set
CONFIG_MTD=y
# CONFIG_MTD_TESTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
# CONFIG_MTD_AFS_PARTS is not set
CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_AR7_PARTS is not set
# CONFIG_MTD_BCM47XX_PARTS is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
CONFIG_MTD_M25P80=y
CONFIG_MTD_SPEAR_SMI=y
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLOCK2MTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# CONFIG_MTD_ST_SPI_FSM is not set
CONFIG_MTD_NAND_ECC=y
# CONFIG_MTD_NAND_ECC_SMC is not set
CONFIG_MTD_NAND=y
# CONFIG_MTD_NAND_ECC_BCH is not set
# CONFIG_MTD_SM_COMMON is not set
CONFIG_MTD_NAND_DENALI=y
# CONFIG_MTD_NAND_DENALI_PCI is not set
CONFIG_MTD_NAND_DENALI_DT=y
# CONFIG_MTD_NAND_GPIO is not set
# CONFIG_MTD_NAND_OMAP2 is not set
# CONFIG_MTD_NAND_OMAP_BCH_BUILD is not set
CONFIG_MTD_NAND_IDS=y
# CONFIG_MTD_NAND_RICOH is not set
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_DOCG4 is not set
# CONFIG_MTD_NAND_CAFE is not set
CONFIG_MTD_NAND_ATMEL=y
# CONFIG_MTD_NAND_PXA3xx is not set
# CONFIG_MTD_NAND_NANDSIM is not set
# CONFIG_MTD_NAND_GPMI_NAND is not set
CONFIG_MTD_NAND_BRCMNAND=y
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_NAND_ORION is not set
CONFIG_MTD_NAND_VF610_NFC=y
# CONFIG_MTD_NAND_MXC is not set
CONFIG_MTD_NAND_DAVINCI=y
# CONFIG_MTD_NAND_FSMC is not set
# CONFIG_MTD_NAND_SUNXI is not set
# CONFIG_MTD_NAND_HISI504 is not set
# CONFIG_MTD_NAND_QCOM is not set
# CONFIG_MTD_ONENAND is not set

#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# CONFIG_MTD_LPDDR2_NVM is not set
CONFIG_MTD_SPI_NOR=y
# CONFIG_MTD_MT81xx_NOR is not set
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
CONFIG_SPI_FSL_QUADSPI=m
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_DYNAMIC=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_ADDRESS_PCI=y
CONFIG_OF_IRQ=y
CONFIG_OF_NET=y
CONFIG_OF_MDIO=y
CONFIG_OF_PCI=y
CONFIG_OF_PCI_IRQ=y
CONFIG_OF_MTD=y
CONFIG_OF_RESERVED_MEM=y
# CONFIG_OF_OVERLAY is not set
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MG_DISK is not set
CONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_BLK_DEV_RSXX is not set
# CONFIG_BLK_DEV_NVME is not set

#
# Misc devices
#
# CONFIG_SENSORS_LIS3LV02D is not set
CONFIG_AD525X_DPOT=y
CONFIG_AD525X_DPOT_I2C=y
# CONFIG_AD525X_DPOT_SPI is not set
CONFIG_ATMEL_TCLIB=y
CONFIG_ATMEL_TCB_CLKSRC=y
CONFIG_ATMEL_TCB_CLKSRC_BLOCK=0
# CONFIG_DUMMY_IRQ is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
CONFIG_ICS932S401=y
CONFIG_ATMEL_SSC=m
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
CONFIG_QCOM_COINCELL=m
CONFIG_APDS9802ALS=y
CONFIG_ISL29003=y
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_TI_DAC7512 is not set
# CONFIG_ARM_CHARLCD is not set
# CONFIG_BMP085_I2C is not set
# CONFIG_BMP085_SPI is not set
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
CONFIG_SRAM=y
CONFIG_VEXPRESS_SYSCFG=y
# CONFIG_C2PORT is not set

#
# EEPROM support
#
CONFIG_EEPROM_AT24=y
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
CONFIG_EEPROM_93CX6=y
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_CB710_CORE is not set

#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set

#
# Altera FPGA firmware download module
#
# CONFIG_ALTERA_STAPL is not set

#
# Intel MIC Bus Driver
#

#
# SCIF Bus Driver
#

#
# VOP Bus Driver
#

#
# Intel MIC Host Driver
#

#
# Intel MIC Card Driver
#

#
# SCIF Driver
#

#
# Intel MIC Coprocessor State Management (COSM) Drivers
#

#
# VOP Driver
#
# CONFIG_ECHO is not set
# CONFIG_CXL_BASE is not set
# CONFIG_CXL_KERNEL_API is not set
# CONFIG_CXL_EEH is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_NETLINK is not set
# CONFIG_SCSI_MQ_DEFAULT is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_HAVE_PATA_PLATFORM=y
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_SATA_PMP=y

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=y
# CONFIG_AHCI_BRCMSTB is not set
CONFIG_AHCI_ST=y
# CONFIG_AHCI_IMX is not set
# CONFIG_AHCI_CEVA is not set
# CONFIG_AHCI_MVEBU is not set
CONFIG_AHCI_SUNXI=y
CONFIG_AHCI_TEGRA=y
# CONFIG_AHCI_QORIQ is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_DWC is not set
CONFIG_SATA_HIGHBANK=y
CONFIG_SATA_MV=y
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
CONFIG_SATA_RCAR=y
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set

#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARASAN_CF is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IMX is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set

#
# Generic fallback / legacy drivers
#
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
CONFIG_NETDEVICES=y
CONFIG_MII=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_TUN is not set
# CONFIG_TUN_VNET_CROSS_LE is not set
# CONFIG_VETH is not set
CONFIG_VIRTIO_NET=y
# CONFIG_NLMON is not set
# CONFIG_ARCNET is not set

#
# CAIF transport drivers
#
CONFIG_VHOST_NET=y
CONFIG_VHOST_RING=y
CONFIG_VHOST=y
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set

#
# Distributed Switch Architecture drivers
#
CONFIG_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_TYPHOON is not set
CONFIG_NET_VENDOR_ADAPTEC=y
# CONFIG_ADAPTEC_STARFIRE is not set
CONFIG_NET_VENDOR_AGERE=y
# CONFIG_ET131X is not set
CONFIG_NET_VENDOR_ALLWINNER=y
CONFIG_SUN4I_EMAC=y
CONFIG_NET_VENDOR_ALTEON=y
# CONFIG_ACENIC is not set
# CONFIG_ALTERA_TSE is not set
CONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not set
CONFIG_NET_VENDOR_ARC=y
# CONFIG_ARC_EMAC is not set
# CONFIG_EMAC_ROCKCHIP is not set
CONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not set
# CONFIG_NET_VENDOR_AURORA is not set
CONFIG_NET_CADENCE=y
CONFIG_MACB=y
CONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BCMGENET is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not set
# CONFIG_SYSTEMPORT is not set
# CONFIG_BNXT is not set
CONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not set
CONFIG_NET_CALXEDA_XGMAC=y
CONFIG_NET_VENDOR_CAVIUM=y
CONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not set
CONFIG_NET_VENDOR_CIRRUS=y
# CONFIG_CS89x0 is not set
CONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not set
# CONFIG_DM9000 is not set
# CONFIG_DNET is not set
CONFIG_NET_VENDOR_DEC=y
# CONFIG_NET_TULIP is not set
CONFIG_NET_VENDOR_DLINK=y
# CONFIG_DL2K is not set
# CONFIG_SUNDANCE is not set
CONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not set
CONFIG_NET_VENDOR_EZCHIP=y
# CONFIG_EZCHIP_NPS_MANAGEMENT_ENET is not set
CONFIG_NET_VENDOR_EXAR=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
CONFIG_NET_VENDOR_FARADAY=y
# CONFIG_FTMAC100 is not set
# CONFIG_FTGMAC100 is not set
CONFIG_NET_VENDOR_FREESCALE=y
CONFIG_FEC=y
CONFIG_FSL_PQ_MDIO=y
# CONFIG_FSL_XGMAC_MDIO is not set
CONFIG_GIANFAR=y
CONFIG_NET_VENDOR_HISILICON=y
CONFIG_HIX5HD2_GMAC=y
# CONFIG_HIP04_ETH is not set
# CONFIG_HNS is not set
# CONFIG_HNS_DSAF is not set
# CONFIG_HNS_ENET is not set
CONFIG_NET_VENDOR_HP=y
# CONFIG_HP100 is not set
CONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not set
# CONFIG_E1000 is not set
# CONFIG_E1000E is not set
CONFIG_IGB=y
CONFIG_IGB_HWMON=y
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_I40E is not set
# CONFIG_I40EVF is not set
# CONFIG_FM10K is not set
CONFIG_NET_VENDOR_I825XX=y
# CONFIG_JME is not set
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_MV643XX_ETH=y
CONFIG_MVMDIO=y
# CONFIG_MVNETA_BM_ENABLE is not set
CONFIG_MVNETA=y
# CONFIG_MVNETA_BM is not set
# CONFIG_MVPP2 is not set
CONFIG_PXA168_ETH=m
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_NET_VENDOR_MEDIATEK is not set
CONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
CONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
CONFIG_KS8851=y
# CONFIG_KS8851_MLL is not set
# CONFIG_KSZ884X_PCI is not set
CONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
# CONFIG_ENCX24J600 is not set
CONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not set
CONFIG_NET_VENDOR_NATSEMI=y
# CONFIG_NATSEMI is not set
# CONFIG_NS83820 is not set
CONFIG_NET_VENDOR_NETRONOME=y
# CONFIG_NFP_NETVF is not set
CONFIG_NET_VENDOR_8390=y
# CONFIG_AX88796 is not set
# CONFIG_NE2K_PCI is not set
CONFIG_NET_VENDOR_NVIDIA=y
# CONFIG_FORCEDETH is not set
CONFIG_NET_VENDOR_OKI=y
# CONFIG_ETHOC is not set
CONFIG_NET_PACKET_ENGINE=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_QLGE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_QED is not set
CONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_QCA7000 is not set
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_R8169=y
CONFIG_NET_VENDOR_RENESAS=y
CONFIG_SH_ETH=y
# CONFIG_RAVB is not set
CONFIG_NET_VENDOR_RDC=y
# CONFIG_R6040 is not set
CONFIG_NET_VENDOR_ROCKER=y
CONFIG_NET_VENDOR_SAMSUNG=y
# CONFIG_SXGBE_ETH is not set
CONFIG_NET_VENDOR_SEEQ=y
CONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not set
CONFIG_NET_VENDOR_SIS=y
# CONFIG_SIS900 is not set
# CONFIG_SIS190 is not set
# CONFIG_SFC is not set
CONFIG_NET_VENDOR_SMSC=y
# CONFIG_SMC91X is not set
# CONFIG_EPIC100 is not set
# CONFIG_SMC911X is not set
CONFIG_SMSC911X=y
# CONFIG_SMSC911X_ARCH_HOOKS is not set
# CONFIG_SMSC9420 is not set
CONFIG_NET_VENDOR_STMICRO=y
CONFIG_STMMAC_ETH=y
CONFIG_STMMAC_PLATFORM=y
CONFIG_DWMAC_GENERIC=y
CONFIG_DWMAC_IPQ806X=y
# CONFIG_DWMAC_LPC18XX is not set
CONFIG_DWMAC_MESON=y
CONFIG_DWMAC_ROCKCHIP=y
CONFIG_DWMAC_SOCFPGA=y
CONFIG_DWMAC_STI=y
CONFIG_DWMAC_SUNXI=y
# CONFIG_STMMAC_PCI is not set
CONFIG_NET_VENDOR_SUN=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NIU is not set
CONFIG_NET_VENDOR_SYNOPSYS=y
CONFIG_SYNOPSYS_DWC_ETH_QOS=y
CONFIG_NET_VENDOR_TEHUTI=y
# CONFIG_TEHUTI is not set
CONFIG_NET_VENDOR_TI=y
# CONFIG_TI_DAVINCI_EMAC is not set
CONFIG_TI_DAVINCI_MDIO=y
CONFIG_TI_DAVINCI_CPDMA=y
CONFIG_TI_CPSW_PHY_SEL=y
CONFIG_TI_CPSW_ALE=y
CONFIG_TI_CPSW=y
# CONFIG_TI_CPTS is not set
# CONFIG_TLAN is not set
CONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not set
CONFIG_NET_VENDOR_XILINX=y
CONFIG_XILINX_EMACLITE=y
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PHYLIB=y

#
# MII PHY device drivers
#
# CONFIG_AQUANTIA_PHY is not set
CONFIG_AT803X_PHY=y
# CONFIG_AMD_PHY is not set
CONFIG_MARVELL_PHY=y
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_TERANETICS_PHY is not set
CONFIG_SMSC_PHY=y
CONFIG_BCM_NET_PHYLIB=y
CONFIG_BROADCOM_PHY=y
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM87XX_PHY is not set
CONFIG_ICPLUS_PHY=y
CONFIG_REALTEK_PHY=y
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_MICREL_PHY=y
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_MICROCHIP_PHY is not set
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=y
# CONFIG_MDIO_GPIO is not set
CONFIG_MDIO_SUN4I=y
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_BCM_IPROC is not set
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
CONFIG_USB_NET_DRIVERS=y
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
CONFIG_USB_PEGASUS=y
# CONFIG_USB_RTL8150 is not set
CONFIG_USB_RTL8152=m
# CONFIG_USB_LAN78XX is not set
CONFIG_USB_USBNET=y
CONFIG_USB_NET_AX8817X=y
CONFIG_USB_NET_AX88179_178A=y
CONFIG_USB_NET_CDCETHER=y
# CONFIG_USB_NET_CDC_EEM is not set
CONFIG_USB_NET_CDC_NCM=y
# CONFIG_USB_NET_HUAWEI_CDC_NCM is not set
# CONFIG_USB_NET_CDC_MBIM is not set
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not set
CONFIG_USB_NET_SMSC75XX=y
CONFIG_USB_NET_SMSC95XX=y
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=y
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
CONFIG_USB_NET_CDC_SUBSET_ENABLE=y
CONFIG_USB_NET_CDC_SUBSET=y
# CONFIG_USB_ALI_M5632 is not set
# CONFIG_USB_AN2720 is not set
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=y
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
# CONFIG_USB_NET_QMI_WWAN is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_NET_INT51X1 is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_USB_SIERRA_NET is not set
# CONFIG_USB_VL600 is not set
# CONFIG_USB_NET_CH9200 is not set
CONFIG_WLAN=y
CONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not set
CONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
# CONFIG_ATH9K is not set
# CONFIG_ATH9K_HTC is not set
# CONFIG_CARL9170 is not set
# CONFIG_ATH6KL is not set
# CONFIG_AR5523 is not set
# CONFIG_WIL6210 is not set
# CONFIG_ATH10K is not set
# CONFIG_WCN36XX is not set
CONFIG_WLAN_VENDOR_ATMEL=y
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not set
CONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
CONFIG_BRCMUTIL=m
# CONFIG_BRCMSMAC is not set
CONFIG_BRCMFMAC=m
CONFIG_BRCMFMAC_PROTO_BCDC=y
CONFIG_BRCMFMAC_SDIO=y
# CONFIG_BRCMFMAC_USB is not set
# CONFIG_BRCMFMAC_PCIE is not set
# CONFIG_BRCM_TRACING is not set
# CONFIG_BRCMDBG is not set
CONFIG_WLAN_VENDOR_CISCO=y
CONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_IWLWIFI is not set
CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_PRISM54 is not set
CONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_MWIFIEX=m
CONFIG_MWIFIEX_SDIO=m
# CONFIG_MWIFIEX_PCIE is not set
# CONFIG_MWIFIEX_USB is not set
# CONFIG_MWL8K is not set
CONFIG_WLAN_VENDOR_MEDIATEK=y
# CONFIG_MT7601U is not set
CONFIG_WLAN_VENDOR_RALINK=y
CONFIG_RT2X00=m
# CONFIG_RT2400PCI is not set
# CONFIG_RT2500PCI is not set
# CONFIG_RT61PCI is not set
# CONFIG_RT2800PCI is not set
# CONFIG_RT2500USB is not set
# CONFIG_RT73USB is not set
CONFIG_RT2800USB=m
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
# CONFIG_RT2800USB_RT3573 is not set
# CONFIG_RT2800USB_RT53XX is not set
# CONFIG_RT2800USB_RT55XX is not set
# CONFIG_RT2800USB_UNKNOWN is not set
CONFIG_RT2800_LIB=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_DEBUG is not set
CONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
CONFIG_RTL_CARDS=m
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8723AE is not set
# CONFIG_RTL8723BE is not set
# CONFIG_RTL8188EE is not set
# CONFIG_RTL8192EE is not set
# CONFIG_RTL8821AE is not set
# CONFIG_RTL8192CU is not set
# CONFIG_RTL8XXXU is not set
CONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not set
CONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not set
CONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
CONFIG_WLAN_VENDOR_ZYDAS=y
# CONFIG_USB_ZD1201 is not set
# CONFIG_ZD1211RW is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
# CONFIG_WAN is not set
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_NVM is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_LEDS=y
CONFIG_INPUT_FF_MEMLESS=m
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
CONFIG_INPUT_MATRIXKMAP=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_QT1070=m
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_SNVS_PWRKEY is not set
# CONFIG_KEYBOARD_IMX is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_NOMADIK is not set
CONFIG_KEYBOARD_TEGRA=y
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_PMIC8XXX is not set
CONFIG_KEYBOARD_SAMSUNG=m
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_KEYBOARD_ST_KEYSCAN=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_SH_KEYSC is not set
# CONFIG_KEYBOARD_STMPE is not set
# CONFIG_KEYBOARD_SUN4I_LRADC is not set
# CONFIG_KEYBOARD_OMAP4 is not set
CONFIG_KEYBOARD_SPEAR=y
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_KEYBOARD_CROS_EC=m
# CONFIG_KEYBOARD_CAP11XX is not set
CONFIG_KEYBOARD_BCM=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_BYD=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_PS2_FOCALTECH=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
CONFIG_MOUSE_CYAPA=m
CONFIG_MOUSE_ELAN_I2C=y
CONFIG_MOUSE_ELAN_I2C_I2C=y
# CONFIG_MOUSE_ELAN_I2C_SMBUS is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_PROPERTIES=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_AR1021_I2C is not set
CONFIG_TOUCHSCREEN_ATMEL_MXT=y
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8318 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_FT6236 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_IPROC is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELAN is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
CONFIG_TOUCHSCREEN_WM97XX=m
CONFIG_TOUCHSCREEN_WM9705=y
CONFIG_TOUCHSCREEN_WM9712=y
CONFIG_TOUCHSCREEN_WM9713=y
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TS4800 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
CONFIG_TOUCHSCREEN_ST1232=m
CONFIG_TOUCHSCREEN_STMPE=y
CONFIG_TOUCHSCREEN_SUN4I=y
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_COLIBRI_VF50 is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AB8500_PONKEY is not set
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_PM8941_PWRKEY is not set
# CONFIG_INPUT_PM8XXX_VIBRATOR is not set
# CONFIG_INPUT_PMIC8XXX_PWRKEY is not set
CONFIG_INPUT_MAX77693_HAPTIC=m
CONFIG_INPUT_MAX8997_HAPTIC=m
# CONFIG_INPUT_MMA8450 is not set
CONFIG_INPUT_MPU3050=y
# CONFIG_INPUT_GP2A is not set
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_TILT_POLLED is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_REGULATOR_HAPTIC is not set
# CONFIG_INPUT_TPS65218_PWRBUTTON is not set
CONFIG_INPUT_AXP20X_PEK=m
# CONFIG_INPUT_TWL4030_PWRBUTTON is not set
# CONFIG_INPUT_TWL4030_VIBRA is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_PALMAS_PWRBUTTON is not set
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_PWM_BEEPER is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_DA9063_ONKEY is not set
CONFIG_INPUT_ADXL34X=m
CONFIG_INPUT_ADXL34X_I2C=m
CONFIG_INPUT_ADXL34X_SPI=m
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_CMA3000 is not set
CONFIG_INPUT_SIRFSOC_ONKEY=y
# CONFIG_INPUT_SOC_BUTTON_ARRAY is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
# CONFIG_RMI4_CORE is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_AMBAKMI=y
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
# CONFIG_SERIO_SUN4I_PS2 is not set
# CONFIG_USERIO is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
CONFIG_DEVMEM=y
CONFIG_DEVKMEM=y

#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
# CONFIG_SERIAL_8250_FINTEK is not set
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
CONFIG_SERIAL_8250_FSL=y
CONFIG_SERIAL_8250_DW=y
CONFIG_SERIAL_8250_EM=y
# CONFIG_SERIAL_8250_RT288X is not set
# CONFIG_SERIAL_8250_OMAP is not set
CONFIG_SERIAL_8250_MT6577=y
CONFIG_SERIAL_8250_UNIPHIER=y
# CONFIG_SERIAL_8250_MOXA is not set
CONFIG_SERIAL_OF_PLATFORM=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_AMBA_PL010 is not set
CONFIG_SERIAL_AMBA_PL011=y
CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set
CONFIG_SERIAL_ATMEL=y
CONFIG_SERIAL_ATMEL_CONSOLE=y
CONFIG_SERIAL_ATMEL_PDC=y
CONFIG_SERIAL_ATMEL_TTYAT=y
CONFIG_SERIAL_MESON=y
CONFIG_SERIAL_MESON_CONSOLE=y
CONFIG_SERIAL_SAMSUNG=y
CONFIG_SERIAL_SAMSUNG_UARTS_4=y
CONFIG_SERIAL_SAMSUNG_UARTS=4
CONFIG_SERIAL_SAMSUNG_CONSOLE=y
CONFIG_SERIAL_SIRFSOC=y
CONFIG_SERIAL_SIRFSOC_CONSOLE=y
CONFIG_SERIAL_TEGRA=y
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
CONFIG_SERIAL_IMX=y
CONFIG_SERIAL_IMX_CONSOLE=y
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_SH_SCI=y
CONFIG_SERIAL_SH_SCI_NR_UARTS=20
CONFIG_SERIAL_SH_SCI_CONSOLE=y
# CONFIG_SERIAL_SH_SCI_EARLYCON is not set
# CONFIG_SERIAL_SH_SCI_DMA is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_SERIAL_MSM=y
CONFIG_SERIAL_MSM_CONSOLE=y
CONFIG_SERIAL_VT8500=y
CONFIG_SERIAL_VT8500_CONSOLE=y
CONFIG_SERIAL_OMAP=y
CONFIG_SERIAL_OMAP_CONSOLE=y
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
CONFIG_SERIAL_XILINX_PS_UART=y
CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
# CONFIG_SERIAL_MPS2_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
CONFIG_SERIAL_FSL_LPUART=y
CONFIG_SERIAL_FSL_LPUART_CONSOLE=y
CONFIG_SERIAL_CONEXANT_DIGICOLOR=y
CONFIG_SERIAL_CONEXANT_DIGICOLOR_CONSOLE=y
CONFIG_SERIAL_ST_ASC=y
CONFIG_SERIAL_ST_ASC_CONSOLE=y
# CONFIG_SERIAL_STM32 is not set
# CONFIG_SERIAL_MVEBU_UART is not set
CONFIG_SERIAL_MCTRL_GPIO=y
# CONFIG_TTY_PRINTK is not set
CONFIG_HVC_DRIVER=y
# CONFIG_HVC_DCC is not set
CONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
CONFIG_HW_RANDOM_ATMEL=y
CONFIG_HW_RANDOM_BCM2835=y
CONFIG_HW_RANDOM_IPROC_RNG200=y
CONFIG_HW_RANDOM_OMAP=y
CONFIG_HW_RANDOM_OMAP3_ROM=y
# CONFIG_HW_RANDOM_VIRTIO is not set
CONFIG_HW_RANDOM_EXYNOS=y
CONFIG_HW_RANDOM_HISI=y
CONFIG_HW_RANDOM_MSM=y
CONFIG_HW_RANDOM_ST=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
# CONFIG_XILLYBUS is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y

#
# Multiplexer I2C Chip support
#
CONFIG_I2C_ARB_GPIO_CHALLENGE=m
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_PCA9541 is not set
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_MUX_PINCTRL=y
# CONFIG_I2C_MUX_REG is not set
CONFIG_I2C_DEMUX_PINCTRL=y
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_HIX5HD2 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
CONFIG_I2C_AT91=m
CONFIG_I2C_BCM2835=y
CONFIG_I2C_BCM_IPROC=y
CONFIG_I2C_BCM_KONA=y
CONFIG_I2C_BRCMSTB=y
CONFIG_I2C_CADENCE=y
# CONFIG_I2C_CBUS_GPIO is not set
CONFIG_I2C_DAVINCI=y
CONFIG_I2C_DESIGNWARE_CORE=y
CONFIG_I2C_DESIGNWARE_PLATFORM=y
# CONFIG_I2C_DESIGNWARE_PCI is not set
CONFIG_I2C_DIGICOLOR=m
CONFIG_I2C_EMEV2=m
CONFIG_I2C_EXYNOS5=y
CONFIG_I2C_GPIO=m
CONFIG_I2C_IMX=m
# CONFIG_I2C_MESON is not set
# CONFIG_I2C_MT65XX is not set
CONFIG_I2C_MV64XXX=y
CONFIG_I2C_NOMADIK=y
# CONFIG_I2C_OCORES is not set
CONFIG_I2C_OMAP=y
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_QUP is not set
CONFIG_I2C_RIIC=y
CONFIG_I2C_RK3X=y
CONFIG_HAVE_S3C2410_I2C=y
CONFIG_I2C_S3C2410=y
CONFIG_I2C_SH_MOBILE=y
# CONFIG_I2C_SIMTEC is not set
CONFIG_I2C_SIRF=y
CONFIG_I2C_ST=y
CONFIG_I2C_SUN6I_P2WI=y
CONFIG_I2C_TEGRA=y
CONFIG_I2C_UNIPHIER=y
CONFIG_I2C_UNIPHIER_F=y
# CONFIG_I2C_VERSATILE is not set
# CONFIG_I2C_WMT is not set
CONFIG_I2C_XILINX=y
CONFIG_I2C_RCAR=y

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
CONFIG_I2C_CROS_EC_TUNNEL=m
# CONFIG_I2C_STUB is not set
CONFIG_I2C_SLAVE=y
CONFIG_I2C_SLAVE_EEPROM=y
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
CONFIG_SPI_ATMEL=m
# CONFIG_SPI_AXI_SPI_ENGINE is not set
CONFIG_SPI_BCM2835=y
CONFIG_SPI_BCM2835AUX=y
# CONFIG_SPI_BCM53XX is not set
CONFIG_SPI_BITBANG=y
CONFIG_SPI_CADENCE=y
CONFIG_SPI_DAVINCI=y
# CONFIG_SPI_DESIGNWARE is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_IMX is not set
# CONFIG_SPI_FSL_SPI is not set
CONFIG_SPI_FSL_DSPI=m
# CONFIG_SPI_MESON_SPIFC is not set
# CONFIG_SPI_MT65XX is not set
# CONFIG_SPI_OC_TINY is not set
CONFIG_SPI_OMAP24XX=y
# CONFIG_SPI_TI_QSPI is not set
CONFIG_SPI_ORION=y
CONFIG_SPI_PL022=y
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_PXA2XX_PCI is not set
CONFIG_SPI_ROCKCHIP=m
CONFIG_SPI_RSPI=y
# CONFIG_SPI_QUP is not set
CONFIG_SPI_S3C64XX=m
# CONFIG_SPI_SC18IS602 is not set
CONFIG_SPI_SH_MSIOF=m
CONFIG_SPI_SH_HSPI=y
CONFIG_SPI_SIRF=y
# CONFIG_SPI_ST_SSC4 is not set
CONFIG_SPI_SUN4I=y
CONFIG_SPI_SUN6I=y
CONFIG_SPI_TEGRA114=y
CONFIG_SPI_TEGRA20_SFLASH=y
CONFIG_SPI_TEGRA20_SLINK=y
# CONFIG_SPI_XCOMM is not set
CONFIG_SPI_XILINX=y
# CONFIG_SPI_ZYNQMP_GQSPI is not set

#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=y
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
CONFIG_SPMI=y
CONFIG_SPMI_MSM_PMIC_ARB=y
# CONFIG_HSI is not set

#
# PPS support
#
CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set

#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_GPIO is not set

#
# PPS generators support
#

#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=y
CONFIG_PTP_1588_CLOCK_GIANFAR=y

#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
CONFIG_PINCTRL=y

#
# Pin controllers
#
CONFIG_PINMUX=y
CONFIG_PINCONF=y
CONFIG_GENERIC_PINCONF=y
# CONFIG_DEBUG_PINCTRL is not set
CONFIG_PINCTRL_AS3722=y
CONFIG_PINCTRL_AT91=y
CONFIG_PINCTRL_AT91PIO4=y
# CONFIG_PINCTRL_AMD is not set
CONFIG_PINCTRL_DIGICOLOR=y
CONFIG_PINCTRL_MESON=y
CONFIG_PINCTRL_ROCKCHIP=y
CONFIG_PINCTRL_SINGLE=y
CONFIG_PINCTRL_SIRF=y
CONFIG_PINCTRL_ST=y
CONFIG_PINCTRL_PALMAS=y
CONFIG_PINCTRL_ZYNQ=y
CONFIG_PINCTRL_BCM281XX=y
CONFIG_PINCTRL_BCM2835=y
CONFIG_PINCTRL_IPROC_GPIO=y
CONFIG_PINCTRL_CYGNUS_MUX=y
CONFIG_PINCTRL_NSP_GPIO=y
# CONFIG_PINCTRL_NS2_MUX is not set
CONFIG_PINCTRL_BERLIN=y
CONFIG_PINCTRL_BERLIN_BG2=y
CONFIG_PINCTRL_BERLIN_BG2CD=y
CONFIG_PINCTRL_BERLIN_BG2Q=y
# CONFIG_PINCTRL_BERLIN_BG4CT is not set
CONFIG_PINCTRL_IMX=y
CONFIG_PINCTRL_IMX50=y
CONFIG_PINCTRL_IMX51=y
CONFIG_PINCTRL_IMX53=y
CONFIG_PINCTRL_IMX6Q=y
CONFIG_PINCTRL_IMX6SL=y
CONFIG_PINCTRL_IMX6SX=y
CONFIG_PINCTRL_IMX6UL=y
CONFIG_PINCTRL_IMX7D=y
CONFIG_PINCTRL_VF610=y
CONFIG_PINCTRL_MVEBU=y
CONFIG_PINCTRL_DOVE=y
CONFIG_PINCTRL_ARMADA_370=y
CONFIG_PINCTRL_ARMADA_375=y
CONFIG_PINCTRL_ARMADA_38X=y
CONFIG_PINCTRL_ARMADA_39X=y
CONFIG_PINCTRL_ARMADA_XP=y
CONFIG_PINCTRL_ABX500=y
CONFIG_PINCTRL_AB8500=y
CONFIG_PINCTRL_AB8540=y
CONFIG_PINCTRL_AB9540=y
CONFIG_PINCTRL_AB8505=y
CONFIG_PINCTRL_NOMADIK=y
CONFIG_PINCTRL_DB8500=y
CONFIG_PINCTRL_DB8540=y
CONFIG_PINCTRL_MSM=y
CONFIG_PINCTRL_APQ8064=y
CONFIG_PINCTRL_APQ8084=y
# CONFIG_PINCTRL_IPQ4019 is not set
CONFIG_PINCTRL_IPQ8064=y
CONFIG_PINCTRL_MSM8660=y
CONFIG_PINCTRL_MSM8960=y
CONFIG_PINCTRL_MSM8X74=y
CONFIG_PINCTRL_MSM8916=y
# CONFIG_PINCTRL_MSM8996 is not set
CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
CONFIG_PINCTRL_QCOM_SSBI_PMIC=y
CONFIG_PINCTRL_SAMSUNG=y
CONFIG_PINCTRL_EXYNOS=y
CONFIG_PINCTRL_EXYNOS5440=y
CONFIG_PINCTRL_SH_PFC=y
CONFIG_PINCTRL_SH_PFC_GPIO=y
CONFIG_PINCTRL_PFC_EMEV2=y
CONFIG_PINCTRL_PFC_R8A73A4=y
CONFIG_PINCTRL_PFC_R8A7740=y
CONFIG_PINCTRL_PFC_R8A7778=y
CONFIG_PINCTRL_PFC_R8A7779=y
CONFIG_PINCTRL_PFC_R8A7790=y
CONFIG_PINCTRL_PFC_R8A7791=y
CONFIG_PINCTRL_PFC_R8A7793=y
CONFIG_PINCTRL_PFC_R8A7794=y
CONFIG_PINCTRL_PFC_SH73A0=y
CONFIG_PINCTRL_SPEAR=y
CONFIG_PINCTRL_SPEAR1310=y
CONFIG_PINCTRL_SPEAR1340=y
CONFIG_PINCTRL_SPEAR_PLGPIO=y
CONFIG_PINCTRL_SUNXI=y
CONFIG_PINCTRL_SUN4I_A10=y
CONFIG_PINCTRL_SUN5I_A10S=y
CONFIG_PINCTRL_SUN5I_A13=y
CONFIG_PINCTRL_SUN6I_A31=y
CONFIG_PINCTRL_SUN6I_A31S=y
CONFIG_PINCTRL_SUN6I_A31_R=y
CONFIG_PINCTRL_SUN7I_A20=y
CONFIG_PINCTRL_SUN8I_A23=y
CONFIG_PINCTRL_SUN8I_A33=y
CONFIG_PINCTRL_SUN8I_A83T=y
CONFIG_PINCTRL_SUN8I_A23_R=y
CONFIG_PINCTRL_SUN8I_H3=y
CONFIG_PINCTRL_SUN8I_H3_R=y
CONFIG_PINCTRL_SUN9I_A80=y
CONFIG_PINCTRL_SUN9I_A80_R=y
CONFIG_PINCTRL_TEGRA=y
CONFIG_PINCTRL_TEGRA20=y
CONFIG_PINCTRL_TEGRA30=y
CONFIG_PINCTRL_TEGRA114=y
CONFIG_PINCTRL_TEGRA124=y
CONFIG_PINCTRL_TEGRA_XUSB=y
CONFIG_PINCTRL_UNIPHIER=y
CONFIG_PINCTRL_UNIPHIER_LD4=y
CONFIG_PINCTRL_UNIPHIER_PRO4=y
CONFIG_PINCTRL_UNIPHIER_SLD8=y
CONFIG_PINCTRL_UNIPHIER_PRO5=y
CONFIG_PINCTRL_UNIPHIER_PXS2=y
CONFIG_PINCTRL_UNIPHIER_LD6B=y
# CONFIG_PINCTRL_WM8850 is not set
CONFIG_PINCTRL_MTK=y
CONFIG_PINCTRL_MT2701=y
CONFIG_PINCTRL_MT7623=y
CONFIG_PINCTRL_MT8135=y
CONFIG_PINCTRL_MT8127=y
# CONFIG_PINCTRL_MT6397 is not set
CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_DEVRES=y
CONFIG_OF_GPIO=y
CONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
CONFIG_GPIO_SYSFS=y
CONFIG_GPIO_GENERIC=y

#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
CONFIG_GPIO_BCM_KONA=y
CONFIG_GPIO_BRCMSTB=y
CONFIG_GPIO_DAVINCI=y
CONFIG_GPIO_DWAPB=y
CONFIG_GPIO_EM=y
CONFIG_GPIO_GENERIC_PLATFORM=y
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_MPC8XXX is not set
CONFIG_GPIO_MVEBU=y
CONFIG_GPIO_MXC=y
CONFIG_GPIO_OMAP=y
CONFIG_GPIO_PL061=y
CONFIG_GPIO_RCAR=y
CONFIG_GPIO_SPEAR_SPICS=y
CONFIG_GPIO_SYSCON=y
CONFIG_GPIO_TEGRA=y
# CONFIG_GPIO_TS4800 is not set
CONFIG_GPIO_VF610=y
# CONFIG_GPIO_VX855 is not set
CONFIG_GPIO_XILINX=y
# CONFIG_GPIO_ZEVIO is not set
CONFIG_GPIO_ZYNQ=y
# CONFIG_GPIO_ZX is not set

#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADP5588 is not set
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_GPIO_PCF857X=y
# CONFIG_GPIO_SX150X is not set
# CONFIG_GPIO_TPIC2810 is not set

#
# MFD GPIO expanders
#
CONFIG_GPIO_PALMAS=y
# CONFIG_GPIO_STMPE is not set
# CONFIG_GPIO_TPS65218 is not set
CONFIG_GPIO_TPS6586X=y
CONFIG_GPIO_TPS65910=y
CONFIG_GPIO_TWL4030=y

#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_RDC321X is not set

#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set

#
# SPI or I2C GPIO expanders
#
# CONFIG_GPIO_MCP23S08 is not set

#
# USB GPIO expanders
#
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
CONFIG_BATTERY_SBS=y
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_AXP288_FUEL_GAUGE is not set
CONFIG_BATTERY_MAX17040=m
CONFIG_BATTERY_MAX17042=m
# CONFIG_CHARGER_ISP1704 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_TWL4030 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_MANAGER is not set
CONFIG_CHARGER_MAX14577=m
CONFIG_CHARGER_MAX77693=m
CONFIG_CHARGER_MAX8997=m
# CONFIG_CHARGER_QCOM_SMBB is not set
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24190 is not set
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_SMB347 is not set
CONFIG_CHARGER_TPS65090=y
# CONFIG_CHARGER_TPS65217 is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_AB8500_BM is not set
# CONFIG_CHARGER_RT9455 is not set
CONFIG_AXP20X_POWER=m
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_AS3722=y
CONFIG_POWER_RESET_AT91_POWEROFF=y
CONFIG_POWER_RESET_AT91_RESET=y
CONFIG_POWER_RESET_AT91_SAMA5D2_SHDWC=y
CONFIG_POWER_RESET_BRCMSTB=y
CONFIG_POWER_RESET_GPIO=y
CONFIG_POWER_RESET_GPIO_RESTART=y
CONFIG_POWER_RESET_HISI=y
# CONFIG_POWER_RESET_IMX is not set
# CONFIG_POWER_RESET_MSM is not set
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_QNAP is not set
# CONFIG_POWER_RESET_RESTART is not set
CONFIG_POWER_RESET_ST=y
# CONFIG_POWER_RESET_VERSATILE is not set
CONFIG_POWER_RESET_VEXPRESS=y
CONFIG_POWER_RESET_KEYSTONE=y
CONFIG_POWER_RESET_SYSCON=y
CONFIG_POWER_RESET_SYSCON_POWEROFF=y
CONFIG_POWER_RESET_RMOBILE=y
CONFIG_POWER_AVS=y
CONFIG_ROCKCHIP_IODOMAIN=y
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
CONFIG_SENSORS_IIO_HWMON=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_POWR1220 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4260 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
CONFIG_SENSORS_LM90=y
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set
CONFIG_SENSORS_LM95245=y
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
CONFIG_SENSORS_NTC_THERMISTOR=m
# CONFIG_SENSORS_NCT6683 is not set
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
CONFIG_SENSORS_PWM_FAN=m
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SHTC1 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH56XX_COMMON is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_ADC128D818 is not set
# CONFIG_SENSORS_ADS1015 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set
CONFIG_SENSORS_INA2XX=m
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VEXPRESS is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_OF=y
# CONFIG_THERMAL_WRITABLE_TRIPS is not set
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_DEFAULT_GOV_POWER_ALLOCATOR is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_POWER_ALLOCATOR is not set
CONFIG_CPU_THERMAL=y
# CONFIG_CLOCK_THERMAL is not set
# CONFIG_DEVFREQ_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_HISI_THERMAL is not set
# CONFIG_IMX_THERMAL is not set
# CONFIG_SPEAR_THERMAL is not set
CONFIG_ROCKCHIP_THERMAL=y
CONFIG_RCAR_THERMAL=y
# CONFIG_DOVE_THERMAL is not set
CONFIG_DB8500_THERMAL=y
CONFIG_ARMADA_THERMAL=y
CONFIG_DB8500_CPUFREQ_COOLING=y

#
# ACPI INT340X thermal drivers
#
CONFIG_MTK_THERMAL=y

#
# Texas Instruments thermal drivers
#
# CONFIG_TI_SOC_THERMAL is not set

#
# Samsung thermal drivers
#
CONFIG_EXYNOS_THERMAL=y

#
# STMicroelectronics thermal drivers
#
CONFIG_ST_THERMAL=y
CONFIG_ST_THERMAL_SYSCFG=y
CONFIG_ST_THERMAL_MEMMAP=y

#
# NVIDIA Tegra thermal drivers
#
# CONFIG_TEGRA_SOCTHERM is not set
# CONFIG_QCOM_SPMI_TEMP_ALARM is not set
# CONFIG_GENERIC_ADC_THERMAL is not set
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_WATCHDOG_SYSFS is not set

#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
CONFIG_DA9063_WATCHDOG=m
# CONFIG_GPIO_WATCHDOG is not set
CONFIG_XILINX_WATCHDOG=y
# CONFIG_ZIIRAVE_WATCHDOG is not set
CONFIG_ARM_SP805_WATCHDOG=y
CONFIG_AT91SAM9X_WATCHDOG=y
CONFIG_SAMA5D4_WATCHDOG=y
# CONFIG_CADENCE_WATCHDOG is not set
CONFIG_HAVE_S3C2410_WATCHDOG=y
# CONFIG_S3C2410_WATCHDOG is not set
CONFIG_DW_WATCHDOG=y
# CONFIG_OMAP_WATCHDOG is not set
CONFIG_DAVINCI_WATCHDOG=m
CONFIG_ORION_WATCHDOG=y
CONFIG_SUNXI_WATCHDOG=y
# CONFIG_TWL4030_WATCHDOG is not set
# CONFIG_TS4800_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
CONFIG_IMX2_WDT=y
CONFIG_UX500_WATCHDOG=y
CONFIG_SIRFSOC_WATCHDOG=y
CONFIG_ST_LPC_WATCHDOG=y
CONFIG_TEGRA_WATCHDOG=m
# CONFIG_QCOM_WDT is not set
CONFIG_MESON_WATCHDOG=y
# CONFIG_MEDIATEK_WATCHDOG is not set
CONFIG_DIGICOLOR_WATCHDOG=y
# CONFIG_ATLAS7_WATCHDOG is not set
# CONFIG_RENESAS_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_BCM47XX_WDT is not set
CONFIG_BCM2835_WDT=y
# CONFIG_BCM_KONA_WDT is not set
# CONFIG_BCM7038_WDT is not set
# CONFIG_MEN_A21_WDT is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y

#
# Broadcom specific AMBA
#
CONFIG_BCMA=y
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
CONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not set
CONFIG_BCMA_DRIVER_PCI=y
# CONFIG_BCMA_DRIVER_GMAC_CMN is not set
# CONFIG_BCMA_DRIVER_GPIO is not set
# CONFIG_BCMA_DEBUG is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_ACT8945A is not set
CONFIG_MFD_AS3711=y
CONFIG_MFD_AS3722=y
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
CONFIG_MFD_ATMEL_FLEXCOM=y
CONFIG_MFD_ATMEL_HLCDC=m
CONFIG_MFD_BCM590XX=y
CONFIG_MFD_AXP20X=m
CONFIG_MFD_AXP20X_I2C=m
CONFIG_MFD_AXP20X_RSB=m
CONFIG_MFD_CROS_EC=m
CONFIG_MFD_CROS_EC_I2C=m
CONFIG_MFD_CROS_EC_SPI=m
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
CONFIG_MFD_DA9063=m
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_MFD_HI655X_PMIC is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_LPC_ICH is not set
# CONFIG_LPC_SCH is not set
# CONFIG_INTEL_SOC_PMIC is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
CONFIG_MFD_MAX14577=y
# CONFIG_MFD_MAX77620 is not set
CONFIG_MFD_MAX77686=y
CONFIG_MFD_MAX77693=y
# CONFIG_MFD_MAX77843 is not set
CONFIG_MFD_MAX8907=y
# CONFIG_MFD_MAX8925 is not set
CONFIG_MFD_MAX8997=y
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_UCB1400_CORE is not set
CONFIG_MFD_PM8XXX=y
CONFIG_MFD_PM8921_CORE=y
CONFIG_MFD_QCOM_RPM=y
CONFIG_MFD_SPMI_PMIC=y
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RTSX_PCI is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RTSX_USB is not set
# CONFIG_MFD_RC5T583 is not set
CONFIG_MFD_RK808=y
# CONFIG_MFD_RN5T618 is not set
CONFIG_MFD_SEC_CORE=y
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_SMSC is not set
CONFIG_ABX500_CORE=y
# CONFIG_AB3100_CORE is not set
CONFIG_AB8500_CORE=y
CONFIG_AB8500_DEBUG=y
CONFIG_AB8500_GPADC=y
CONFIG_MFD_DB8500_PRCMU=y
CONFIG_MFD_STMPE=y

#
# STMicroelectronics STMPE Interface Drivers
#
CONFIG_STMPE_I2C=y
# CONFIG_STMPE_SPI is not set
CONFIG_MFD_SUN6I_PRCM=y
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
CONFIG_MFD_OMAP_USB_HOST=y
CONFIG_MFD_PALMAS=y
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
CONFIG_MFD_TPS65090=y
CONFIG_MFD_TPS65217=y
CONFIG_MFD_TPS65218=y
CONFIG_MFD_TPS6586X=y
CONFIG_MFD_TPS65910=y
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
CONFIG_TWL4030_CORE=y
CONFIG_TWL4030_POWER=y
# CONFIG_MFD_TWL4030_AUDIO is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
CONFIG_MFD_VEXPRESS_SYSREG=y
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
CONFIG_REGULATOR_ACT8865=y
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_ANATOP is not set
CONFIG_REGULATOR_AB8500=y
CONFIG_REGULATOR_AS3711=y
CONFIG_REGULATOR_AS3722=y
CONFIG_REGULATOR_AXP20X=m
CONFIG_REGULATOR_BCM590XX=y
# CONFIG_REGULATOR_DA9063 is not set
CONFIG_REGULATOR_DA9210=y
# CONFIG_REGULATOR_DA9211 is not set
CONFIG_REGULATOR_DBX500_PRCMU=y
CONFIG_REGULATOR_DB8500_PRCMU=y
CONFIG_REGULATOR_FAN53555=y
CONFIG_REGULATOR_GPIO=y
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
CONFIG_REGULATOR_LP872X=y
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
CONFIG_REGULATOR_MAX14577=m
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
CONFIG_REGULATOR_MAX8907=y
# CONFIG_REGULATOR_MAX8952 is not set
CONFIG_REGULATOR_MAX8973=y
CONFIG_REGULATOR_MAX8997=m
CONFIG_REGULATOR_MAX77686=y
CONFIG_REGULATOR_MAX77693=m
CONFIG_REGULATOR_MAX77802=m
# CONFIG_REGULATOR_MT6311 is not set
CONFIG_REGULATOR_PALMAS=y
CONFIG_REGULATOR_PBIAS=y
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PV88060 is not set
# CONFIG_REGULATOR_PV88080 is not set
# CONFIG_REGULATOR_PV88090 is not set
CONFIG_REGULATOR_PWM=y
CONFIG_REGULATOR_QCOM_RPM=y
CONFIG_REGULATOR_QCOM_SMD_RPM=y
# CONFIG_REGULATOR_QCOM_SPMI is not set
CONFIG_REGULATOR_RK808=y
# CONFIG_REGULATOR_S2MPA01 is not set
CONFIG_REGULATOR_S2MPS11=y
CONFIG_REGULATOR_S5M8767=y
CONFIG_REGULATOR_TI_ABB=y
CONFIG_REGULATOR_TPS51632=y
CONFIG_REGULATOR_TPS62360=y
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
CONFIG_REGULATOR_TPS65090=y
CONFIG_REGULATOR_TPS65217=y
CONFIG_REGULATOR_TPS65218=y
# CONFIG_REGULATOR_TPS6524X is not set
CONFIG_REGULATOR_TPS6586X=y
CONFIG_REGULATOR_TPS65910=y
CONFIG_REGULATOR_TWL4030=y
CONFIG_REGULATOR_VEXPRESS=y
CONFIG_MEDIA_SUPPORT=m

#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
# CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set
# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set
# CONFIG_MEDIA_RADIO_SUPPORT is not set
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_RC_SUPPORT is not set
CONFIG_MEDIA_CONTROLLER=y
# CONFIG_MEDIA_CONTROLLER_DVB is not set
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2_SUBDEV_API=y
CONFIG_VIDEO_V4L2=m
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_V4L2_MEM2MEM_DEV=m
# CONFIG_V4L2_FLASH_LED_CLASS is not set
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_DMA_CONTIG=m
CONFIG_VIDEOBUF2_VMALLOC=m
# CONFIG_TTPCI_EEPROM is not set

#
# Media drivers
#
CONFIG_MEDIA_USB_SUPPORT=y

#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_BENQ is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_CPIA1 is not set
# CONFIG_USB_GSPCA_DTCS033 is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_JL2005BCD is not set
# CONFIG_USB_GSPCA_KINECT is not set
# CONFIG_USB_GSPCA_KONICA is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_NW80X is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_OV534_9 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7302 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SE401 is not set
# CONFIG_USB_GSPCA_SN9C2028 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SPCA1528 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_SQ930X is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_STK1135 is not set
# CONFIG_USB_GSPCA_STV0680 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TOPRO is not set
# CONFIG_USB_GSPCA_TOUPTEK is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_VICAM is not set
# CONFIG_USB_GSPCA_XIRLINK_CIT is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_USB_PWC is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
# CONFIG_VIDEO_USBTV is not set

#
# Webcam, TV (analog/digital) USB devices
#
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_MEDIA_PCI_SUPPORT is not set
CONFIG_V4L_PLATFORM_DRIVERS=y
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_VIDEO_SH_VOU is not set
CONFIG_SOC_CAMERA=m
CONFIG_SOC_CAMERA_SCALE_CROP=m
CONFIG_SOC_CAMERA_PLATFORM=m
CONFIG_VIDEO_RCAR_VIN=m
# CONFIG_VIDEO_SH_MOBILE_CSI2 is not set
# CONFIG_VIDEO_SH_MOBILE_CEU is not set
CONFIG_VIDEO_ATMEL_ISI=m
# CONFIG_VIDEO_SAMSUNG_EXYNOS4_IS is not set
# CONFIG_VIDEO_SAMSUNG_S5P_TV is not set
# CONFIG_VIDEO_AM437X_VPFE is not set
# CONFIG_VIDEO_XILINX is not set
# CONFIG_VIDEO_TI_CAL is not set
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_CODA is not set
# CONFIG_VIDEO_MEM2MEM_DEINTERLACE is not set
# CONFIG_VIDEO_SAMSUNG_S5P_G2D is not set
# CONFIG_VIDEO_SAMSUNG_S5P_JPEG is not set
# CONFIG_VIDEO_SAMSUNG_S5P_MFC is not set
# CONFIG_VIDEO_SAMSUNG_EXYNOS_GSC is not set
# CONFIG_VIDEO_STI_BDISP is not set
# CONFIG_VIDEO_SH_VEU is not set
CONFIG_VIDEO_RENESAS_JPU=m
CONFIG_VIDEO_RENESAS_VSP1=m
# CONFIG_VIDEO_TI_VPE is not set
# CONFIG_V4L_TEST_DRIVERS is not set

#
# Supported MMC/SDIO adapters
#
# CONFIG_CYPRESS_FIRMWARE is not set

#
# Media ancillary drivers (tuners, sensors, i2c, frontends)
#
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set

#
# Encoders, decoders, sensors and other helper chips
#

#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_MSP3400 is not set
# CONFIG_VIDEO_CS3308 is not set
# CONFIG_VIDEO_CS5345 is not set
# CONFIG_VIDEO_CS53L32A is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_UDA1342 is not set
# CONFIG_VIDEO_WM8775 is not set
# CONFIG_VIDEO_WM8739 is not set
# CONFIG_VIDEO_VP27SMPX is not set
# CONFIG_VIDEO_SONY_BTF_MPX is not set

#
# RDS decoders
#
# CONFIG_VIDEO_SAA6588 is not set

#
# Video decoders
#
CONFIG_VIDEO_ADV7180=m
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV7604 is not set
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_KS0127 is not set
CONFIG_VIDEO_ML86V7667=m
# CONFIG_VIDEO_SAA7110 is not set
# CONFIG_VIDEO_SAA711X is not set
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_VPX3220 is not set

#
# Video and audio decoders
#
# CONFIG_VIDEO_SAA717X is not set
# CONFIG_VIDEO_CX25840 is not set

#
# Video encoders
#
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_ADV7511 is not set
# CONFIG_VIDEO_AD9389B is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_THS8200 is not set

#
# Camera sensor devices
#
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV7640 is not set
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9V011 is not set
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_SMIAPP is not set
# CONFIG_VIDEO_S5C73M3 is not set

#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_AS3645A is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set

#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set

#
# Audio/Video compression chips
#
# CONFIG_VIDEO_SAA6752HS is not set

#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_THS7303 is not set
# CONFIG_VIDEO_M52790 is not set

#
# Sensors used on soc_camera driver
#

#
# soc_camera sensor drivers
#
# CONFIG_SOC_CAMERA_IMX074 is not set
# CONFIG_SOC_CAMERA_MT9M001 is not set
# CONFIG_SOC_CAMERA_MT9M111 is not set
# CONFIG_SOC_CAMERA_MT9T031 is not set
# CONFIG_SOC_CAMERA_MT9T112 is not set
# CONFIG_SOC_CAMERA_MT9V022 is not set
# CONFIG_SOC_CAMERA_OV2640 is not set
# CONFIG_SOC_CAMERA_OV5642 is not set
# CONFIG_SOC_CAMERA_OV6650 is not set
# CONFIG_SOC_CAMERA_OV772X is not set
# CONFIG_SOC_CAMERA_OV9640 is not set
# CONFIG_SOC_CAMERA_OV9740 is not set
# CONFIG_SOC_CAMERA_RJ54N1 is not set
# CONFIG_SOC_CAMERA_TW9910 is not set

#
# Customise DVB Frontends
#
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_V4L=m
CONFIG_DVB_TUNER_DIB0070=m
CONFIG_DVB_TUNER_DIB0090=m

#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set

#
# Graphics support
#
CONFIG_HAVE_FB_ATMEL=y
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
CONFIG_TEGRA_HOST1X=y
CONFIG_TEGRA_HOST1X_FIREWALL=y
# CONFIG_IMX_IPUV3_CORE is not set
CONFIG_DRM=y
CONFIG_DRM_MIPI_DSI=y
# CONFIG_DRM_DP_AUX_CHARDEV is not set
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y
CONFIG_DRM_FBDEV_EMULATION=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_DRM_TTM=m
CONFIG_DRM_GEM_CMA_HELPER=y
CONFIG_DRM_KMS_CMA_HELPER=y

#
# I2C encoder or helper chips
#
CONFIG_DRM_I2C_ADV7511=m
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set

#
# ACP (Audio CoProcessor) Configuration
#
CONFIG_DRM_NOUVEAU=m
CONFIG_NOUVEAU_PLATFORM_DRIVER=y
CONFIG_NOUVEAU_DEBUG=5
CONFIG_NOUVEAU_DEBUG_DEFAULT=3
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_DRM_VGEM is not set
CONFIG_DRM_EXYNOS=m

#
# CRTCs
#
CONFIG_DRM_EXYNOS_FIMD=y
# CONFIG_DRM_EXYNOS5433_DECON is not set
# CONFIG_DRM_EXYNOS7_DECON is not set
# CONFIG_DRM_EXYNOS_MIXER is not set
# CONFIG_DRM_EXYNOS_VIDI is not set

#
# Encoders and Bridges
#
# CONFIG_DRM_EXYNOS_DPI is not set
CONFIG_DRM_EXYNOS_DSI=y
CONFIG_DRM_EXYNOS_DP=y

#
# Sub-drivers
#
# CONFIG_DRM_EXYNOS_G2D is not set
# CONFIG_DRM_EXYNOS_IPP is not set
CONFIG_DRM_ROCKCHIP=m
CONFIG_ROCKCHIP_ANALOGIX_DP=m
CONFIG_ROCKCHIP_DW_HDMI=m
CONFIG_ROCKCHIP_DW_MIPI_DSI=m
CONFIG_ROCKCHIP_INNO_HDMI=m
# CONFIG_DRM_UDL is not set
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_DRM_ARMADA is not set
CONFIG_DRM_ATMEL_HLCDC=m
CONFIG_DRM_RCAR_DU=m
CONFIG_DRM_RCAR_HDMI=y
CONFIG_DRM_RCAR_LVDS=y
# CONFIG_DRM_RCAR_VSP is not set
# CONFIG_DRM_SHMOBILE is not set
# CONFIG_DRM_SUN4I is not set
# CONFIG_DRM_OMAP is not set
# CONFIG_DRM_TILCDC is not set
# CONFIG_DRM_QXL is not set
# CONFIG_DRM_BOCHS is not set
# CONFIG_DRM_VIRTIO_GPU is not set
CONFIG_DRM_MSM=y
# CONFIG_DRM_MSM_REGISTER_LOGGING is not set
CONFIG_DRM_MSM_HDMI_HDCP=y
CONFIG_DRM_MSM_DSI=y
CONFIG_DRM_MSM_DSI_PLL=y
CONFIG_DRM_MSM_DSI_28NM_PHY=y
CONFIG_DRM_MSM_DSI_20NM_PHY=y
CONFIG_DRM_MSM_DSI_28NM_8960_PHY=y
# CONFIG_DRM_FSL_DCU is not set
CONFIG_DRM_TEGRA=y
# CONFIG_DRM_TEGRA_DEBUG is not set
# CONFIG_DRM_TEGRA_STAGING is not set
CONFIG_DRM_PANEL=y

#
# Display Panels
#
CONFIG_DRM_PANEL_SIMPLE=y
# CONFIG_DRM_PANEL_SAMSUNG_LD9040 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00 is not set
CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0=m
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set
# CONFIG_DRM_PANEL_SHARP_LS043T1LE01 is not set
CONFIG_DRM_BRIDGE=y

#
# Display Interface Bridges
#
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
CONFIG_DRM_DW_HDMI=m
# CONFIG_DRM_DW_HDMI_AHB_AUDIO is not set
CONFIG_DRM_NXP_PTN3460=m
CONFIG_DRM_PARADE_PS8622=m
CONFIG_DRM_ANALOGIX_DP=m
# CONFIG_DRM_STI is not set
CONFIG_DRM_VC4=y
# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_ARCPGU is not set
# CONFIG_DRM_MEDIATEK is not set

#
# Frame buffer Devices
#
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_CMDLINE=y
CONFIG_FB_NOTIFY=y
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=y
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
CONFIG_FB_ARMCLCD=y
CONFIG_PLAT_VERSATILE_CLCD=y
# CONFIG_FB_IMX is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_ATMEL is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_VT8500 is not set
CONFIG_FB_WM8505=y
# CONFIG_FB_WMT_GE_ROPS is not set
CONFIG_FB_SH_MOBILE_LCDC=y
# CONFIG_FB_S3C is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_XILINX is not set
# CONFIG_FB_DA8XX is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
CONFIG_FB_MX3=y
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_AUO_K190X is not set
# CONFIG_FB_MXS is not set
CONFIG_FB_SIMPLE=y
# CONFIG_FB_OMAP2 is not set
# CONFIG_EXYNOS_VIDEO is not set
CONFIG_FB_SH_MOBILE_MERAM=y
# CONFIG_FB_SSD1307 is not set
# CONFIG_FB_SM712 is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not set
CONFIG_LCD_PLATFORM=m
# CONFIG_LCD_S6E63M0 is not set
# CONFIG_LCD_LD9040 is not set
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
CONFIG_BACKLIGHT_PWM=y
# CONFIG_BACKLIGHT_PM8941_WLED is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_PANDORA is not set
# CONFIG_BACKLIGHT_TPS65217 is not set
CONFIG_BACKLIGHT_AS3711=y
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEOMODE_HELPERS=y
CONFIG_HDMI=y

#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_LOGO is not set
CONFIG_SOUND=m
# CONFIG_SOUND_OSS_CORE is not set
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_DMAENGINE_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
CONFIG_SND_JACK_INPUT_DEV=y
# CONFIG_SND_SEQUENCER is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
CONFIG_SND_PCM_TIMER=y
# CONFIG_SND_HRTIMER is not set
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_MAX_CARDS=32
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_PROC_FS=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
# CONFIG_SND_RAWMIDI_SEQ is not set
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SE6X is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set

#
# HD-Audio
#
CONFIG_SND_HDA=m
# CONFIG_SND_HDA_INTEL is not set
CONFIG_SND_HDA_TEGRA=m
# CONFIG_SND_HDA_HWDEP is not set
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=1
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=m
# CONFIG_SND_HDA_CODEC_ANALOG is not set
# CONFIG_SND_HDA_CODEC_SIGMATEL is not set
# CONFIG_SND_HDA_CODEC_VIA is not set
CONFIG_SND_HDA_CODEC_HDMI=m
# CONFIG_SND_HDA_CODEC_CIRRUS is not set
# CONFIG_SND_HDA_CODEC_CONEXANT is not set
# CONFIG_SND_HDA_CODEC_CA0110 is not set
# CONFIG_SND_HDA_CODEC_CA0132 is not set
# CONFIG_SND_HDA_CODEC_CMEDIA is not set
# CONFIG_SND_HDA_CODEC_SI3054 is not set
CONFIG_SND_HDA_GENERIC=m
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDA_CORE=m
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_ARM=y
# CONFIG_SND_ARMAACI is not set

#
# Atmel devices (AVR32 and AT91)
#
# CONFIG_SND_ATMEL_AC97C is not set
CONFIG_SND_SPI=y
# CONFIG_SND_AT73C213 is not set
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_BCD2000 is not set
# CONFIG_SND_USB_POD is not set
# CONFIG_SND_USB_PODHD is not set
# CONFIG_SND_USB_TONEPORT is not set
# CONFIG_SND_USB_VARIAX is not set
CONFIG_SND_SOC=m
CONFIG_SND_SOC_AC97_BUS=y
CONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=y
# CONFIG_SND_SOC_ADI is not set
# CONFIG_SND_SOC_AMD_ACP is not set
CONFIG_SND_ATMEL_SOC=m
CONFIG_SND_ATMEL_SOC_DMA=m
CONFIG_SND_ATMEL_SOC_SSC_DMA=m
CONFIG_SND_ATMEL_SOC_SSC=m
# CONFIG_SND_AT91_SOC_SAM9G20_WM8731 is not set
CONFIG_SND_ATMEL_SOC_WM8904=m
# CONFIG_SND_AT91_SOC_SAM9X5_WM8731 is not set
# CONFIG_SND_ATMEL_SOC_CLASSD is not set
CONFIG_SND_ATMEL_SOC_PDMIC=m
CONFIG_SND_BCM2835_SOC_I2S=m
# CONFIG_SND_EDMA_SOC is not set
# CONFIG_SND_DESIGNWARE_I2S is not set

#
# SoC Audio for Freescale CPUs
#

#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
CONFIG_SND_SOC_FSL_SAI=m
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# CONFIG_SND_IMX_SOC is not set
# CONFIG_SND_OMAP_SOC is not set
# CONFIG_SND_KIRKWOOD_SOC is not set
# CONFIG_SND_SOC_IMG is not set
# CONFIG_SND_SOC_MEDIATEK is not set
# CONFIG_SND_SOC_QCOM is not set
CONFIG_SND_SOC_ROCKCHIP=m
CONFIG_SND_SOC_ROCKCHIP_I2S=m
CONFIG_SND_SOC_ROCKCHIP_SPDIF=m
CONFIG_SND_SOC_ROCKCHIP_MAX98090=m
CONFIG_SND_SOC_ROCKCHIP_RT5645=m
CONFIG_SND_SOC_SAMSUNG=m
CONFIG_SND_SAMSUNG_I2S=m
# CONFIG_SND_SOC_SAMSUNG_SMDK_WM8994 is not set
# CONFIG_SND_SOC_SAMSUNG_SMDK_SPDIF is not set
# CONFIG_SND_SOC_SMDK_WM8994_PCM is not set
CONFIG_SND_SOC_SNOW=m
CONFIG_SND_SOC_ODROIDX2=m
# CONFIG_SND_SOC_ARNDALE_RT5631_ALC5631 is not set

#
# SoC Audio support for SuperH
#
CONFIG_SND_SOC_SH4_FSI=m
CONFIG_SND_SOC_RCAR=m
CONFIG_SND_SOC_RSRC_CARD=m
# CONFIG_SND_SOC_SIRF is not set
# CONFIG_SND_SOC_STI is not set

#
# Allwinner SoC Audio support
#
CONFIG_SND_SUN4I_CODEC=m
# CONFIG_SND_SUN4I_SPDIF is not set
CONFIG_SND_SOC_TEGRA=m
CONFIG_SND_SOC_TEGRA20_AC97=m
CONFIG_SND_SOC_TEGRA20_DAS=m
CONFIG_SND_SOC_TEGRA20_I2S=m
CONFIG_SND_SOC_TEGRA20_SPDIF=m
CONFIG_SND_SOC_TEGRA30_AHUB=m
CONFIG_SND_SOC_TEGRA30_I2S=m
CONFIG_SND_SOC_TEGRA_RT5640=m
CONFIG_SND_SOC_TEGRA_WM8753=m
CONFIG_SND_SOC_TEGRA_WM8903=m
CONFIG_SND_SOC_TEGRA_WM9712=m
CONFIG_SND_SOC_TEGRA_TRIMSLICE=m
CONFIG_SND_SOC_TEGRA_ALC5632=m
CONFIG_SND_SOC_TEGRA_MAX98090=m
# CONFIG_SND_SOC_TEGRA_RT5677 is not set
# CONFIG_SND_SOC_UX500 is not set
# CONFIG_SND_SOC_XTFPGA_I2S is not set
CONFIG_SND_SOC_I2C_AND_SPI=m

#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
CONFIG_SND_SOC_AK4642=m
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_ALC5623 is not set
CONFIG_SND_SOC_ALC5632=m
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_ES8328 is not set
# CONFIG_SND_SOC_GTM601 is not set
# CONFIG_SND_SOC_INNO_RK3036 is not set
CONFIG_SND_SOC_MAX98090=m
CONFIG_SND_SOC_MAX98095=m
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
CONFIG_SND_SOC_RL6231=m
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not set
CONFIG_SND_SOC_RT5640=m
CONFIG_SND_SOC_RT5645=m
# CONFIG_SND_SOC_RT5677_SPI is not set
CONFIG_SND_SOC_SGTL5000=m
# CONFIG_SND_SOC_SIRF_AUDIO_CODEC is not set
CONFIG_SND_SOC_SPDIF=m
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TFA9879 is not set
CONFIG_SND_SOC_TLV320AIC23=m
CONFIG_SND_SOC_TLV320AIC23_I2C=m
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC3X is not set
CONFIG_SND_SOC_TS3A227E=m
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731 is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
CONFIG_SND_SOC_WM8753=m
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
CONFIG_SND_SOC_WM8903=m
CONFIG_SND_SOC_WM8904=m
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
CONFIG_SND_SOC_WM8978=m
CONFIG_SND_SOC_WM9712=m
# CONFIG_SND_SOC_TPA6130A2 is not set
CONFIG_SND_SIMPLE_CARD=m
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m

#
# HID support
#
CONFIG_HID=y
# CONFIG_HID_BATTERY_STRENGTH is not set
# CONFIG_HIDRAW is not set
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=y

#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_BETOP_FF is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_CORSAIR is not set
# CONFIG_HID_PRODIKEYS is not set
# CONFIG_HID_CMEDIA is not set
# CONFIG_HID_CP2112 is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not set
# CONFIG_HID_GFRM is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_GT683R is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set

#
# USB HID support
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set

#
# I2C HID support
#
# CONFIG_I2C_HID is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_PCI=y
CONFIG_USB_XHCI_PLATFORM=y
# CONFIG_USB_XHCI_MTK is not set
CONFIG_USB_XHCI_MVEBU=y
CONFIG_USB_XHCI_RCAR=y
CONFIG_USB_XHCI_TEGRA=m
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
# CONFIG_USB_EHCI_MXC is not set
CONFIG_USB_EHCI_HCD_OMAP=y
CONFIG_USB_EHCI_HCD_ORION=y
CONFIG_USB_EHCI_HCD_SPEAR=y
CONFIG_USB_EHCI_HCD_STI=y
CONFIG_USB_EHCI_HCD_AT91=y
CONFIG_USB_EHCI_MSM=m
CONFIG_USB_EHCI_TEGRA=y
CONFIG_USB_EHCI_EXYNOS=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
# CONFIG_USB_MAX3421_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_SPEAR=y
CONFIG_USB_OHCI_HCD_STI=y
CONFIG_USB_OHCI_HCD_AT91=y
CONFIG_USB_OHCI_HCD_OMAP3=y
CONFIG_USB_OHCI_HCD_PCI=y
CONFIG_USB_OHCI_EXYNOS=m
CONFIG_USB_OHCI_HCD_PLATFORM=y
# CONFIG_USB_UHCI_HCD is not set
CONFIG_USB_UHCI_SUPPORT_NON_PCI_HC=y
CONFIG_USB_UHCI_PLATFORM=y
# CONFIG_USB_SL811_HCD is not set
CONFIG_USB_R8A66597_HCD=m
# CONFIG_USB_RENESAS_USBHS_HCD is not set
# CONFIG_USB_IMX21_HCD is not set
# CONFIG_USB_HCD_BCMA is not set
# CONFIG_USB_HCD_TEST_MODE is not set
CONFIG_USB_RENESAS_USBHS=m

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
# CONFIG_USB_UAS is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USBIP_CORE is not set
CONFIG_USB_MUSB_HDRC=m
# CONFIG_USB_MUSB_HOST is not set
# CONFIG_USB_MUSB_GADGET is not set
CONFIG_USB_MUSB_DUAL_ROLE=y

#
# Platform Glue Layer
#
CONFIG_USB_MUSB_SUNXI=m
# CONFIG_USB_MUSB_OMAP2PLUS is not set
# CONFIG_USB_MUSB_AM35X is not set
# CONFIG_USB_MUSB_DSPS is not set
# CONFIG_USB_MUSB_UX500 is not set

#
# MUSB DMA mode
#
# CONFIG_MUSB_PIO_ONLY is not set
# CONFIG_USB_TI_CPPI41_DMA is not set
CONFIG_USB_DWC3=y
# CONFIG_USB_DWC3_HOST is not set
# CONFIG_USB_DWC3_GADGET is not set
CONFIG_USB_DWC3_DUAL_ROLE=y

#
# Platform Glue Driver Support
#
CONFIG_USB_DWC3_OMAP=y
CONFIG_USB_DWC3_EXYNOS=y
CONFIG_USB_DWC3_PCI=y
CONFIG_USB_DWC3_KEYSTONE=y
CONFIG_USB_DWC3_OF_SIMPLE=y
CONFIG_USB_DWC3_ST=y
CONFIG_USB_DWC2=y
# CONFIG_USB_DWC2_HOST is not set

#
# Gadget/Dual-role mode requires USB Gadget support to be enabled
#
# CONFIG_USB_DWC2_PERIPHERAL is not set
CONFIG_USB_DWC2_DUAL_ROLE=y
# CONFIG_USB_DWC2_PCI is not set
# CONFIG_USB_DWC2_DEBUG is not set
# CONFIG_USB_DWC2_TRACK_MISSED_SOFS is not set
CONFIG_USB_CHIPIDEA=y
CONFIG_USB_CHIPIDEA_OF=y
CONFIG_USB_CHIPIDEA_PCI=y
CONFIG_USB_CHIPIDEA_UDC=y
CONFIG_USB_CHIPIDEA_HOST=y
CONFIG_USB_ISP1760=y
CONFIG_USB_ISP1760_HCD=y
CONFIG_USB_ISP1761_UDC=y
# CONFIG_USB_ISP1760_HOST_ROLE is not set
# CONFIG_USB_ISP1760_GADGET_ROLE is not set
CONFIG_USB_ISP1760_DUAL_ROLE=y

#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HSIC_USB3503 is not set
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set

#
# USB Physical Layer drivers
#
CONFIG_USB_PHY=y
CONFIG_AB8500_USB=y
CONFIG_KEYSTONE_USB_PHY=y
CONFIG_NOP_USB_XCEIV=y
# CONFIG_AM335X_PHY_USB is not set
CONFIG_USB_GPIO_VBUS=y
CONFIG_USB_ISP1301=y
CONFIG_USB_MSM_OTG=m
# CONFIG_USB_QCOM_8X16_PHY is not set
CONFIG_USB_MXS_PHY=y
CONFIG_USB_ULPI=y
CONFIG_USB_ULPI_VIEWPORT=y
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2

#
# USB Peripheral Controller
#
# CONFIG_USB_AT91 is not set
# CONFIG_USB_ATMEL_USBA is not set
CONFIG_USB_FSL_USB2=y
# CONFIG_USB_FOTG210_UDC is not set
# CONFIG_USB_GR_UDC is not set
# CONFIG_USB_R8A66597 is not set
CONFIG_USB_RENESAS_USBHS_UDC=m
# CONFIG_USB_RENESAS_USB3 is not set
# CONFIG_USB_PXA27X is not set
# CONFIG_USB_MV_UDC is not set
# CONFIG_USB_MV_U3D is not set
# CONFIG_USB_M66592 is not set
# CONFIG_USB_BDC_UDC is not set
# CONFIG_USB_AMD5536UDC is not set
# CONFIG_USB_NET2272 is not set
# CONFIG_USB_NET2280 is not set
# CONFIG_USB_GOKU is not set
# CONFIG_USB_EG20T is not set
# CONFIG_USB_GADGET_XILINX is not set
# CONFIG_USB_DUMMY_HCD is not set
CONFIG_USB_LIBCOMPOSITE=m
CONFIG_USB_U_ETHER=m
CONFIG_USB_F_ECM=m
CONFIG_USB_F_SUBSET=m
CONFIG_USB_F_RNDIS=m
# CONFIG_USB_CONFIGFS is not set
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
# CONFIG_USB_ETH_EEM is not set
# CONFIG_USB_G_NCM is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_MASS_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_ACM_MS is not set
# CONFIG_USB_G_MULTI is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not set
# CONFIG_USB_G_WEBCAM is not set
# CONFIG_USB_LED_TRIG is not set
# CONFIG_UWB is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_PWRSEQ_EMMC=y
CONFIG_PWRSEQ_SIMPLE=y

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=16
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_ARMMMCI=y
CONFIG_MMC_QCOM_DML=y
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_IO_ACCESSORS=y
# CONFIG_MMC_SDHCI_PCI is not set
CONFIG_MMC_SDHCI_PLTFM=y
CONFIG_MMC_SDHCI_OF_ARASAN=y
CONFIG_MMC_SDHCI_OF_AT91=y
CONFIG_MMC_SDHCI_OF_ESDHC=m
CONFIG_MMC_SDHCI_ESDHC_IMX=y
CONFIG_MMC_SDHCI_DOVE=y
CONFIG_MMC_SDHCI_TEGRA=y
CONFIG_MMC_SDHCI_S3C=y
# CONFIG_MMC_SDHCI_SIRF is not set
CONFIG_MMC_SDHCI_PXAV3=y
CONFIG_MMC_SDHCI_SPEAR=y
CONFIG_MMC_SDHCI_S3C_DMA=y
CONFIG_MMC_SDHCI_BCM_KONA=y
# CONFIG_MMC_SDHCI_BCM2835 is not set
# CONFIG_MMC_SDHCI_F_SDH30 is not set
CONFIG_MMC_SDHCI_IPROC=y
CONFIG_MMC_SDHCI_ST=y
CONFIG_MMC_OMAP=y
CONFIG_MMC_OMAP_HS=y
CONFIG_MMC_ATMELMCI=y
CONFIG_MMC_SDHCI_MSM=y
# CONFIG_MMC_MXC is not set
# CONFIG_MMC_TIFM_SD is not set
CONFIG_MMC_MVSDIO=y
CONFIG_MMC_TMIO_CORE=y
CONFIG_MMC_SDHI=y
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
CONFIG_MMC_DW=y
CONFIG_MMC_DW_PLTFM=y
CONFIG_MMC_DW_EXYNOS=y
# CONFIG_MMC_DW_K3 is not set
# CONFIG_MMC_DW_PCI is not set
CONFIG_MMC_DW_ROCKCHIP=y
CONFIG_MMC_SH_MMCIF=y
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
CONFIG_MMC_WMT=y
# CONFIG_MMC_USDHI6ROL0 is not set
CONFIG_MMC_SUNXI=y
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
CONFIG_LEDS_CLASS_FLASH=m

#
# LED drivers
#
# CONFIG_LEDS_AAT1290 is not set
# CONFIG_LEDS_BCM6328 is not set
# CONFIG_LEDS_BCM6358 is not set
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
CONFIG_LEDS_GPIO=y
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP5521 is not set
# CONFIG_LEDS_LP5523 is not set
# CONFIG_LEDS_LP5562 is not set
# CONFIG_LEDS_LP8501 is not set
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
CONFIG_LEDS_PWM=y
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_LT3593 is not set
CONFIG_LEDS_NS2=y
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
CONFIG_LEDS_MAX77693=m
CONFIG_LEDS_MAX8997=m
# CONFIG_LEDS_LM355x is not set
# CONFIG_LEDS_KTD2692 is not set
# CONFIG_LEDS_IS31FL32XX is not set

#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
# CONFIG_LEDS_SYSCON is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=y
CONFIG_LEDS_TRIGGER_ONESHOT=y
# CONFIG_LEDS_TRIGGER_MTD is not set
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_BACKLIGHT=y
CONFIG_LEDS_TRIGGER_CPU=y
CONFIG_LEDS_TRIGGER_GPIO=y
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y

#
# iptables trigger is under Netfilter config (LED target)
#
CONFIG_LEDS_TRIGGER_TRANSIENT=y
CONFIG_LEDS_TRIGGER_CAMERA=y
# CONFIG_LEDS_TRIGGER_PANIC is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_EDAC=y
CONFIG_EDAC_LEGACY_SYSFS=y
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=y
CONFIG_EDAC_HIGHBANK_MC=y
CONFIG_EDAC_HIGHBANK_L2=y
# CONFIG_EDAC_ALTERA is not set
# CONFIG_EDAC_SYNOPSYS is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABX80X is not set
CONFIG_RTC_DRV_AS3722=y
CONFIG_RTC_DRV_DS1307=y
CONFIG_RTC_DRV_DS1307_HWMON=y
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
CONFIG_RTC_DRV_HYM8563=m
# CONFIG_RTC_DRV_MAX6900 is not set
CONFIG_RTC_DRV_MAX8907=y
CONFIG_RTC_DRV_MAX8997=m
CONFIG_RTC_DRV_MAX77686=y
CONFIG_RTC_DRV_RK808=m
CONFIG_RTC_DRV_RS5C372=m
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12057 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
CONFIG_RTC_DRV_TWL4030=y
CONFIG_RTC_DRV_PALMAS=y
CONFIG_RTC_DRV_TPS6586X=y
CONFIG_RTC_DRV_TPS65910=y
CONFIG_RTC_DRV_S35390A=m
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
CONFIG_RTC_DRV_RX8581=m
# CONFIG_RTC_DRV_RX8025 is not set
CONFIG_RTC_DRV_EM3027=y
# CONFIG_RTC_DRV_RV8803 is not set
CONFIG_RTC_DRV_S5M=m

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_RX6110 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
CONFIG_RTC_I2C_AND_SPI=y

#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set

#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
CONFIG_RTC_DRV_DA9063=m
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
CONFIG_RTC_DRV_SPEAR=y
# CONFIG_RTC_DRV_AB8500 is not set
# CONFIG_RTC_DRV_ZYNQMP is not set

#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_DIGICOLOR=m
# CONFIG_RTC_DRV_IMXDI is not set
# CONFIG_RTC_DRV_OMAP is not set
CONFIG_HAVE_S3C_RTC=y
CONFIG_RTC_DRV_S3C=m
# CONFIG_RTC_DRV_PL030 is not set
CONFIG_RTC_DRV_PL031=y
CONFIG_RTC_DRV_AT91RM9200=m
CONFIG_RTC_DRV_AT91SAM9=m
CONFIG_RTC_DRV_VT8500=y
CONFIG_RTC_DRV_SUN6I=y
CONFIG_RTC_DRV_SUNXI=y
CONFIG_RTC_DRV_MV=y
# CONFIG_RTC_DRV_ARMADA38X is not set
# CONFIG_RTC_DRV_PM8XXX is not set
CONFIG_RTC_DRV_TEGRA=y
# CONFIG_RTC_DRV_MXC is not set
# CONFIG_RTC_DRV_SNVS is not set
# CONFIG_RTC_DRV_SIRFSOC is not set
CONFIG_RTC_DRV_ST_LPC=y

#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_HID_SENSOR_TIME is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set

#
# DMA Devices
#
CONFIG_ASYNC_TX_ENABLE_CHANNEL_SWITCH=y
CONFIG_DMA_ENGINE=y
CONFIG_DMA_VIRTUAL_CHANNELS=y
CONFIG_DMA_OF=y
# CONFIG_AMBA_PL08X is not set
CONFIG_AT_HDMAC=y
CONFIG_AT_XDMAC=y
# CONFIG_AXI_DMAC is not set
CONFIG_DMA_BCM2835=y
CONFIG_DMA_OMAP=y
CONFIG_DMA_SUN4I=y
CONFIG_DMA_SUN6I=y
CONFIG_FSL_EDMA=y
CONFIG_IMX_DMA=y
CONFIG_IMX_SDMA=y
# CONFIG_INTEL_IDMA64 is not set
# CONFIG_K3_DMA is not set
CONFIG_MV_XOR=y
CONFIG_MXS_DMA=y
CONFIG_MX3_IPU=y
CONFIG_MX3_IPU_IRQS=4
# CONFIG_NBPFAXI_DMA is not set
CONFIG_PL330_DMA=y
CONFIG_SIRF_DMA=y
CONFIG_STE_DMA40=y
CONFIG_TEGRA20_APB_DMA=y
# CONFIG_TI_CPPI41 is not set
CONFIG_TI_DMA_CROSSBAR=y
CONFIG_TI_EDMA=y
CONFIG_XILINX_VDMA=y
CONFIG_QCOM_BAM_DMA=y
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not set
CONFIG_DW_DMAC_CORE=y
CONFIG_DW_DMAC=y
# CONFIG_DW_DMAC_PCI is not set
CONFIG_RENESAS_DMA=y
CONFIG_SH_DMAE_BASE=y
CONFIG_SH_DMAE=y
CONFIG_SH_DMAE_R8A73A4=y
CONFIG_RCAR_DMAC=y
CONFIG_RENESAS_USB_DMAC=m
# CONFIG_SUDMAC is not set

#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
CONFIG_DMA_ENGINE_RAID=y

#
# DMABUF options
#
# CONFIG_SYNC_FILE is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set
CONFIG_VIRTIO=y

#
# Virtio drivers
#
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_INPUT is not set
CONFIG_VIRTIO_MMIO=y
# CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set

#
# Microsoft Hyper-V guest support
#
CONFIG_STAGING=y
# CONFIG_PRISM2_USB is not set
# CONFIG_COMEDI is not set
# CONFIG_RTL8192U is not set
# CONFIG_RTLLIB is not set
# CONFIG_R8712U is not set
# CONFIG_R8188EU is not set
# CONFIG_R8723AU is not set
# CONFIG_RTS5208 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set

#
# IIO staging drivers
#

#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
# CONFIG_ADIS16203 is not set
# CONFIG_ADIS16209 is not set
# CONFIG_ADIS16240 is not set
# CONFIG_LIS3L02DQ is not set
# CONFIG_SCA3000 is not set

#
# Analog to digital converters
#
# CONFIG_AD7606 is not set
# CONFIG_AD7780 is not set
# CONFIG_AD7816 is not set
# CONFIG_AD7192 is not set
# CONFIG_AD7280 is not set
# CONFIG_SPEAR_ADC is not set

#
# Analog digital bi-direction converters
#
# CONFIG_ADT7316 is not set

#
# Capacitance to digital converters
#
# CONFIG_AD7150 is not set
# CONFIG_AD7152 is not set
# CONFIG_AD7746 is not set

#
# Direct Digital Synthesis
#
# CONFIG_AD9832 is not set
# CONFIG_AD9834 is not set

#
# Digital gyroscope sensors
#
# CONFIG_ADIS16060 is not set

#
# Network Analyzer, Impedance Converters
#
# CONFIG_AD5933 is not set

#
# Light sensors
#
CONFIG_SENSORS_ISL29018=y
CONFIG_SENSORS_ISL29028=y
# CONFIG_TSL2583 is not set
# CONFIG_TSL2x7x is not set

#
# Active energy metering IC
#
# CONFIG_ADE7753 is not set
# CONFIG_ADE7754 is not set
# CONFIG_ADE7758 is not set
# CONFIG_ADE7759 is not set
# CONFIG_ADE7854 is not set

#
# Resolver to digital converters
#
# CONFIG_AD2S90 is not set
# CONFIG_AD2S1200 is not set
# CONFIG_AD2S1210 is not set

#
# Triggers - standalone
#
# CONFIG_FB_SM750 is not set
# CONFIG_FB_XGI is not set
# CONFIG_USB_EMXX is not set

#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
CONFIG_MFD_NVEC=y
CONFIG_KEYBOARD_NVEC=y
CONFIG_SERIO_NVEC_PS2=y
CONFIG_NVEC_POWER=y
CONFIG_NVEC_PAZ00=y
# CONFIG_STAGING_MEDIA is not set

#
# Android
#
CONFIG_STAGING_BOARD=y
# CONFIG_LTE_GDM724X is not set
# CONFIG_MTD_SPINAND_MT29F is not set
# CONFIG_LNET is not set
# CONFIG_DGNC is not set
# CONFIG_GS_FPGABOOT is not set
# CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set
# CONFIG_FB_TFT is not set
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not set
# CONFIG_MOST is not set
# CONFIG_GOLDFISH is not set
CONFIG_CHROME_PLATFORMS=y
CONFIG_CROS_EC_CHARDEV=m
CONFIG_CROS_EC_PROTO=y
CONFIG_CLKDEV_LOOKUP=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y

#
# Common Clock Framework
#
CONFIG_COMMON_CLK_VERSATILE=y
CONFIG_CLK_SP810=y
CONFIG_CLK_VEXPRESS_OSC=y
CONFIG_COMMON_CLK_MAX_GEN=y
CONFIG_COMMON_CLK_MAX77686=y
CONFIG_COMMON_CLK_MAX77802=m
CONFIG_COMMON_CLK_RK808=m
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI514 is not set
# CONFIG_COMMON_CLK_SI570 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CDCE925 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
CONFIG_COMMON_CLK_S2MPS11=m
# CONFIG_COMMON_CLK_AXI_CLKGEN is not set
CONFIG_CLK_QORIQ=y
CONFIG_COMMON_CLK_KEYSTONE=y
# CONFIG_COMMON_CLK_NXP is not set
# CONFIG_COMMON_CLK_PALMAS is not set
# CONFIG_COMMON_CLK_PWM is not set
# CONFIG_COMMON_CLK_PXA is not set
# CONFIG_COMMON_CLK_PIC32 is not set
# CONFIG_COMMON_CLK_OXNAS is not set
CONFIG_CLK_BCM_KONA=y
CONFIG_COMMON_CLK_IPROC=y
CONFIG_COMMON_CLK_HI3519=y
CONFIG_COMMON_CLK_HI6220=y
CONFIG_RESET_HISI=y
# CONFIG_STUB_CLK_HI6220 is not set
CONFIG_MVEBU_CLK_COMMON=y
CONFIG_MVEBU_CLK_CPU=y
CONFIG_MVEBU_CLK_COREDIV=y
CONFIG_ARMADA_370_CLK=y
CONFIG_ARMADA_375_CLK=y
CONFIG_ARMADA_38X_CLK=y
CONFIG_ARMADA_39X_CLK=y
CONFIG_ARMADA_XP_CLK=y
CONFIG_DOVE_CLK=y
CONFIG_QCOM_GDSC=y
CONFIG_COMMON_CLK_QCOM=y
CONFIG_APQ_GCC_8084=y
CONFIG_APQ_MMCC_8084=y
# CONFIG_IPQ_GCC_4019 is not set
# CONFIG_IPQ_GCC_806X is not set
# CONFIG_IPQ_LCC_806X is not set
CONFIG_MSM_GCC_8660=y
# CONFIG_MSM_GCC_8916 is not set
CONFIG_MSM_GCC_8960=y
# CONFIG_MSM_LCC_8960 is not set
CONFIG_MSM_MMCC_8960=y
CONFIG_MSM_GCC_8974=y
CONFIG_MSM_MMCC_8974=y
# CONFIG_MSM_GCC_8996 is not set
# CONFIG_MSM_MMCC_8996 is not set
CONFIG_CLK_RENESAS_CPG_MSTP=y
CONFIG_COMMON_CLK_SAMSUNG=y
CONFIG_TEGRA_CLK_EMC=y
CONFIG_COMMON_CLK_TI_ADPLL=y
CONFIG_HWSPINLOCK=y

#
# Hardware Spinlock drivers
#
# CONFIG_HWSPINLOCK_OMAP is not set
CONFIG_HWSPINLOCK_QCOM=y
# CONFIG_HWSPINLOCK_SIRF is not set
# CONFIG_HSEM_U8500 is not set

#
# Clock Source drivers
#
CONFIG_CLKSRC_OF=y
CONFIG_CLKSRC_PROBE=y
CONFIG_CLKSRC_MMIO=y
CONFIG_DIGICOLOR_TIMER=y
CONFIG_DW_APB_TIMER=y
CONFIG_DW_APB_TIMER_OF=y
CONFIG_ROCKCHIP_TIMER=y
CONFIG_ARMADA_370_XP_TIMER=y
CONFIG_MESON6_TIMER=y
CONFIG_ORION_TIMER=y
CONFIG_SUN4I_TIMER=y
CONFIG_SUN5I_HSTIMER=y
CONFIG_TEGRA_TIMER=y
CONFIG_VT8500_TIMER=y
CONFIG_CADENCE_TTC_TIMER=y
CONFIG_CLKSRC_NOMADIK_MTU=y
CONFIG_CLKSRC_DBX500_PRCMU=y
CONFIG_CLKSRC_DBX500_PRCMU_SCHED_CLOCK=y
CONFIG_CLKSRC_TI_32K=y
CONFIG_ARM_ARCH_TIMER=y
CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y
CONFIG_ARM_GLOBAL_TIMER=y
CONFIG_ARM_TIMER_SP804=y
CONFIG_CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK=y
CONFIG_ATMEL_PIT=y
CONFIG_CLKSRC_EXYNOS_MCT=y
CONFIG_CLKSRC_SAMSUNG_PWM=y
CONFIG_SYS_SUPPORTS_SH_CMT=y
CONFIG_MTK_TIMER=y
CONFIG_SYS_SUPPORTS_SH_MTU2=y
CONFIG_SYS_SUPPORTS_SH_TMU=y
CONFIG_SYS_SUPPORTS_EM_STI=y
CONFIG_SH_TIMER_CMT=y
CONFIG_SH_TIMER_MTU2=y
CONFIG_SH_TIMER_TMU=y
CONFIG_EM_TIMER_STI=y
CONFIG_CLKSRC_QCOM=y
CONFIG_CLKSRC_VERSATILE=y
CONFIG_CLKSRC_IMX_GPT=y
CONFIG_CLKSRC_ST_LPC=y
CONFIG_MAILBOX=y
# CONFIG_ARM_MHU is not set
CONFIG_PL320_MBOX=y
# CONFIG_OMAP2PLUS_MBOX is not set
# CONFIG_ROCKCHIP_MBOX is not set
# CONFIG_ALTERA_MBOX is not set
CONFIG_BCM2835_MBOX=y
# CONFIG_STI_MBOX is not set
# CONFIG_TI_MESSAGE_MANAGER is not set
# CONFIG_HI6220_MBOX is not set
# CONFIG_MAILBOX_TEST is not set
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y

#
# Generic IOMMU Pagetable Support
#
# CONFIG_IOMMU_IO_PGTABLE_LPAE is not set
# CONFIG_IOMMU_IO_PGTABLE_ARMV7S is not set
CONFIG_OF_IOMMU=y
# CONFIG_OMAP_IOMMU is not set
CONFIG_ROCKCHIP_IOMMU=y
CONFIG_TEGRA_IOMMU_GART=y
CONFIG_TEGRA_IOMMU_SMMU=y
# CONFIG_EXYNOS_IOMMU is not set
# CONFIG_IPMMU_VMSA is not set
# CONFIG_ARM_SMMU is not set
# CONFIG_MTK_IOMMU is not set

#
# Remoteproc drivers
#
# CONFIG_STE_MODEM_RPROC is not set
# CONFIG_WKUP_M3_RPROC is not set
# CONFIG_ST_REMOTEPROC is not set

#
# Rpmsg drivers
#

#
# SOC (System On Chip) specific Drivers
#
CONFIG_RASPBERRYPI_POWER=y
CONFIG_SOC_BRCMSTB=y
# CONFIG_MTK_INFRACFG is not set
# CONFIG_MTK_PMIC_WRAP is not set
# CONFIG_MTK_SCPSYS is not set
CONFIG_QCOM_GSBI=y
CONFIG_QCOM_PM=y
CONFIG_QCOM_SMEM=y
CONFIG_QCOM_SMD=y
CONFIG_QCOM_SMD_RPM=y
CONFIG_QCOM_SMEM_STATE=y
CONFIG_QCOM_SMP2P=y
CONFIG_QCOM_SMSM=y
CONFIG_QCOM_WCNSS_CTRL=m
CONFIG_ROCKCHIP_PM_DOMAINS=y
CONFIG_SOC_SAMSUNG=y
CONFIG_EXYNOS_PMU=y
CONFIG_SUNXI_SRAM=y
CONFIG_ARCH_TEGRA_2x_SOC=y
CONFIG_ARCH_TEGRA_3x_SOC=y
CONFIG_ARCH_TEGRA_114_SOC=y
CONFIG_ARCH_TEGRA_124_SOC=y
# CONFIG_SOC_TI is not set
CONFIG_PM_DEVFREQ=y

#
# DEVFREQ Governors
#
CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=m
# CONFIG_DEVFREQ_GOV_PERFORMANCE is not set
# CONFIG_DEVFREQ_GOV_POWERSAVE is not set
# CONFIG_DEVFREQ_GOV_USERSPACE is not set
# CONFIG_DEVFREQ_GOV_PASSIVE is not set

#
# DEVFREQ Drivers
#
# CONFIG_ARM_EXYNOS_BUS_DEVFREQ is not set
CONFIG_ARM_TEGRA_DEVFREQ=m
# CONFIG_PM_DEVFREQ_EVENT is not set
CONFIG_EXTCON=y

#
# Extcon Device Drivers
#
# CONFIG_EXTCON_ADC_JACK is not set
# CONFIG_EXTCON_AXP288 is not set
# CONFIG_EXTCON_GPIO is not set
# CONFIG_EXTCON_MAX14577 is not set
# CONFIG_EXTCON_MAX3355 is not set
# CONFIG_EXTCON_MAX77693 is not set
# CONFIG_EXTCON_MAX8997 is not set
# CONFIG_EXTCON_PALMAS is not set
# CONFIG_EXTCON_RT8973A is not set
# CONFIG_EXTCON_SM5502 is not set
# CONFIG_EXTCON_USB_GPIO is not set
CONFIG_MEMORY=y
# CONFIG_ARM_PL172_MPMC is not set
CONFIG_ATMEL_SDRAMC=y
CONFIG_TI_AEMIF=y
# CONFIG_TI_EMIF is not set
CONFIG_OMAP_GPMC=y
# CONFIG_OMAP_GPMC_DEBUG is not set
CONFIG_MVEBU_DEVBUS=y
CONFIG_TEGRA20_MC=y
CONFIG_SAMSUNG_MC=y
CONFIG_EXYNOS_SROM=y
CONFIG_TEGRA_MC=y
CONFIG_TEGRA124_EMC=y
CONFIG_IIO=y
CONFIG_IIO_BUFFER=y
# CONFIG_IIO_BUFFER_CB is not set
CONFIG_IIO_KFIFO_BUF=y
CONFIG_IIO_TRIGGERED_BUFFER=y
# CONFIG_IIO_CONFIGFS is not set
CONFIG_IIO_TRIGGER=y
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_TRIGGER is not set

#
# Accelerometers
#
# CONFIG_BMA180 is not set
# CONFIG_BMC150_ACCEL is not set
# CONFIG_IIO_ST_ACCEL_3AXIS is not set
# CONFIG_KXSD9 is not set
# CONFIG_KXCJK1013 is not set
# CONFIG_MMA7455_I2C is not set
# CONFIG_MMA7455_SPI is not set
# CONFIG_MMA8452 is not set
# CONFIG_MMA9551 is not set
# CONFIG_MMA9553 is not set
# CONFIG_MXC4005 is not set
# CONFIG_MXC6255 is not set
# CONFIG_STK8312 is not set
# CONFIG_STK8BA50 is not set

#
# Analog to digital converters
#
# CONFIG_AD7266 is not set
# CONFIG_AD7291 is not set
# CONFIG_AD7298 is not set
# CONFIG_AD7476 is not set
# CONFIG_AD7791 is not set
# CONFIG_AD7793 is not set
# CONFIG_AD7887 is not set
# CONFIG_AD7923 is not set
# CONFIG_AD799X is not set
CONFIG_AT91_ADC=m
CONFIG_AT91_SAMA5D2_ADC=m
# CONFIG_AXP288_ADC is not set
CONFIG_BERLIN2_ADC=m
# CONFIG_CC10001_ADC is not set
CONFIG_EXYNOS_ADC=m
# CONFIG_HI8435 is not set
# CONFIG_INA2XX_ADC is not set
# CONFIG_IMX7D_ADC is not set
# CONFIG_MAX1027 is not set
# CONFIG_MAX1363 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
# CONFIG_NAU7802 is not set
# CONFIG_PALMAS_GPADC is not set
# CONFIG_QCOM_SPMI_IADC is not set
# CONFIG_QCOM_SPMI_VADC is not set
# CONFIG_ROCKCHIP_SARADC is not set
# CONFIG_TI_ADC081C is not set
# CONFIG_TI_ADC0832 is not set
# CONFIG_TI_ADC128S052 is not set
# CONFIG_TI_ADS1015 is not set
# CONFIG_TI_ADS8688 is not set
# CONFIG_TWL4030_MADC is not set
# CONFIG_TWL6030_GPADC is not set
CONFIG_VF610_ADC=m
CONFIG_XILINX_XADC=y

#
# Amplifiers
#
# CONFIG_AD8366 is not set

#
# Chemical Sensors
#
# CONFIG_ATLAS_PH_SENSOR is not set
# CONFIG_IAQCORE is not set
# CONFIG_VZ89X is not set

#
# Hid Sensor IIO Common
#

#
# SSP Sensor Common
#
# CONFIG_IIO_SSP_SENSORHUB is not set

#
# Digital to analog converters
#
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5592R is not set
# CONFIG_AD5593R is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
# CONFIG_AD5686 is not set
# CONFIG_AD5755 is not set
# CONFIG_AD5761 is not set
# CONFIG_AD5764 is not set
# CONFIG_AD5791 is not set
# CONFIG_AD7303 is not set
# CONFIG_M62332 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4922 is not set
# CONFIG_VF610_DAC is not set

#
# IIO dummy driver
#
# CONFIG_IIO_SIMPLE_DUMMY is not set

#
# Frequency Synthesizers DDS/PLL
#

#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set

#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF4350 is not set

#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
# CONFIG_ADXRS450 is not set
# CONFIG_BMG160 is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set

#
# Health Sensors
#

#
# Heart Rate Monitors
#
# CONFIG_AFE4403 is not set
# CONFIG_AFE4404 is not set
# CONFIG_MAX30100 is not set

#
# Humidity sensors
#
# CONFIG_AM2315 is not set
# CONFIG_DHT11 is not set
# CONFIG_HDC100X is not set
# CONFIG_HTU21 is not set
# CONFIG_SI7005 is not set
# CONFIG_SI7020 is not set

#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16480 is not set
# CONFIG_BMI160_I2C is not set
# CONFIG_BMI160_SPI is not set
# CONFIG_KMX61 is not set
# CONFIG_INV_MPU6050_I2C is not set
# CONFIG_INV_MPU6050_SPI is not set

#
# Light sensors
#
# CONFIG_ADJD_S311 is not set
# CONFIG_AL3320A is not set
# CONFIG_APDS9300 is not set
# CONFIG_APDS9960 is not set
# CONFIG_BH1750 is not set
# CONFIG_BH1780 is not set
# CONFIG_CM32181 is not set
# CONFIG_CM3232 is not set
# CONFIG_CM3323 is not set
# CONFIG_CM36651 is not set
# CONFIG_GP2AP020A00F is not set
# CONFIG_ISL29125 is not set
# CONFIG_JSA1212 is not set
# CONFIG_RPR0521 is not set
# CONFIG_LTR501 is not set
# CONFIG_MAX44000 is not set
# CONFIG_OPT3001 is not set
# CONFIG_PA12203001 is not set
# CONFIG_STK3310 is not set
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not set
# CONFIG_TSL4531 is not set
# CONFIG_US5182D is not set
# CONFIG_VCNL4000 is not set
# CONFIG_VEML6070 is not set

#
# Magnetometer sensors
#
CONFIG_AK8975=y
# CONFIG_AK09911 is not set
# CONFIG_BMC150_MAGN_I2C is not set
# CONFIG_BMC150_MAGN_SPI is not set
# CONFIG_MAG3110 is not set
# CONFIG_MMC35240 is not set
# CONFIG_IIO_ST_MAGN_3AXIS is not set
# CONFIG_SENSORS_HMC5843_I2C is not set
# CONFIG_SENSORS_HMC5843_SPI is not set

#
# Inclinometer sensors
#

#
# Triggers - standalone
#
# CONFIG_IIO_INTERRUPT_TRIGGER is not set
# CONFIG_IIO_SYSFS_TRIGGER is not set

#
# Digital potentiometers
#
# CONFIG_DS1803 is not set
# CONFIG_MCP4131 is not set
# CONFIG_MCP4531 is not set
# CONFIG_TPL0102 is not set

#
# Pressure sensors
#
# CONFIG_BMP280 is not set
# CONFIG_HP03 is not set
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL115_SPI is not set
# CONFIG_MPL3115 is not set
# CONFIG_MS5611 is not set
# CONFIG_MS5637 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set
# CONFIG_HP206C is not set

#
# Lightning sensors
#
# CONFIG_AS3935 is not set

#
# Proximity sensors
#
# CONFIG_LIDAR_LITE_V2 is not set
# CONFIG_SX9500 is not set

#
# Temperature sensors
#
# CONFIG_MLX90614 is not set
# CONFIG_TMP006 is not set
# CONFIG_TSYS01 is not set
# CONFIG_TSYS02D is not set
# CONFIG_NTB is not set
# CONFIG_VME_BUS is not set
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
# CONFIG_PWM_AB8500 is not set
CONFIG_PWM_ATMEL=m
CONFIG_PWM_ATMEL_HLCDC_PWM=m
CONFIG_PWM_ATMEL_TCB=m
# CONFIG_PWM_BCM_KONA is not set
CONFIG_PWM_BCM2835=y
# CONFIG_PWM_BERLIN is not set
# CONFIG_PWM_BRCMSTB is not set
CONFIG_PWM_FSL_FTM=m
# CONFIG_PWM_IMX is not set
# CONFIG_PWM_MTK_DISP is not set
# CONFIG_PWM_OMAP_DMTIMER is not set
# CONFIG_PWM_PCA9685 is not set
# CONFIG_PWM_RCAR is not set
CONFIG_PWM_RENESAS_TPU=y
CONFIG_PWM_ROCKCHIP=m
CONFIG_PWM_SAMSUNG=m
# CONFIG_PWM_SPEAR is not set
CONFIG_PWM_STI=y
CONFIG_PWM_SUN4I=y
CONFIG_PWM_TEGRA=y
# CONFIG_PWM_TIECAP is not set
# CONFIG_PWM_TIEHRPWM is not set
# CONFIG_PWM_TWL is not set
# CONFIG_PWM_TWL_LED is not set
CONFIG_PWM_VT8500=y
CONFIG_IRQCHIP=y
CONFIG_ARM_GIC=y
CONFIG_ARM_GIC_MAX_NR=1
CONFIG_ARM_GIC_V2M=y
CONFIG_GIC_NON_BANKED=y
CONFIG_ARM_GIC_V3=y
CONFIG_ARMADA_370_XP_IRQ=y
CONFIG_ALPINE_MSI=y
CONFIG_ATMEL_AIC5_IRQ=y
CONFIG_BCM7120_L2_IRQ=y
CONFIG_BRCMSTB_L2_IRQ=y
CONFIG_DW_APB_ICTL=y
CONFIG_OMAP_IRQCHIP=y
CONFIG_ORION_IRQCHIP=y
CONFIG_RENESAS_INTC_IRQPIN=y
CONFIG_RENESAS_IRQC=y
CONFIG_ST_IRQCHIP=y
# CONFIG_TS4800_IRQ is not set
CONFIG_IRQ_CROSSBAR=y
CONFIG_KEYSTONE_IRQ=y
CONFIG_LS_SCFG_MSI=y
CONFIG_PARTITION_PERCPU=y
# CONFIG_IPACK_BUS is not set
CONFIG_ARCH_HAS_RESET_CONTROLLER=y
CONFIG_RESET_CONTROLLER=y
CONFIG_STI_RESET_SYSCFG=y
CONFIG_STIH415_RESET=y
CONFIG_STIH416_RESET=y
CONFIG_STIH407_RESET=y
# CONFIG_COMMON_RESET_HI6220 is not set
# CONFIG_FMC is not set

#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
# CONFIG_PHY_BCM_NS_USB2 is not set
CONFIG_PHY_BERLIN_USB=y
CONFIG_PHY_BERLIN_SATA=y
CONFIG_ARMADA375_USBCLUSTER_PHY=y
# CONFIG_PHY_DM816X_USB is not set
CONFIG_PHY_EXYNOS_MIPI_VIDEO=y
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
CONFIG_PHY_MVEBU_SATA=y
CONFIG_PHY_MIPHY28LP=y
CONFIG_PHY_MIPHY365X=y
CONFIG_PHY_RCAR_GEN2=m
# CONFIG_PHY_RCAR_GEN3_USB2 is not set
CONFIG_OMAP_CONTROL_PHY=y
CONFIG_OMAP_USB2=y
CONFIG_TI_PIPE3=y
CONFIG_PHY_EXYNOS_DP_VIDEO=y
# CONFIG_BCM_KONA_USB2_PHY is not set
# CONFIG_PHY_EXYNOS5250_SATA is not set
CONFIG_PHY_HIX5HD2_SATA=y
# CONFIG_PHY_MT65XX_USB3 is not set
CONFIG_PHY_SUN4I_USB=y
CONFIG_PHY_SUN9I_USB=y
CONFIG_PHY_SAMSUNG_USB2=m
CONFIG_PHY_EXYNOS4210_USB2=y
CONFIG_PHY_EXYNOS4X12_USB2=y
CONFIG_PHY_EXYNOS5250_USB2=y
CONFIG_PHY_EXYNOS5_USBDRD=y
CONFIG_PHY_QCOM_APQ8064_SATA=m
# CONFIG_PHY_QCOM_IPQ806X_SATA is not set
CONFIG_PHY_ROCKCHIP_USB=m
# CONFIG_PHY_ROCKCHIP_EMMC is not set
CONFIG_PHY_ROCKCHIP_DP=m
CONFIG_PHY_ST_SPEAR1310_MIPHY=y
CONFIG_PHY_ST_SPEAR1340_MIPHY=y
CONFIG_PHY_STIH407_USB=y
CONFIG_PHY_STIH41X_USB=y
# CONFIG_PHY_QCOM_UFS is not set
CONFIG_PHY_BRCM_SATA=y
CONFIG_PHY_CYGNUS_PCIE=y
CONFIG_PHY_TEGRA_XUSB=y
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set

#
# Performance monitor support
#
CONFIG_ARM_PMU=y
CONFIG_RAS=y
# CONFIG_THUNDERBOLT is not set

#
# Android
#
# CONFIG_ANDROID is not set
# CONFIG_LIBNVDIMM is not set
CONFIG_NVMEM=y
# CONFIG_NVMEM_IMX_OCOTP is not set
# CONFIG_MTK_EFUSE is not set
# CONFIG_QCOM_QFPROM is not set
# CONFIG_ROCKCHIP_EFUSE is not set
CONFIG_NVMEM_SUNXI_SID=y
# CONFIG_NVMEM_VF610_OCOTP is not set
# CONFIG_STM is not set
# CONFIG_INTEL_TH is not set

#
# FPGA Configuration Support
#
# CONFIG_FPGA is not set

#
# Firmware Drivers
#
CONFIG_ARM_PSCI_FW=y
# CONFIG_FIRMWARE_MEMMAP is not set
CONFIG_RASPBERRYPI_FIRMWARE=y
CONFIG_QCOM_SCM=y
CONFIG_QCOM_SCM_32=y
CONFIG_HAVE_ARM_SMCCC=y
# CONFIG_BCM47XX_NVRAM is not set

#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_ENCRYPTION is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_MANDATORY_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_QUOTACTL is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_FAT_DEFAULT_UTF8 is not set
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
# CONFIG_PROC_CHILDREN is not set
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=m
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ORANGEFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS2_FS is not set
CONFIG_UBIFS_FS=y
# CONFIG_UBIFS_FS_ADVANCED_COMPR is not set
CONFIG_UBIFS_FS_LZO=y
CONFIG_UBIFS_FS_ZLIB=y
# CONFIG_UBIFS_ATIME_SUPPORT is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_FILE_CACHE=y
# CONFIG_SQUASHFS_FILE_DIRECT is not set
CONFIG_SQUASHFS_DECOMP_SINGLE=y
# CONFIG_SQUASHFS_DECOMP_MULTI is not set
# CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU is not set
# CONFIG_SQUASHFS_XATTR is not set
CONFIG_SQUASHFS_ZLIB=y
# CONFIG_SQUASHFS_LZ4 is not set
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_PSTORE is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFSD is not set
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_DEBUG is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#

#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DYNAMIC_DEBUG is not set

#
# Compile-time checks and compiler options
#
# CONFIG_DEBUG_INFO is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_PAGE_OWNER is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_DEBUG_KERNEL=y

#
# Memory Debugging
#
# CONFIG_PAGE_EXTENSION is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_DEBUG_HIGHMEM is not set
# CONFIG_DEBUG_SHIRQ is not set

#
# Debug Lockups and Hangs
#
CONFIG_LOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
# CONFIG_WQ_WATCHDOG is not set
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHED_INFO is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
# CONFIG_DEBUG_TIMEKEEPING is not set
# CONFIG_TIMER_STATS is not set

#
# Lock Debugging (spinlocks, mutexes, etc...)
#
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_STACKTRACE is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PI_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set

#
# RCU Debugging
#
# CONFIG_PROVE_RCU is not set
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_TORTURE_TEST is not set
# CONFIG_RCU_PERF_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=21
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_ENABLE_DEFAULT_TRACERS is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_TRACER_SNAPSHOT is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_UPROBE_EVENT is not set
# CONFIG_PROBE_EVENTS is not set
# CONFIG_TRACEPOINT_BENCHMARK is not set
CONFIG_TRACING_EVENTS_GPIO=y

#
# Runtime Testing
#
# CONFIG_LKDTM is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_HEXDUMP is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_PRINTF is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_UUID is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_HASH is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_TEST_BPF is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_MEMTEST is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_UBSAN is not set
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
# CONFIG_STRICT_DEVMEM is not set
# CONFIG_ARM_PTDUMP is not set
CONFIG_ARM_UNWIND=y
# CONFIG_DEBUG_USER is not set
# CONFIG_DEBUG_LL is not set
CONFIG_DEBUG_IMX_UART_PORT=1
CONFIG_DEBUG_VF_UART_PORT=1
CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S"
# CONFIG_DEBUG_UART_8250 is not set
CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h"
# CONFIG_PID_IN_CONTEXTIDR is not set
# CONFIG_DEBUG_SET_MODULE_RONX is not set
# CONFIG_CORESIGHT is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_PERSISTENT_KEYRINGS is not set
# CONFIG_BIG_KEYS is not set
# CONFIG_ENCRYPTED_KEYS is not set
# CONFIG_KEY_DH_OPERATIONS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_RNG_DEFAULT=m
CONFIG_CRYPTO_AKCIPHER2=y
# CONFIG_CRYPTO_RSA is not set
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_NULL2=y
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=m
# CONFIG_CRYPTO_MCRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_ABLK_HELPER=m

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_SEQIV=m
CONFIG_CRYPTO_ECHAINIV=m

#
# Block modes
#
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_CTR=m
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_KEYWRAP is not set

#
# Hash modes
#
CONFIG_CRYPTO_CMAC=m
CONFIG_CRYPTO_HMAC=m
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_CRCT10DIF is not set
CONFIG_CRYPTO_GHASH=m
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
# CONFIG_CRYPTO_842 is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_DRBG_MENU=m
CONFIG_CRYPTO_DRBG_HMAC=y
# CONFIG_CRYPTO_DRBG_HASH is not set
# CONFIG_CRYPTO_DRBG_CTR is not set
CONFIG_CRYPTO_DRBG=m
CONFIG_CRYPTO_JITTERENTROPY=m
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
# CONFIG_CRYPTO_USER_API_RNG is not set
# CONFIG_CRYPTO_USER_API_AEAD is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_MV_CESA is not set
CONFIG_CRYPTO_DEV_MARVELL_CESA=m
# CONFIG_CRYPTO_DEV_FSL_CAAM is not set
# CONFIG_CRYPTO_DEV_OMAP_SHAM is not set
# CONFIG_CRYPTO_DEV_OMAP_AES is not set
# CONFIG_CRYPTO_DEV_OMAP_DES is not set
# CONFIG_CRYPTO_DEV_SAHARA is not set
# CONFIG_CRYPTO_DEV_MXC_SCC is not set
# CONFIG_CRYPTO_DEV_S5P is not set
# CONFIG_CRYPTO_DEV_UX500 is not set
CONFIG_CRYPTO_DEV_ATMEL_AES=m
CONFIG_CRYPTO_DEV_ATMEL_TDES=m
CONFIG_CRYPTO_DEV_ATMEL_SHA=m
# CONFIG_CRYPTO_DEV_MXS_DCP is not set
# CONFIG_CRYPTO_DEV_QCE is not set
CONFIG_CRYPTO_DEV_SUN4I_SS=m
CONFIG_CRYPTO_DEV_ROCKCHIP=m
# CONFIG_ASYMMETRIC_KEY_TYPE is not set

#
# Certificates for signature checking
#
CONFIG_ARM_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM=m
CONFIG_CRYPTO_SHA1_ARM_NEON=m
CONFIG_CRYPTO_SHA1_ARM_CE=m
CONFIG_CRYPTO_SHA2_ARM_CE=m
CONFIG_CRYPTO_SHA256_ARM=m
CONFIG_CRYPTO_SHA512_ARM=m
CONFIG_CRYPTO_AES_ARM=m
CONFIG_CRYPTO_AES_ARM_BS=m
CONFIG_CRYPTO_AES_ARM_CE=m
CONFIG_CRYPTO_GHASH_ARM_CE=m
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_HAVE_ARCH_BITREVERSE=y
CONFIG_RATIONAL=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_STMP_DEVICE=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set
# CONFIG_AUDIT_ARCH_COMPAT_GENERIC is not set
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_ASSOCIATIVE_ARRAY=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_DMA=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
# CONFIG_GLOB_SELFTEST is not set
CONFIG_NLATTR=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
# CONFIG_CORDIC is not set
# CONFIG_DDR is not set
# CONFIG_IRQ_POLL is not set
CONFIG_LIBFDT=y
CONFIG_OID_REGISTRY=y
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_SG_SPLIT is not set
CONFIG_SG_POOL=y
CONFIG_ARCH_HAS_SG_CHAIN=y
CONFIG_HAVE_KVM_IRQFD=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_MMIO=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_KVM_VFIO=y
CONFIG_HAVE_KVM_ARCH_TLB_FLUSH_ALL=y
CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_ARM_HOST=y
CONFIG_KVM_NEW_VGIC=y

[-- Attachment #3: Type: text/plain, Size: 151 bytes --]

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-24  9:30                     ` Marc Zyngier
@ 2016-07-25  6:28                       ` Stefan Agner
  0 siblings, 0 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-25  6:28 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-24 02:30, Marc Zyngier wrote:
> On Sat, 23 Jul 2016 09:33:54 -0700
> Stefan Agner <stefan@agner.ch> wrote:
> 
>> On 2016-07-23 03:20, Marc Zyngier wrote:
>> > On Sat, 23 Jul 2016 00:45:50 -0700
>> > Stefan Agner <stefan@agner.ch> wrote:
>> >
>> >> On 2016-07-22 11:11, Marc Zyngier wrote:
>> >> > On 22/07/16 18:56, Stefan Agner wrote:
>> >> >> On 2016-07-22 10:49, Marc Zyngier wrote:
>> >> >>> On 22/07/16 18:38, Andrew Jones wrote:
>> >> >>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> >> >>>>> On 22/07/16 15:35, Andrew Jones wrote:
>> >> >>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> >> >>>>>>> Hi Stefan,
>> >> >>>>>>>
>> >> >>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>> >> >>>>>>>> Hi,
>> >> >>>>>>>>
>> >> >>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> >> >>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>> >> >>>>>>>>
>> >> >>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>> >> >>>>>>>> pgd = 8ca52740
>> >> >>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> >> >>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>> >> >>>>>>>> Modules linked in:
>> >> >>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> >> >>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>> >> >>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> >> >>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> >> >>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>> >> >>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> >> >>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> >> >>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> >> >>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> >> >>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>> >> >>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> >> >>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> >> >>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> >> >>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> >> >>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> >> >>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> >> >>>>>>>> 1e20:                                                       ffffffe0
>> >> >>>>>>>> 00000000
>> >> >>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> >> >>>>>>>> 810074f8
>> >> >>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> >> >>>>>>>> 8ca5f800
>> >> >>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> >> >>>>>>>> 7ffbfeff
>> >> >>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> >> >>>>>>>> ffffe000
>> >> >>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> >> >>>>>>>> 8023f248
>> >> >>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> >> >>>>>>>> 00000000
>> >> >>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> >> >>>>>>>> 00000000
>> >> >>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> >> >>>>>>>> 80bc2ec4
>> >> >>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> >> >>>>>>>> 007c1e70
>> >> >>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> >> >>>>>>>> 00000000
>> >> >>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> >> >>>>>>>> 00000036
>> >> >>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> >> >>>>>>>> 755feac0
>> >> >>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> >> >>>>>>>> 755fec6c
>> >> >>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> >> >>>>>>>> 00000000
>> >> >>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> >> >>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> >> >>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> >> >>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> >> >>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> >> >>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> >> >>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> >> >>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>> >> >>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> >> >>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> >> >>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> >> >>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>> >> >>>>>>>>
>> >> >>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> >> >>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> >> >>>>>>>> -nographic -serial stdio -kernel zImage).
>> >> >>>>>>>>
>> >> >>>>>>>> Using a bit older Qemu version 2.4.0.
>> >> >>>>>>>
>> >> >>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> >> >>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> >> >>>>>>> on a Midway (Cortex-A15).
>> >> >>>>>>
>> >> >>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>> >> >>>>>> (I haven't tried anywhere else yet)
>> >> >>>>>>
>> >> >>>>>>>
>> >> >>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>> >> >>>>>>
>> >> >>>>>> Disabling NEW_VGIC "fixes" guest boots.
>> >> >>>>>>
>> >> >>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>> >> >>>>>> tests and provide a comparison of my config vs. a defconfig in
>> >> >>>>>> a few minutes.
>> >> >>>>>
>> >> >>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> >> >>>>> If you can narrow it down to the difference with defconfig, that'd be
>> >> >>>>> tremendously helpful.
>> >> >>>>
>> >> >>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>> >> >>>> selection.
>> >> >>>
>> >> >>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>> >> >>
>> >> >> Hehe, was just plowing through code and came to that conclusion, glad I
>> >> >> got that right :-)
>> >> >>
>> >> >> What defconfig do you use? I could reproduce the issue also with
>> >> >> multi_v7_defconfig + ARM_LPAE + KVM.
>> >> >
>> >> > I have my own config file with the crap I need to make things work on
>> >> > the various platforms I have around. If multi_v7_defconfig works on the
>> >> > cubietruck, I'll give it a spin tomorrow. I need a beer now.
>> >> >
>> >> >> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>> >> >> clock next to get to the bits and pieces required for my board...
>> >> >>
>> >> >> That said, it works fine otherwise, and the stacktrace looks rather
>> >> >> platform independent...
>> >> >
>> >> > Yeah, and that's the worrying part.
>> >>
>> >>
>> >> FWIW, I tried here with Qemu 2.6.0, same stack trace...
>> >
>> > I don't think this is userspace related, specially given that Andrew
>> > managed to trigger it on arm64 as well. I guess we're looking at
>> > something that changes the layout of memory (page size in Drew's case),
>> > and exposes another latent bug. I'll try to get multi_v7_defconfig
>> > running on my CT later today, and hopefully the thing will explode.
>> > Fingers crossed.
>> >
>>
>> I hit another issue, this time in the guest. At times, it seemed as if
>> qemu-system-arm freezed (no console output). I then enabled earlyprintk
>> for PL01X UART, and got this:
>>
>> Architected timer frequency not available
>> ------------[ cut here ]------------
>> WARNING: CPU: 0 PID: 0 at kernel/time/clockevents.c:44
>> cev_delta2ns+0x114/0x128
>> Modules linked in:
>> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.7.0-rc7 #5
>> Hardware name: Generic DT based system
>> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
>> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
>> [<8030e734>] (dump_stack) from [<8011a718>] (__warn+0xe8/0x100)
>> [<8011a718>] (__warn) from [<8011a7e0>] (warn_slowpath_null+0x20/0x28)
>> [<8011a7e0>] (warn_slowpath_null) from [<8017503c>]
>> (cev_delta2ns+0x114/0x128)
>> [<8017503c>] (cev_delta2ns) from [<8017548c>]
>> (clockevents_config.part.2+0x4c/0x6c)
>> [<8017548c>] (clockevents_config.part.2) from [<801754cc>]
>> (clockevents_config_and_register+0x20/0x2c)
>> [<801754cc>] (clockevents_config_and_register) from [<80435d9c>]
>> (arch_timer_setup+0xd8/0x1b4)
>> [<80435d9c>] (arch_timer_setup) from [<8081c118>]
>> (arch_timer_of_init+0x2a0/0x2c8)
>> [<8081c118>] (arch_timer_of_init) from [<8081bb14>]
>> (clocksource_probe+0x54/0x90)
>> [<8081bb14>] (clocksource_probe) from [<80800b30>]
>> (start_kernel+0x240/0x378)
>> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
>> ---[ end trace cb88537fdc8fa200 ]---
>> Architected cp15 timer(s) running at 0.00MHz (virt).
>> Division by zero in kernel.
>> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
>> Hardware name: Generic DT based system
>> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
>> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
>> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
>> [<8030c764>] (Ldiv0_64) from [<80172360>]
>> (clocks_calc_max_nsecs+0x24/0x78)
>> [<80172360>] (clocks_calc_max_nsecs) from [<801725d8>]
>> (__clocksource_update_freq_scale+0x224/0x2fc)
>> [<801725d8>] (__clocksource_update_freq_scale) from [<801726c4>]
>> (__clocksource_register_scale+0x14/0xa8)
>> [<801726c4>] (__clocksource_register_scale) from [<8081be20>]
>> (arch_timer_common_init+0x1d8/0x230)
>> [<8081be20>] (arch_timer_common_init) from [<8081c0dc>]
>> (arch_timer_of_init+0x264/0x2c8)
>> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
>> (clocksource_probe+0x54/0x90)
>> [<8081bb14>] (clocksource_probe) from [<80800b30>]
>> (start_kernel+0x240/0x378)
>> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
>> clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x0,
>> max_idle_ns: 0 ns
>> Division by zero in kernel.
>> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
>> Hardware name: Generic DT based system
>> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
>> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
>> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
>> [<8030c764>] (Ldiv0_64) from [<80172288>]
>> (clocks_calc_mult_shift+0x11c/0x13c)
>> [<80172288>] (clocks_calc_mult_shift) from [<8080a388>]
>> (sched_clock_register+0x64/0x1d8)
>> [<8080a388>] (sched_clock_register) from [<8081be54>]
>> (arch_timer_common_init+0x20c/0x230)
>> [<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
>> (arch_timer_of_init+0x264/0x2c8)
>> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
>> (clocksource_probe+0x54/0x90)
>> [<8081bb14>] (clocksource_probe) from [<80800b30>]
>> (start_kernel+0x240/0x378)
>> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
>> Division by zero in kernel.
>> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7 #5
>> Hardware name: Generic DT based system
>> [<8010e2a0>] (unwind_backtrace) from [<8010b270>] (show_stack+0x10/0x14)
>> [<8010b270>] (show_stack) from [<8030e734>] (dump_stack+0x84/0x98)
>> [<8030e734>] (dump_stack) from [<8030c764>] (Ldiv0_64+0x8/0x18)
>> [<8030c764>] (Ldiv0_64) from [<80172360>]
>> (clocks_calc_max_nsecs+0x24/0x78)
>> [<80172360>] (clocks_calc_max_nsecs) from [<8080a3cc>]
>> (sched_clock_register+0xa8/0x1d8)
>> [<8080a3cc>] (sched_clock_register) from [<8081be54>]
>> (arch_timer_common_init+0x20c/0x230)
>> [<8081be54>] (arch_timer_common_init) from [<8081c0dc>]
>> (arch_timer_of_init+0x264/0x2c8)
>> [<8081c0dc>] (arch_timer_of_init) from [<8081bb14>]
>> (clocksource_probe+0x54/0x90)
>> [<8081bb14>] (clocksource_probe) from [<80800b30>]
>> (start_kernel+0x240/0x378)
>> [<80800b30>] (start_kernel) from [<4000807c>] (0x4000807c)
>> sched_clock: 56 bits at 0 Hz, resolution 0ns, wraps every 0ns
>> Console: colour dummy device 80x30
>> Calibrating delay loop...
>>
>>
>> When it works (which tends to be around every 5. try), then the clock of
>> the Architected timer seems to be correctly identified:
>> Architected cp15 timer(s) running at 8.00MHz (virt).
>>
>> Host looks good:
>> # dmesg | grep Architected
>> [    0.000000] Architected cp15 timer(s) running at 8.00MHz (phys).
>>
>> Afaict, U-Boot correctly initializes the timers frequency in
>> arch/arm/imx-common/syscounter.c.
> 
> It certainly does, but probably only on the boot CPU, whereas it should
> be set on all CPUs (this is a per-CPU register). If your guest boots on
> a secondary CPU, it will find zero as its CNTFRQ, and barf.
> 

Oh I see, that totally explains the behavior I am seeing...

>>
>> The guest is using a vanilla v4.7-rc7 kernel.
>>
>> The host is running without CONFIG_KVM_NEW_VGIC.
>>
>> Looks like some kind of race during initialization...? Related to the
>> new VGIC issue?
> 
> Completely unrelated. Clearly, u-boot is bogus on your system. This bit
> of code:
> 
> http://git.denx.de/?p=u-boot.git;a=blob;f=arch/arm/cpu/armv7/nonsec_virt.S;h=95ce9387b83e972414b6de2d5711a9f40fe097df;hb=HEAD#l185
> 
> is what should be doing the job. It must be called on each CPU, before
> switching to non-secure mode.

... and yes, after defining CONFIG_TIMER_CLK_FREQ it works always! Will
send a patch to the U-Boot ML, thanks!

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-24 12:36               ` Marc Zyngier
  2016-07-25  6:14                 ` Stefan Agner
@ 2016-07-25  6:36                 ` Stefan Agner
  2016-07-25 13:33                   ` Andre Przywara
  1 sibling, 1 reply; 45+ messages in thread
From: Stefan Agner @ 2016-07-25  6:36 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-24 05:36, Marc Zyngier wrote:
> On Sun, 24 Jul 2016 13:22:55 +0100
> Marc Zyngier <marc.zyngier@arm.com> wrote:
> 
>> On Fri, 22 Jul 2016 10:56:44 -0700
>> Stefan Agner <stefan@agner.ch> wrote:
>>
>> > On 2016-07-22 10:49, Marc Zyngier wrote:
>> > > On 22/07/16 18:38, Andrew Jones wrote:
>> > >> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>> > >>> On 22/07/16 15:35, Andrew Jones wrote:
>> > >>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>> > >>>>> Hi Stefan,
>> > >>>>>
>> > >>>>> On 22/07/16 06:57, Stefan Agner wrote:
>> > >>>>>> Hi,
>> > >>>>>>
>> > >>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>> > >>>>>> this stack trace immediately after invoking qemu-system-arm:
>> > >>>>>>
>> > >>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>> > >>>>>> pgd = 8ca52740
>> > >>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>> > >>>>>> Internal error: Oops: 207 [#1] SMP ARM
>> > >>>>>> Modules linked in:
>> > >>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>> > >>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>> > >>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>> > >>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>> > >>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>> > >>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>> > >>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>> > >>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>> > >>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>> > >>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>> > >>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>> > >>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>> > >>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>> > >>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>> > >>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>> > >>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>> > >>>>>> 1e20:                                                       ffffffe0
>> > >>>>>> 00000000
>> > >>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>> > >>>>>> 810074f8
>> > >>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>> > >>>>>> 8ca5f800
>> > >>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>> > >>>>>> 7ffbfeff
>> > >>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>> > >>>>>> ffffe000
>> > >>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>> > >>>>>> 8023f248
>> > >>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>> > >>>>>> 00000000
>> > >>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>> > >>>>>> 00000000
>> > >>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>> > >>>>>> 80bc2ec4
>> > >>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>> > >>>>>> 007c1e70
>> > >>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>> > >>>>>> 00000000
>> > >>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>> > >>>>>> 00000036
>> > >>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>> > >>>>>> 755feac0
>> > >>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>> > >>>>>> 755fec6c
>> > >>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>> > >>>>>> 00000000
>> > >>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>> > >>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>> > >>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>> > >>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>> > >>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>> > >>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>> > >>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>> > >>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>> > >>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>> > >>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>> > >>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>> > >>>>>> ---[ end trace cb88537fdc8fa206 ]---
>> > >>>>>>
>> > >>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>> > >>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>> > >>>>>> -nographic -serial stdio -kernel zImage).
>> > >>>>>>
>> > >>>>>> Using a bit older Qemu version 2.4.0.
>> > >>>>>
>> > >>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>> > >>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>> > >>>>> on a Midway (Cortex-A15).
>> > >>>>
>> > >>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>> > >>>> (I haven't tried anywhere else yet)
>> > >>>>
>> > >>>>>
>> > >>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>> > >>>>
>> > >>>> Disabling NEW_VGIC "fixes" guest boots.
>> > >>>>
>> > >>>> I'm not using defconfig for my host kernel. I'll do a couple more
>> > >>>> tests and provide a comparison of my config vs. a defconfig in
>> > >>>> a few minutes.
>> > >>>
>> > >>> Damn. It is not failing for me, so it has to be a kernel config thing...
>> > >>> If you can narrow it down to the difference with defconfig, that'd be
>> > >>> tremendously helpful.
>> > >>
>> > >> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>> > >> selection.
>> > >
>> > > That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>> >
>> > Hehe, was just plowing through code and came to that conclusion, glad I
>> > got that right :-)
>> >
>> > What defconfig do you use? I could reproduce the issue also with
>> > multi_v7_defconfig + ARM_LPAE + KVM.
>>
>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>> built-in to make my life simpler). The host works perfectly, and I can
>> spawn VMs without any issue.
>>
>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>> as packaged with Jessie from a while ago. I've also upgraded the box to
>> something more recent (2.5), same effect.
>>
>> >
>> > Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>> > clock next to get to the bits and pieces required for my board...
>> >
>> > That said, it works fine otherwise, and the stacktrace looks rather
>> > platform independent...
>>
>> Indeed, and if these clocks were doing anything unsavoury, we'd
>> probably see other things exploding. So we need to find out where we
>> are diverging.
>>
>> What compiler are you using? I just noticed that my build
>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>> going to upgrade that to gcc 5.3 and retest.

As you expected, the clock fix did not influence this problem. Still the
same. I ran strace several times, the crash seems to happen always about
the same time, maybe this gives you a hint?

ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
mmap2(NULL, 2101248, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa3bff000
mmap2(0xa3c00000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa3c00000
munmap(0xa3bff000, 4096)                = 0
munmap(0xa3c02000, 2088960)             = 0
madvise(0xa3c00000, 4096, MADV_MERGEABLE) = -1 EINVAL (Invalid argument)
madvise(0xa3c00000, 4096, MADV_HUGEPAGE) = -1 EINVAL (Invalid argument)
madvise(0xa3c00000, 4096, MADV_DONTFORK) = 0
ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
futex(0x9afe3c, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x4957a8, 4) =
1
tgkill(450, 452, SIGUSR1)               = 0
futex(0x4957a8, FUTEX_WAKE_PRIVATE, 1)  = 1
futex(0x4956a8, FUTEX_WAKE_PRIVATE, 1)  = 1
futex(0x4956ac, FUTEX_WAIT_PRIVATE, 3, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
ioctl(11, KVM_ARM_VCPU_INIT, 0xbe8be99c) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
[   20.383970] Unable to handle kernel paging request at virtual address
fffffffc
...

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  6:14                 ` Stefan Agner
@ 2016-07-25  8:11                   ` Marc Zyngier
  2016-07-25  8:17                     ` Marc Zyngier
  2016-07-25 16:52                     ` Stefan Agner
  2016-07-25  8:42                   ` Marc Zyngier
  1 sibling, 2 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25  8:11 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On 25/07/16 07:14, Stefan Agner wrote:
> On 2016-07-24 05:36, Marc Zyngier wrote:
>> On Sun, 24 Jul 2016 13:22:55 +0100
>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>
>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>> Stefan Agner <stefan@agner.ch> wrote:
>>>
>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>> Hi Stefan,
>>>>>>>>>
>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>
>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>> Modules linked in:
>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>> 00000000
>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>> 810074f8
>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>> 8ca5f800
>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>> 7ffbfeff
>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>> ffffe000
>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>> 8023f248
>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>> 80bc2ec4
>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>> 007c1e70
>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>> 00000000
>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>> 00000036
>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>> 755feac0
>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>> 755fec6c
>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>
>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>
>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>
>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>
>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>
>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>
>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>> a few minutes.
>>>>>>>
>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>> tremendously helpful.
>>>>>>
>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>> selection.
>>>>>
>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>
>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>> got that right :-)
>>>>
>>>> What defconfig do you use? I could reproduce the issue also with
>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>
>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>> built-in to make my life simpler). The host works perfectly, and I can
>>> spawn VMs without any issue.
>>>
>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>> something more recent (2.5), same effect.
>>>
>>>>
>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>> clock next to get to the bits and pieces required for my board...
>>>>
>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>> platform independent...
>>>
>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>> probably see other things exploding. So we need to find out where we
>>> are diverging.
>>>
>>> What compiler are you using? I just noticed that my build
>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>> going to upgrade that to gcc 5.3 and retest.
>>
>> Same thing. The damn thing stubbornly works.
>>
>> Please send your full configuration, compiler version, exact QEMU
>> command line, and any other detail that could be vaguely relevant. As
>> the old VGIC gets removed in 4.8, we definitely need to nail that
>> sucker right now.
> 
> I built the kernel with
> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
> the same compiler version, but built using OpenEmbedded.
> 
> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
> that much on mainline but it seems to be rather stable so far.
> 
> I can reproduce the issue with a minimal command such as this:
> qemu-system-arm -enable-kvm -M virt -cpu host
> 
> [  179.430694] Unable to handle kernel paging request at virtual address
> fffffffc
> What is puzzling me a bit that the address the kernel tries to access is
> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
> unhandled error return?

Your initial report had 0xffffffe4 instead. Which looks a bit like a
"container_of" operation on a NULL pointer. Do you always get the same
backtrace? If so, any chance you could run a

arm-linux-gnueabihf-addr2line -e vmlinux -i TheCrashingPC

so that we get an idea of which lock we're crashing on?

I'm about to try your own config to see if I get somewhere.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  8:11                   ` Marc Zyngier
@ 2016-07-25  8:17                     ` Marc Zyngier
  2016-07-25 13:50                       ` Andre Przywara
  2016-07-25 16:52                     ` Stefan Agner
  1 sibling, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25  8:17 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On 25/07/16 09:11, Marc Zyngier wrote:
> On 25/07/16 07:14, Stefan Agner wrote:
>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>
>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>
>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>> Hi Stefan,
>>>>>>>>>>
>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>
>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>> Modules linked in:
>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>> 810074f8
>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>> 8ca5f800
>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>> ffffe000
>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>> 8023f248
>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>> 007c1e70
>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>> 00000036
>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>> 755feac0
>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>> 755fec6c
>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>
>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>
>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>
>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>
>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>
>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>
>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>> a few minutes.
>>>>>>>>
>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>> tremendously helpful.
>>>>>>>
>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>> selection.
>>>>>>
>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>
>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>> got that right :-)
>>>>>
>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>
>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>> spawn VMs without any issue.
>>>>
>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>> something more recent (2.5), same effect.
>>>>
>>>>>
>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>> clock next to get to the bits and pieces required for my board...
>>>>>
>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>> platform independent...
>>>>
>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>> probably see other things exploding. So we need to find out where we
>>>> are diverging.
>>>>
>>>> What compiler are you using? I just noticed that my build
>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>> going to upgrade that to gcc 5.3 and retest.
>>>
>>> Same thing. The damn thing stubbornly works.
>>>
>>> Please send your full configuration, compiler version, exact QEMU
>>> command line, and any other detail that could be vaguely relevant. As
>>> the old VGIC gets removed in 4.8, we definitely need to nail that
>>> sucker right now.
>>
>> I built the kernel with
>> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
>> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
>> the same compiler version, but built using OpenEmbedded.
>>
>> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
>> that much on mainline but it seems to be rather stable so far.
>>
>> I can reproduce the issue with a minimal command such as this:
>> qemu-system-arm -enable-kvm -M virt -cpu host
>>
>> [  179.430694] Unable to handle kernel paging request at virtual address
>> fffffffc
>> What is puzzling me a bit that the address the kernel tries to access is
>> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
>> unhandled error return?
> 
> Your initial report had 0xffffffe4 instead. Which looks a bit like a
> "container_of" operation on a NULL pointer. Do you always get the same
> backtrace? If so, any chance you could run a
> 
> arm-linux-gnueabihf-addr2line -e vmlinux -i TheCrashingPC

Actually, try with the LR value, not the PC.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  6:14                 ` Stefan Agner
  2016-07-25  8:11                   ` Marc Zyngier
@ 2016-07-25  8:42                   ` Marc Zyngier
  1 sibling, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25  8:42 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On 25/07/16 07:14, Stefan Agner wrote:
> On 2016-07-24 05:36, Marc Zyngier wrote:
>> On Sun, 24 Jul 2016 13:22:55 +0100
>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>
>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>> Stefan Agner <stefan@agner.ch> wrote:
>>>
>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>> Hi Stefan,
>>>>>>>>>
>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>
>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>> Modules linked in:
>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>> 00000000
>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>> 810074f8
>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>> 8ca5f800
>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>> 7ffbfeff
>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>> ffffe000
>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>> 8023f248
>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>> 80bc2ec4
>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>> 007c1e70
>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>> 00000000
>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>> 00000036
>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>> 755feac0
>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>> 755fec6c
>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>
>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>
>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>
>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>
>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>
>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>
>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>> a few minutes.
>>>>>>>
>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>> tremendously helpful.
>>>>>>
>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>> selection.
>>>>>
>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>
>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>> got that right :-)
>>>>
>>>> What defconfig do you use? I could reproduce the issue also with
>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>
>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>> built-in to make my life simpler). The host works perfectly, and I can
>>> spawn VMs without any issue.
>>>
>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>> something more recent (2.5), same effect.
>>>
>>>>
>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>> clock next to get to the bits and pieces required for my board...
>>>>
>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>> platform independent...
>>>
>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>> probably see other things exploding. So we need to find out where we
>>> are diverging.
>>>
>>> What compiler are you using? I just noticed that my build
>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>> going to upgrade that to gcc 5.3 and retest.
>>
>> Same thing. The damn thing stubbornly works.
>>
>> Please send your full configuration, compiler version, exact QEMU
>> command line, and any other detail that could be vaguely relevant. As
>> the old VGIC gets removed in 4.8, we definitely need to nail that
>> sucker right now.
> 
> I built the kernel with
> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
> the same compiler version, but built using OpenEmbedded.

Something doesn't add up here. The LR in your original report is
802172d4, which would indicate a 2/2 split. But you compile your kernel
with CONFIG_VMSPLIT_3G=y. Have you changed it? Can you give me a crash
log that matches this kernel configuration?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-22 19:54             ` Marc Zyngier
@ 2016-07-25  9:00               ` Andrew Jones
  2016-07-25  9:05                 ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Andrew Jones @ 2016-07-25  9:00 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Fri, Jul 22, 2016 at 08:54:28PM +0100, Marc Zyngier wrote:
> On Fri, 22 Jul 2016 21:45:00 +0200
> Andrew Jones <drjones@redhat.com> wrote:
> 
> > On Fri, Jul 22, 2016 at 07:06:36PM +0100, Marc Zyngier wrote:
> > > On 22/07/16 18:38, Andrew Jones wrote:  
> > > > On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> > > >> On 22/07/16 15:35, Andrew Jones wrote:  
> > > >>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> > > >>>> Hi Stefan,
> > > >>>>
> > > >>>> On 22/07/16 06:57, Stefan Agner wrote:  
> > > >>>>> Hi,
> > > >>>>>
> > > >>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> > > >>>>> this stack trace immediately after invoking qemu-system-arm:
> > > >>>>>
> > > >>>>> Unable to handle kernel paging request at virtual address ffffffe4
> > > >>>>> pgd = 8ca52740
> > > >>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> > > >>>>> Internal error: Oops: 207 [#1] SMP ARM
> > > >>>>> Modules linked in:  
> > > >>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> > > >>>>> 4.7.0-rc7-00094-gea3ed2c #109
> > > >>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> > > >>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> > > >>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> > > >>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> > > >>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> > > >>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> > > >>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> > > >>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> > > >>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> > > >>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> > > >>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> > > >>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> > > >>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> > > >>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> > > >>>>> 1e20:                                                       ffffffe0
> > > >>>>> 00000000
> > > >>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> > > >>>>> 810074f8
> > > >>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> > > >>>>> 8ca5f800
> > > >>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> > > >>>>> 7ffbfeff
> > > >>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> > > >>>>> ffffe000
> > > >>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> > > >>>>> 8023f248
> > > >>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> > > >>>>> 00000000
> > > >>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> > > >>>>> 00000000
> > > >>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> > > >>>>> 80bc2ec4
> > > >>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> > > >>>>> 007c1e70
> > > >>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> > > >>>>> 00000000
> > > >>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> > > >>>>> 00000036
> > > >>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> > > >>>>> 755feac0
> > > >>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> > > >>>>> 755fec6c
> > > >>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> > > >>>>> 00000000
> > > >>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> > > >>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> > > >>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> > > >>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> > > >>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> > > >>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> > > >>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> > > >>>>> (do_vfs_ioctl+0xa0/0x8b8)
> > > >>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> > > >>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> > > >>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> > > >>>>> ---[ end trace cb88537fdc8fa206 ]---
> > > >>>>>
> > > >>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> > > >>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> > > >>>>> -nographic -serial stdio -kernel zImage).
> > > >>>>>
> > > >>>>> Using a bit older Qemu version 2.4.0.  
> > > >>>>
> > > >>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> > > >>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> > > >>>> on a Midway (Cortex-A15).  
> > > >>>
> > > >>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> > > >>> (I haven't tried anywhere else yet)
> > > >>>  
> > > >>>>
> > > >>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> > > >>>
> > > >>> Disabling NEW_VGIC "fixes" guest boots.
> > > >>>
> > > >>> I'm not using defconfig for my host kernel. I'll do a couple more
> > > >>> tests and provide a comparison of my config vs. a defconfig in
> > > >>> a few minutes.  
> > > >>
> > > >> Damn. It is not failing for me, so it has to be a kernel config thing...
> > > >> If you can narrow it down to the difference with defconfig, that'd be
> > > >> tremendously helpful.  
> > > > 
> > > > It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> > > > selection.  
> > > 
> > > root@flakes:~# zgrep 64K /proc/config.gz
> > > CONFIG_ARM64_64K_PAGES=y
> > > 
> > > VMs up and running. It is definitely something else, potentially
> > > affected by the page size. This is going to be a fun weekend.
> > > 
> > > Thanks for having had a look!  
> > 
> > Ah... I didn't even notice the 32-bit addresses above, only the
> > 
> >  PC is at do_raw_spin_lock+0x8/0x1dc
> >  LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> > 
> > which matches the backtrace I get with a 64-bit guest. And I really
> > only change PAGE_SIZE between a host kernel that works and doesn't,
> > which does also change ARM64_CONT_SHIFT and PGTABLE_LEVELS, but
> > nothing else, as far as config goes...
> > 
> > I have more information now too, to help throw gas on the fire.
> > 
> > I've now built the same kernel, but with old-vgic and 64K pages. Guests
> > don't boot with that either. kvm-unit-tests tests pass, except for the
> > smp test. The secondary does nothing, the primary waits on it (wfe)
> > forever. Unit tests all pass and guests (even smp) boot with the same
> > kernel built with both new and old vgic, but with 4K pages.
> > 
> > I checked where the guest was when it wasn't booting. It's wfi in
> > cpu_do_idle. So now we have do_raw_spin_lock (wfe related), an wfe
> > related issue with kvm-unit-tests, and a wfi issue with guest boot.
> > This makes me think that this issue is not strictly new-vgic related,
> > but rather wfx (and somehow 64K pages) related.
> 
> The guest locked in WFI is quite typical of waiting for an interrupt to
> be delivered (usually a timer). Being locked there tends to indicate
> that we're not making progress on that front.
> 
> Would you, by any chance, be booting with ACPI? If so, could you dump
> which addresses your GIC is reported at? I'll be able to compare that
> with my Seattle on Monday.

I'm not using ACPI for these latest upstream builds. And, as I don't
have a custom DT, I presume that means the DT I'm using is
arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi

Thanks,
drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  9:00               ` Andrew Jones
@ 2016-07-25  9:05                 ` Marc Zyngier
  2016-07-25  9:18                   ` Andrew Jones
  0 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25  9:05 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 25/07/16 10:00, Andrew Jones wrote:
> On Fri, Jul 22, 2016 at 08:54:28PM +0100, Marc Zyngier wrote:
>> On Fri, 22 Jul 2016 21:45:00 +0200
>> Andrew Jones <drjones@redhat.com> wrote:
>>
>>> On Fri, Jul 22, 2016 at 07:06:36PM +0100, Marc Zyngier wrote:
>>>> On 22/07/16 18:38, Andrew Jones wrote:  
>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
>>>>>> On 22/07/16 15:35, Andrew Jones wrote:  
>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
>>>>>>>> Hi Stefan,
>>>>>>>>
>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:  
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>
>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>> pgd = 8ca52740
>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>> Modules linked in:  
>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>> 00000000
>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>> 810074f8
>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>> 8ca5f800
>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>> 7ffbfeff
>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>> ffffe000
>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>> 8023f248
>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>> 00000000
>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>> 00000000
>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>> 80bc2ec4
>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>> 007c1e70
>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>> 00000000
>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>> 00000036
>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>> 755feac0
>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>> 755fec6c
>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>> 00000000
>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>
>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>
>>>>>>>>> Using a bit older Qemu version 2.4.0.  
>>>>>>>>
>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>> on a Midway (Cortex-A15).  
>>>>>>>
>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>  
>>>>>>>>
>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?  
>>>>>>>
>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>
>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>> a few minutes.  
>>>>>>
>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>> tremendously helpful.  
>>>>>
>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>> selection.  
>>>>
>>>> root@flakes:~# zgrep 64K /proc/config.gz
>>>> CONFIG_ARM64_64K_PAGES=y
>>>>
>>>> VMs up and running. It is definitely something else, potentially
>>>> affected by the page size. This is going to be a fun weekend.
>>>>
>>>> Thanks for having had a look!  
>>>
>>> Ah... I didn't even notice the 32-bit addresses above, only the
>>>
>>>  PC is at do_raw_spin_lock+0x8/0x1dc
>>>  LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>
>>> which matches the backtrace I get with a 64-bit guest. And I really
>>> only change PAGE_SIZE between a host kernel that works and doesn't,
>>> which does also change ARM64_CONT_SHIFT and PGTABLE_LEVELS, but
>>> nothing else, as far as config goes...
>>>
>>> I have more information now too, to help throw gas on the fire.
>>>
>>> I've now built the same kernel, but with old-vgic and 64K pages. Guests
>>> don't boot with that either. kvm-unit-tests tests pass, except for the
>>> smp test. The secondary does nothing, the primary waits on it (wfe)
>>> forever. Unit tests all pass and guests (even smp) boot with the same
>>> kernel built with both new and old vgic, but with 4K pages.
>>>
>>> I checked where the guest was when it wasn't booting. It's wfi in
>>> cpu_do_idle. So now we have do_raw_spin_lock (wfe related), an wfe
>>> related issue with kvm-unit-tests, and a wfi issue with guest boot.
>>> This makes me think that this issue is not strictly new-vgic related,
>>> but rather wfx (and somehow 64K pages) related.
>>
>> The guest locked in WFI is quite typical of waiting for an interrupt to
>> be delivered (usually a timer). Being locked there tends to indicate
>> that we're not making progress on that front.
>>
>> Would you, by any chance, be booting with ACPI? If so, could you dump
>> which addresses your GIC is reported at? I'll be able to compare that
>> with my Seattle on Monday.
> 
> I'm not using ACPI for these latest upstream builds. And, as I don't
> have a custom DT, I presume that means the DT I'm using is
> arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi

OK, that clears it on that front (Seattle+ACPI+64k+KVM is a bit of a
nightmare combo at the moment).

I'm still not able to reproduce any of these two reports, even with
Stefan's config. Can you send me the one that did crash on your Seattle?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  9:05                 ` Marc Zyngier
@ 2016-07-25  9:18                   ` Andrew Jones
  0 siblings, 0 replies; 45+ messages in thread
From: Andrew Jones @ 2016-07-25  9:18 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Mon, Jul 25, 2016 at 10:05:48AM +0100, Marc Zyngier wrote:
> On 25/07/16 10:00, Andrew Jones wrote:
> > On Fri, Jul 22, 2016 at 08:54:28PM +0100, Marc Zyngier wrote:
> >> On Fri, 22 Jul 2016 21:45:00 +0200
> >> Andrew Jones <drjones@redhat.com> wrote:
> >>
> >>> On Fri, Jul 22, 2016 at 07:06:36PM +0100, Marc Zyngier wrote:
> >>>> On 22/07/16 18:38, Andrew Jones wrote:  
> >>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:  
> >>>>>> On 22/07/16 15:35, Andrew Jones wrote:  
> >>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:  
> >>>>>>>> Hi Stefan,
> >>>>>>>>
> >>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:  
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
> >>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
> >>>>>>>>>
> >>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
> >>>>>>>>> pgd = 8ca52740
> >>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
> >>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
> >>>>>>>>> Modules linked in:  
> >>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W      
> >>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
> >>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
> >>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
> >>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
> >>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
> >>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
> >>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
> >>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
> >>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
> >>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
> >>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
> >>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
> >>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
> >>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
> >>>>>>>>> 1e20:                                                       ffffffe0
> >>>>>>>>> 00000000
> >>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
> >>>>>>>>> 810074f8
> >>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
> >>>>>>>>> 8ca5f800
> >>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
> >>>>>>>>> 7ffbfeff
> >>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
> >>>>>>>>> ffffe000
> >>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
> >>>>>>>>> 8023f248
> >>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
> >>>>>>>>> 00000000
> >>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
> >>>>>>>>> 00000000
> >>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
> >>>>>>>>> 80bc2ec4
> >>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
> >>>>>>>>> 007c1e70
> >>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
> >>>>>>>>> 00000000
> >>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
> >>>>>>>>> 00000036
> >>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
> >>>>>>>>> 755feac0
> >>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
> >>>>>>>>> 755fec6c
> >>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
> >>>>>>>>> 00000000
> >>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
> >>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
> >>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
> >>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
> >>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
> >>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
> >>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
> >>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
> >>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
> >>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
> >>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
> >>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
> >>>>>>>>>
> >>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
> >>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
> >>>>>>>>> -nographic -serial stdio -kernel zImage).
> >>>>>>>>>
> >>>>>>>>> Using a bit older Qemu version 2.4.0.  
> >>>>>>>>
> >>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
> >>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
> >>>>>>>> on a Midway (Cortex-A15).  
> >>>>>>>
> >>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
> >>>>>>> (I haven't tried anywhere else yet)
> >>>>>>>  
> >>>>>>>>
> >>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?  
> >>>>>>>
> >>>>>>> Disabling NEW_VGIC "fixes" guest boots.
> >>>>>>>
> >>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
> >>>>>>> tests and provide a comparison of my config vs. a defconfig in
> >>>>>>> a few minutes.  
> >>>>>>
> >>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
> >>>>>> If you can narrow it down to the difference with defconfig, that'd be
> >>>>>> tremendously helpful.  
> >>>>>
> >>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
> >>>>> selection.  
> >>>>
> >>>> root@flakes:~# zgrep 64K /proc/config.gz
> >>>> CONFIG_ARM64_64K_PAGES=y
> >>>>
> >>>> VMs up and running. It is definitely something else, potentially
> >>>> affected by the page size. This is going to be a fun weekend.
> >>>>
> >>>> Thanks for having had a look!  
> >>>
> >>> Ah... I didn't even notice the 32-bit addresses above, only the
> >>>
> >>>  PC is at do_raw_spin_lock+0x8/0x1dc
> >>>  LR is at kvm_vgic_flush_hwstate+0x8c/0x224
> >>>
> >>> which matches the backtrace I get with a 64-bit guest. And I really
> >>> only change PAGE_SIZE between a host kernel that works and doesn't,
> >>> which does also change ARM64_CONT_SHIFT and PGTABLE_LEVELS, but
> >>> nothing else, as far as config goes...
> >>>
> >>> I have more information now too, to help throw gas on the fire.
> >>>
> >>> I've now built the same kernel, but with old-vgic and 64K pages. Guests
> >>> don't boot with that either. kvm-unit-tests tests pass, except for the
> >>> smp test. The secondary does nothing, the primary waits on it (wfe)
> >>> forever. Unit tests all pass and guests (even smp) boot with the same
> >>> kernel built with both new and old vgic, but with 4K pages.
> >>>
> >>> I checked where the guest was when it wasn't booting. It's wfi in
> >>> cpu_do_idle. So now we have do_raw_spin_lock (wfe related), an wfe
> >>> related issue with kvm-unit-tests, and a wfi issue with guest boot.
> >>> This makes me think that this issue is not strictly new-vgic related,
> >>> but rather wfx (and somehow 64K pages) related.
> >>
> >> The guest locked in WFI is quite typical of waiting for an interrupt to
> >> be delivered (usually a timer). Being locked there tends to indicate
> >> that we're not making progress on that front.
> >>
> >> Would you, by any chance, be booting with ACPI? If so, could you dump
> >> which addresses your GIC is reported at? I'll be able to compare that
> >> with my Seattle on Monday.
> > 
> > I'm not using ACPI for these latest upstream builds. And, as I don't
> > have a custom DT, I presume that means the DT I'm using is
> > arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi
> 
> OK, that clears it on that front (Seattle+ACPI+64k+KVM is a bit of a
> nightmare combo at the moment).
> 
> I'm still not able to reproduce any of these two reports, even with
> Stefan's config. Can you send me the one that did crash on your Seattle?

Sent in a private mail, but feel free to share as you like.

Thanks,
drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  6:36                 ` Stefan Agner
@ 2016-07-25 13:33                   ` Andre Przywara
  2016-07-25 16:18                     ` Stefan Agner
  0 siblings, 1 reply; 45+ messages in thread
From: Andre Przywara @ 2016-07-25 13:33 UTC (permalink / raw)
  To: Stefan Agner, Marc Zyngier; +Cc: kvmarm

Hi Stefan,

On 25/07/16 07:36, Stefan Agner wrote:
> On 2016-07-24 05:36, Marc Zyngier wrote:
>> On Sun, 24 Jul 2016 13:22:55 +0100
>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>
>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>> Stefan Agner <stefan@agner.ch> wrote:
>>>
>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>> Hi Stefan,
>>>>>>>>>
>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>
>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>> Modules linked in:
>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>> 00000000
>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>> 810074f8
>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>> 8ca5f800
>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>> 7ffbfeff
>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>> ffffe000
>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>> 8023f248
>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>> 80bc2ec4
>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>> 007c1e70
>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>> 00000000
>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>> 00000036
>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>> 755feac0
>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>> 755fec6c
>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>> 00000000
>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>
>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>
>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>
>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>
>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>
>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>
>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>> a few minutes.
>>>>>>>
>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>> tremendously helpful.
>>>>>>
>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>> selection.
>>>>>
>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>
>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>> got that right :-)
>>>>
>>>> What defconfig do you use? I could reproduce the issue also with
>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>
>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>> built-in to make my life simpler). The host works perfectly, and I can
>>> spawn VMs without any issue.
>>>
>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>> something more recent (2.5), same effect.
>>>
>>>>
>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>> clock next to get to the bits and pieces required for my board...
>>>>
>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>> platform independent...
>>>
>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>> probably see other things exploding. So we need to find out where we
>>> are diverging.
>>>
>>> What compiler are you using? I just noticed that my build
>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>> going to upgrade that to gcc 5.3 and retest.
> 
> As you expected, the clock fix did not influence this problem. Still the
> same. I ran strace several times, the crash seems to happen always about
> the same time, maybe this gives you a hint?
> 
> ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
> mmap2(NULL, 2101248, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0xa3bff000
> mmap2(0xa3c00000, 4096, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa3c00000
> munmap(0xa3bff000, 4096)                = 0
> munmap(0xa3c02000, 2088960)             = 0
> madvise(0xa3c00000, 4096, MADV_MERGEABLE) = -1 EINVAL (Invalid argument)
> madvise(0xa3c00000, 4096, MADV_HUGEPAGE) = -1 EINVAL (Invalid argument)
> madvise(0xa3c00000, 4096, MADV_DONTFORK) = 0
> ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
> futex(0x9afe3c, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x4957a8, 4) =
> 1
> tgkill(450, 452, SIGUSR1)               = 0
> futex(0x4957a8, FUTEX_WAKE_PRIVATE, 1)  = 1
> futex(0x4956a8, FUTEX_WAKE_PRIVATE, 1)  = 1
> futex(0x4956ac, FUTEX_WAIT_PRIVATE, 3, NULL) = -1 EAGAIN (Resource
> temporarily unavailable)
> ioctl(11, KVM_ARM_VCPU_INIT, 0xbe8be99c) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
> [   20.383970] Unable to handle kernel paging request at virtual address
> fffffffc


Did you run that strace with -f to catch the children's (VCPUs) ioctls
as well? If not, can you do this, please?
I get this sequence here on my (non-crashing) system (4.7-rc7
defconfig+kvm running on a BananaPi (dual A7 Allwinner A20)):
http://pastebin.com/ayuZMAp9
This is with QEMU 2.5.0 and:
$ strace -e trace=ioctl -f -o /dev/shm/strace.log qemu-system-arm
-enable-kvm -M virt -cpu host -serial stdio -append
"console=ttyAMA0,115200n8" -kernel zImage-4.7-rc7

I think the interesting ioctls are from the VCPUs, so can you try to
catch them as well?

Thanks,
Andre.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  8:17                     ` Marc Zyngier
@ 2016-07-25 13:50                       ` Andre Przywara
  2016-07-25 14:05                         ` Marc Zyngier
  0 siblings, 1 reply; 45+ messages in thread
From: Andre Przywara @ 2016-07-25 13:50 UTC (permalink / raw)
  To: Marc Zyngier, Stefan Agner; +Cc: kvmarm

Hi,

On 25/07/16 09:17, Marc Zyngier wrote:
> On 25/07/16 09:11, Marc Zyngier wrote:
>> On 25/07/16 07:14, Stefan Agner wrote:
>>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>>
>>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>>
>>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>>> Hi Stefan,
>>>>>>>>>>>
>>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>>
>>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>>> Modules linked in:
>>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>>> 810074f8
>>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>>> 8ca5f800
>>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>>> ffffe000
>>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>>> 8023f248
>>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>>> 007c1e70
>>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>>> 00000036
>>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>>> 755feac0
>>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>>> 755fec6c
>>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>>
>>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>>
>>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>>
>>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>>
>>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>>
>>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>>
>>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>>> a few minutes.
>>>>>>>>>
>>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>>> tremendously helpful.
>>>>>>>>
>>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>>> selection.
>>>>>>>
>>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>>
>>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>>> got that right :-)
>>>>>>
>>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>>
>>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>>> spawn VMs without any issue.
>>>>>
>>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>>> something more recent (2.5), same effect.
>>>>>
>>>>>>
>>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>>> clock next to get to the bits and pieces required for my board...
>>>>>>
>>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>>> platform independent...
>>>>>
>>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>>> probably see other things exploding. So we need to find out where we
>>>>> are diverging.
>>>>>
>>>>> What compiler are you using? I just noticed that my build
>>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>>> going to upgrade that to gcc 5.3 and retest.
>>>>
>>>> Same thing. The damn thing stubbornly works.
>>>>
>>>> Please send your full configuration, compiler version, exact QEMU
>>>> command line, and any other detail that could be vaguely relevant. As
>>>> the old VGIC gets removed in 4.8, we definitely need to nail that
>>>> sucker right now.
>>>
>>> I built the kernel with
>>> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
>>> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
>>> the same compiler version, but built using OpenEmbedded.
>>>
>>> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
>>> that much on mainline but it seems to be rather stable so far.
>>>
>>> I can reproduce the issue with a minimal command such as this:
>>> qemu-system-arm -enable-kvm -M virt -cpu host
>>>
>>> [  179.430694] Unable to handle kernel paging request at virtual address
>>> fffffffc
>>> What is puzzling me a bit that the address the kernel tries to access is
>>> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
>>> unhandled error return?
>>
>> Your initial report had 0xffffffe4 instead. Which looks a bit like a
>> "container_of" operation on a NULL pointer. Do you always get the same
>> backtrace? If so, any chance you could run a
>>
>> arm-linux-gnueabihf-addr2line -e vmlinux -i TheCrashingPC
> 
> Actually, try with the LR value, not the PC.

I didn't see it crash, but from comparing the PC offsets of my
disassembly and Stefan's and correlating the assembly with the C code I
am quite sure it's this lock here:

static void vgic_flush_lr_state(struct kvm_vcpu *vcpu)
{
....
	list_for_each_entry(irq, &vgic_cpu->ap_list_head, ap_list) }
  ----->	spin_lock(&irq->irq_lock);

		if (unlikely(vgic_target_oracle(irq) != vcpu))
			goto next;

I can see from the assembly that we would call _raw_spin_lock with -4 in
r0 if the list pointer would be NULL, which makes me wonder if we either
step on an uninitialised VCPU or if it's a bogus IRQ we are looking at?

Cheers,
Andre.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 13:50                       ` Andre Przywara
@ 2016-07-25 14:05                         ` Marc Zyngier
  2016-07-25 14:28                           ` Andrew Jones
  0 siblings, 1 reply; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25 14:05 UTC (permalink / raw)
  To: Andre Przywara, Stefan Agner; +Cc: kvmarm

On 25/07/16 14:50, Andre Przywara wrote:
> Hi,
> 
> On 25/07/16 09:17, Marc Zyngier wrote:
>> On 25/07/16 09:11, Marc Zyngier wrote:
>>> On 25/07/16 07:14, Stefan Agner wrote:
>>>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>>>
>>>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>>>
>>>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>>>> Hi Stefan,
>>>>>>>>>>>>
>>>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>>>> Modules linked in:
>>>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>>>> 00000000
>>>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>>>> 810074f8
>>>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>>>> 8ca5f800
>>>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>>>> ffffe000
>>>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>>>> 8023f248
>>>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>>>> 00000000
>>>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>>>> 00000000
>>>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>>>> 007c1e70
>>>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>>>> 00000000
>>>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>>>> 00000036
>>>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>>>> 755feac0
>>>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>>>> 755fec6c
>>>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>>>> 00000000
>>>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>>>
>>>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>>>
>>>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>>>
>>>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>>>
>>>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>>>
>>>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>>>> a few minutes.
>>>>>>>>>>
>>>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>>>> tremendously helpful.
>>>>>>>>>
>>>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>>>> selection.
>>>>>>>>
>>>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>>>
>>>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>>>> got that right :-)
>>>>>>>
>>>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>>>
>>>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>>>> spawn VMs without any issue.
>>>>>>
>>>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>>>> something more recent (2.5), same effect.
>>>>>>
>>>>>>>
>>>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>>>> clock next to get to the bits and pieces required for my board...
>>>>>>>
>>>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>>>> platform independent...
>>>>>>
>>>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>>>> probably see other things exploding. So we need to find out where we
>>>>>> are diverging.
>>>>>>
>>>>>> What compiler are you using? I just noticed that my build
>>>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>>>> going to upgrade that to gcc 5.3 and retest.
>>>>>
>>>>> Same thing. The damn thing stubbornly works.
>>>>>
>>>>> Please send your full configuration, compiler version, exact QEMU
>>>>> command line, and any other detail that could be vaguely relevant. As
>>>>> the old VGIC gets removed in 4.8, we definitely need to nail that
>>>>> sucker right now.
>>>>
>>>> I built the kernel with
>>>> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
>>>> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
>>>> the same compiler version, but built using OpenEmbedded.
>>>>
>>>> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
>>>> that much on mainline but it seems to be rather stable so far.
>>>>
>>>> I can reproduce the issue with a minimal command such as this:
>>>> qemu-system-arm -enable-kvm -M virt -cpu host
>>>>
>>>> [  179.430694] Unable to handle kernel paging request at virtual address
>>>> fffffffc
>>>> What is puzzling me a bit that the address the kernel tries to access is
>>>> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
>>>> unhandled error return?
>>>
>>> Your initial report had 0xffffffe4 instead. Which looks a bit like a
>>> "container_of" operation on a NULL pointer. Do you always get the same
>>> backtrace? If so, any chance you could run a
>>>
>>> arm-linux-gnueabihf-addr2line -e vmlinux -i TheCrashingPC
>>
>> Actually, try with the LR value, not the PC.
> 
> I didn't see it crash, but from comparing the PC offsets of my
> disassembly and Stefan's and correlating the assembly with the C code I
> am quite sure it's this lock here:
> 
> static void vgic_flush_lr_state(struct kvm_vcpu *vcpu)
> {
> ....
> 	list_for_each_entry(irq, &vgic_cpu->ap_list_head, ap_list) }
>   ----->	spin_lock(&irq->irq_lock);
> 
> 		if (unlikely(vgic_target_oracle(irq) != vcpu))
> 			goto next;
> 
> I can see from the assembly that we would call _raw_spin_lock with -4 in
> r0 if the list pointer would be NULL, which makes me wonder if we either
> step on an uninitialised VCPU or if it's a bogus IRQ we are looking at?

Drew saw it pointing at the similar sequence in compute_ap_list_depth.

News flash: Mark Rutland just saw it crashing on his Seattle using my
kernel that doesn't crash on mine. So we're looking at external factors
now. DT, firmware, whatever.

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 14:05                         ` Marc Zyngier
@ 2016-07-25 14:28                           ` Andrew Jones
  2016-07-25 14:39                             ` Marc Zyngier
  2016-07-25 15:07                             ` Marc Zyngier
  0 siblings, 2 replies; 45+ messages in thread
From: Andrew Jones @ 2016-07-25 14:28 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
> News flash: Mark Rutland just saw it crashing on his Seattle using my
> kernel that doesn't crash on mine. So we're looking at external factors
> now. DT, firmware, whatever.

Interesting, especially with the information that the bug is also
on v7 with uboot (where it's present with 4k pages), and on v8
with UEFI (where it's not present with 4k pages, only 64k)

drew

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 14:28                           ` Andrew Jones
@ 2016-07-25 14:39                             ` Marc Zyngier
  2016-07-25 15:07                             ` Marc Zyngier
  1 sibling, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25 14:39 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 25/07/16 15:28, Andrew Jones wrote:
> On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
>> News flash: Mark Rutland just saw it crashing on his Seattle using my
>> kernel that doesn't crash on mine. So we're looking at external factors
>> now. DT, firmware, whatever.
> 
> Interesting, especially with the information that the bug is also
> on v7 with uboot (where it's present with 4k pages), and on v8
> with UEFI (where it's not present with 4k pages, only 64k)

Yup. Transplanting Mark's DT to my Seattle had finally triggered it.
Time for some diff'ing...

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 14:28                           ` Andrew Jones
  2016-07-25 14:39                             ` Marc Zyngier
@ 2016-07-25 15:07                             ` Marc Zyngier
  2016-07-25 15:25                               ` Andre Przywara
  2016-07-25 15:29                               ` Andrew Jones
  1 sibling, 2 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25 15:07 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 25/07/16 15:28, Andrew Jones wrote:
> On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
>> News flash: Mark Rutland just saw it crashing on his Seattle using my
>> kernel that doesn't crash on mine. So we're looking at external factors
>> now. DT, firmware, whatever.
> 
> Interesting, especially with the information that the bug is also
> on v7 with uboot (where it's present with 4k pages), and on v8
> with UEFI (where it's not present with 4k pages, only 64k)

Here's what I get with Mark's DT:

[    2.199618] kvm [1]: 8-bit VMID
[    2.202756] kvm [1]: Hyp mode initialized successfully
[    2.207907] kvm [1]: GICV size 0x2000 not a multiple of page size 0x10000
[    2.214736] kvm [1]: virtual timer IRQ4

Somehow, we fail to detect that we cannot run with 64k pages,
because we cannot safely pass the 8kB region to the guest.
KVM should fail to initialize, or at least report that there
is no VGIC. Drew, is that what you have on your system as well?

That doesn't explain Stefan's issue though.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 15:07                             ` Marc Zyngier
@ 2016-07-25 15:25                               ` Andre Przywara
  2016-07-25 15:29                               ` Andrew Jones
  1 sibling, 0 replies; 45+ messages in thread
From: Andre Przywara @ 2016-07-25 15:25 UTC (permalink / raw)
  To: Marc Zyngier, Andrew Jones; +Cc: kvmarm

Hi,

On 25/07/16 16:07, Marc Zyngier wrote:
> On 25/07/16 15:28, Andrew Jones wrote:
>> On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
>>> News flash: Mark Rutland just saw it crashing on his Seattle using my
>>> kernel that doesn't crash on mine. So we're looking at external factors
>>> now. DT, firmware, whatever.
>>
>> Interesting, especially with the information that the bug is also
>> on v7 with uboot (where it's present with 4k pages), and on v8
>> with UEFI (where it's not present with 4k pages, only 64k)
> 
> Here's what I get with Mark's DT:
> 
> [    2.199618] kvm [1]: 8-bit VMID
> [    2.202756] kvm [1]: Hyp mode initialized successfully
> [    2.207907] kvm [1]: GICV size 0x2000 not a multiple of page size 0x10000
> [    2.214736] kvm [1]: virtual timer IRQ4

Stefan, can you check whether you see something similar in your host
dmesg after booting? Do you use a DT that is based upon the upstream
imx7d.dtsi? Do you have an interrupt defined in there? Can you post the
DT, or at least the gic node?

> Somehow, we fail to detect that we cannot run with 64k pages,
> because we cannot safely pass the 8kB region to the guest.
> KVM should fail to initialize, or at least report that there
> is no VGIC. Drew, is that what you have on your system as well?

So chasing back the error path I see that we don't fail KVM entirely,
just set vgic_present to false. But that variable exists in
arch/arm/kvm/arm.c only and we don't check it in the VGIC code. Chasing
that trace now ...

Cheers,
Andre.

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 15:07                             ` Marc Zyngier
  2016-07-25 15:25                               ` Andre Przywara
@ 2016-07-25 15:29                               ` Andrew Jones
  2016-07-25 15:38                                 ` Marc Zyngier
  1 sibling, 1 reply; 45+ messages in thread
From: Andrew Jones @ 2016-07-25 15:29 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On Mon, Jul 25, 2016 at 04:07:20PM +0100, Marc Zyngier wrote:
> On 25/07/16 15:28, Andrew Jones wrote:
> > On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
> >> News flash: Mark Rutland just saw it crashing on his Seattle using my
> >> kernel that doesn't crash on mine. So we're looking at external factors
> >> now. DT, firmware, whatever.
> > 
> > Interesting, especially with the information that the bug is also
> > on v7 with uboot (where it's present with 4k pages), and on v8
> > with UEFI (where it's not present with 4k pages, only 64k)
> 
> Here's what I get with Mark's DT:
> 
> [    2.199618] kvm [1]: 8-bit VMID
> [    2.202756] kvm [1]: Hyp mode initialized successfully
> [    2.207907] kvm [1]: GICV size 0x2000 not a multiple of page size 0x10000
> [    2.214736] kvm [1]: virtual timer IRQ4
> 
> Somehow, we fail to detect that we cannot run with 64k pages,
> because we cannot safely pass the 8kB region to the guest.
> KVM should fail to initialize, or at least report that there
> is no VGIC. Drew, is that what you have on your system as well?

Yup, precisely. I wish I would have grepped and reported that before...

I also now see that when booting with old vgic and 64k pages I get an
additional message after the GICV... line

[    1.889241] kvm [1]: error: KVM vGIC probing failed

So we should port that error message over.

Thanks,
drew

> 
> That doesn't explain Stefan's issue though.
> 
> Thanks,
> 
> 	M.
> -- 
> Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 15:29                               ` Andrew Jones
@ 2016-07-25 15:38                                 ` Marc Zyngier
  0 siblings, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25 15:38 UTC (permalink / raw)
  To: Andrew Jones; +Cc: Andre Przywara, kvmarm

On 25/07/16 16:29, Andrew Jones wrote:
> On Mon, Jul 25, 2016 at 04:07:20PM +0100, Marc Zyngier wrote:
>> On 25/07/16 15:28, Andrew Jones wrote:
>>> On Mon, Jul 25, 2016 at 03:05:46PM +0100, Marc Zyngier wrote:
>>>> News flash: Mark Rutland just saw it crashing on his Seattle using my
>>>> kernel that doesn't crash on mine. So we're looking at external factors
>>>> now. DT, firmware, whatever.
>>>
>>> Interesting, especially with the information that the bug is also
>>> on v7 with uboot (where it's present with 4k pages), and on v8
>>> with UEFI (where it's not present with 4k pages, only 64k)
>>
>> Here's what I get with Mark's DT:
>>
>> [    2.199618] kvm [1]: 8-bit VMID
>> [    2.202756] kvm [1]: Hyp mode initialized successfully
>> [    2.207907] kvm [1]: GICV size 0x2000 not a multiple of page size 0x10000
>> [    2.214736] kvm [1]: virtual timer IRQ4
>>
>> Somehow, we fail to detect that we cannot run with 64k pages,
>> because we cannot safely pass the 8kB region to the guest.
>> KVM should fail to initialize, or at least report that there
>> is no VGIC. Drew, is that what you have on your system as well?
> 
> Yup, precisely. I wish I would have grepped and reported that before...
> 
> I also now see that when booting with old vgic and 64k pages I get an
> additional message after the GICV... line
> 
> [    1.889241] kvm [1]: error: KVM vGIC probing failed
> 
> So we should port that error message over.

Not just the message. Somehow, the rest of KVM still thinks we have
things up and running, while we won't be able to deliver an interrupt.
Pretty shit.

Now, coming back to Stefan's issue, I see that his DT lacks a
maintenance interrupt in the GIC node, which would be another failure
mode. Except that he says that it works with the old vgic. That's weird.

Basically, our error handling is bonkers and needs fixing.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 13:33                   ` Andre Przywara
@ 2016-07-25 16:18                     ` Stefan Agner
  0 siblings, 0 replies; 45+ messages in thread
From: Stefan Agner @ 2016-07-25 16:18 UTC (permalink / raw)
  To: Andre Przywara; +Cc: Marc Zyngier, kvmarm

On 2016-07-25 06:33, Andre Przywara wrote:
> Hi Stefan,
> 
> On 25/07/16 07:36, Stefan Agner wrote:
>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>
>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>
>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>> Hi Stefan,
>>>>>>>>>>
>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>
>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>> Modules linked in:
>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>> 810074f8
>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>> 8ca5f800
>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>> ffffe000
>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>> 8023f248
>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>> 007c1e70
>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>> 00000036
>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>> 755feac0
>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>> 755fec6c
>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>
>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>
>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>
>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>
>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>
>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>
>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>> a few minutes.
>>>>>>>>
>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>> tremendously helpful.
>>>>>>>
>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>> selection.
>>>>>>
>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>
>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>> got that right :-)
>>>>>
>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>
>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>> spawn VMs without any issue.
>>>>
>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>> something more recent (2.5), same effect.
>>>>
>>>>>
>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>> clock next to get to the bits and pieces required for my board...
>>>>>
>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>> platform independent...
>>>>
>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>> probably see other things exploding. So we need to find out where we
>>>> are diverging.
>>>>
>>>> What compiler are you using? I just noticed that my build
>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>> going to upgrade that to gcc 5.3 and retest.
>>
>> As you expected, the clock fix did not influence this problem. Still the
>> same. I ran strace several times, the crash seems to happen always about
>> the same time, maybe this gives you a hint?
>>
>> ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
>> mmap2(NULL, 2101248, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
>> 0xa3bff000
>> mmap2(0xa3c00000, 4096, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa3c00000
>> munmap(0xa3bff000, 4096)                = 0
>> munmap(0xa3c02000, 2088960)             = 0
>> madvise(0xa3c00000, 4096, MADV_MERGEABLE) = -1 EINVAL (Invalid argument)
>> madvise(0xa3c00000, 4096, MADV_HUGEPAGE) = -1 EINVAL (Invalid argument)
>> madvise(0xa3c00000, 4096, MADV_DONTFORK) = 0
>> ioctl(9, KVM_CHECK_EXTENSION or LOGGER_GET_NEXT_ENTRY_LEN, 0x10) = 1
>> futex(0x9afe3c, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x4957a8, 4) =
>> 1
>> tgkill(450, 452, SIGUSR1)               = 0
>> futex(0x4957a8, FUTEX_WAKE_PRIVATE, 1)  = 1
>> futex(0x4956a8, FUTEX_WAKE_PRIVATE, 1)  = 1
>> futex(0x4956ac, FUTEX_WAIT_PRIVATE, 3, NULL) = -1 EAGAIN (Resource
>> temporarily unavailable)
>> ioctl(11, KVM_ARM_VCPU_INIT, 0xbe8be99c) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> ioctl(11, KVM_ARM_SET_DEVICE_ADDR or KVM_GET_ONE_REG, 0xbe8be998) = 0
>> [   20.383970] Unable to handle kernel paging request at virtual address
>> fffffffc
> 
> 
> Did you run that strace with -f to catch the children's (VCPUs) ioctls
> as well? If not, can you do this, please?

I did not. This run is with -f:

http://pastebin.com/2sUi0P1k

> I get this sequence here on my (non-crashing) system (4.7-rc7
> defconfig+kvm running on a BananaPi (dual A7 Allwinner A20)):
> http://pastebin.com/ayuZMAp9
> This is with QEMU 2.5.0 and:
> $ strace -e trace=ioctl -f -o /dev/shm/strace.log qemu-system-arm
> -enable-kvm -M virt -cpu host -serial stdio -append
> "console=ttyAMA0,115200n8" -kernel zImage-4.7-rc7
> 
> I think the interesting ioctls are from the VCPUs, so can you try to
> catch them as well?

After that trace, there is no more strace output, it seems that the
thread gets killed by SIGSEGV.

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25  8:11                   ` Marc Zyngier
  2016-07-25  8:17                     ` Marc Zyngier
@ 2016-07-25 16:52                     ` Stefan Agner
  2016-07-25 17:06                       ` Marc Zyngier
  1 sibling, 1 reply; 45+ messages in thread
From: Stefan Agner @ 2016-07-25 16:52 UTC (permalink / raw)
  To: Marc Zyngier; +Cc: Andre Przywara, kvmarm

On 2016-07-25 01:11, Marc Zyngier wrote:
> On 25/07/16 07:14, Stefan Agner wrote:
>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>
>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>
>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>> Hi Stefan,
>>>>>>>>>>
>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>
>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>> Modules linked in:
>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>> 810074f8
>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>> 8ca5f800
>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>> ffffe000
>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>> 8023f248
>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>> 007c1e70
>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>> 00000000
>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>> 00000036
>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>> 755feac0
>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>> 755fec6c
>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>> 00000000
>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>
>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>
>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>
>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>
>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>
>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>
>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>> a few minutes.
>>>>>>>>
>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>> tremendously helpful.
>>>>>>>
>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>> selection.
>>>>>>
>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>
>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>> got that right :-)
>>>>>
>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>
>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>> spawn VMs without any issue.
>>>>
>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>> something more recent (2.5), same effect.
>>>>
>>>>>
>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>> clock next to get to the bits and pieces required for my board...
>>>>>
>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>> platform independent...
>>>>
>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>> probably see other things exploding. So we need to find out where we
>>>> are diverging.
>>>>
>>>> What compiler are you using? I just noticed that my build
>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>> going to upgrade that to gcc 5.3 and retest.
>>>
>>> Same thing. The damn thing stubbornly works.
>>>
>>> Please send your full configuration, compiler version, exact QEMU
>>> command line, and any other detail that could be vaguely relevant. As
>>> the old VGIC gets removed in 4.8, we definitely need to nail that
>>> sucker right now.
>>
>> I built the kernel with
>> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
>> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
>> the same compiler version, but built using OpenEmbedded.
>>
>> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
>> that much on mainline but it seems to be rather stable so far.
>>
>> I can reproduce the issue with a minimal command such as this:
>> qemu-system-arm -enable-kvm -M virt -cpu host
>>
>> [  179.430694] Unable to handle kernel paging request at virtual address
>> fffffffc
>> What is puzzling me a bit that the address the kernel tries to access is
>> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
>> unhandled error return?
> 
> Your initial report had 0xffffffe4 instead. Which looks a bit like a
> "container_of" operation on a NULL pointer. Do you always get the same
> backtrace? If so, any chance you could run a
> 

For completeness here, after changing to the multi_v7_defconfig, the
stacktrace changed slightly. This is the stack trace using
multi_v7_defconfig + LPAE + KVM.

[   14.166422] Unable to handle kernel paging request at virtual address
fffffffc
[   14.173727] pgd = d90fba80
[   14.176491] [fffffffc] *pgd=80000080207003, *pmd=9bfde003,
*pte=00000000
[   14.183297] Internal error: Oops: 207 [#1] SMP ARM
[   14.188095] Modules linked in:
[   14.191170] CPU: 0 PID: 539 Comm: qemu-system-arm Not tainted
4.7.0-rc7-00250-gda34b82-dirty #125
[   14.200048] Hardware name: Freescale i.MX7 Dual (Device Tree)
[   14.205801] task: db6b1a40 ti: d9138000 task.ti: d9138000
[   14.211213] PC is at _raw_spin_lock+0x4/0x40
[   14.215491] LR is at kvm_vgic_flush_hwstate+0x74/0x21c
[   14.220637] pc : [<c0ca7a5c>]    lr : [<c0416a1c>]    psr: a0070013
[   14.220637] sp : d9139e58  ip : da206000  fp : 00000000
[   14.232141] r10: c17100f4  r9 : c16076c8  r8 : d9140a90
[   14.237378] r7 : d9140000  r6 : 00000000  r5 : c16076b8  r4 :
fffffffc
[   14.243919] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 :
fffffffc
[   14.250461] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM 
Segment user
[   14.257610] Control: 30c5387d  Table: 990fba80  DAC: fffffffd
[   14.263369] Process qemu-system-arm (pid: 539, stack limit =
0xd9138220)
[   14.270084] Stack: (0xd9139e58 to 0xd913a000)
[   14.274454] 9e40:                                                    
  d9140000 c16076b8
[   14.282656] 9e60: 00000000 00ff0000 00000001 c040f610 db6b1e10
d9138000 d90f9000 c17100f4
[   14.290859] 9e80: c1602410 00000001 00000000 00010000 00000000
00ff0000 00000000 7ffbfeff
[   14.299061] 9ea0: fffffffe 00495000 db6516c0 000007a8 00000001
00000000 00000000 ffffe000
[   14.307263] 9ec0: d9140000 00000000 d9109780 00000000 0089d188
c040acc8 c041a124 b5ff398c
[   14.315465] 9ee0: 00000080 00000000 fffffffa c046268c 0000000a
b5ff398c d9139f08 00000000
[   14.323667] 9f00: da841930 d9109780 0000ae80 00000000 d9138000
c053ae64 fffffffa 00000219
[   14.331868] 9f20: 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000001
[   14.340070] 9f40: 00000000 00000081 004957a8 00000001 d9138000
00000000 b5ff3c6c c04bd6dc
[   14.348272] 9f60: 00000001 00000000 ffffffff d9109781 0000000b
d9109780 0000ae80 00000000
[   14.356474] 9f80: d9138000 00000000 0089d188 c053b5e0 0089fb28
00922388 00000000 00000036
[   14.364676] 9fa0: c041a124 c0419f80 0089fb28 00922388 0000000b
0000ae80 00000000 00004270
[   14.372878] 9fc0: 0089fb28 00922388 00000000 00000036 beac7040
0089fb28 b6feb4c0 0089d188
[   14.381081] 9fe0: 0045f098 b5ff3a6c 0004f74b b6b9266c 60070010
0000000b 0946b84a 44f3d1ce
[   14.389293] [<c0ca7a5c>] (_raw_spin_lock) from [<c0416a1c>]
(kvm_vgic_flush_hwstate+0x74/0x21c)
[   14.398024] [<c0416a1c>] (kvm_vgic_flush_hwstate) from [<c040f610>]
(kvm_arch_vcpu_ioctl_run+0x130/0x460)
[   14.407627] [<c040f610>] (kvm_arch_vcpu_ioctl_run) from [<c040acc8>]
(kvm_vcpu_ioctl+0x2e0/0x6d4)
[   14.416535] [<c040acc8>] (kvm_vcpu_ioctl) from [<c053ae64>]
(do_vfs_ioctl+0x9c/0x7e4)
[   14.424394] [<c053ae64>] (do_vfs_ioctl) from [<c053b5e0>]
(SyS_ioctl+0x34/0x5c)
[   14.431731] [<c053b5e0>] (SyS_ioctl) from [<c0419f80>]
(ret_fast_syscall+0x0/0x34)
[   14.439327] Code: f1080080 eafffff0 00000000 f590f000 (e1903f9f)
[   14.445543] ---[ end trace 541ebb092b7d1375 ]---

--
Stefan

^ permalink raw reply	[flat|nested] 45+ messages in thread

* Re: KVM on ARM crashes with new VGIC v4.7-rc7
  2016-07-25 16:52                     ` Stefan Agner
@ 2016-07-25 17:06                       ` Marc Zyngier
  0 siblings, 0 replies; 45+ messages in thread
From: Marc Zyngier @ 2016-07-25 17:06 UTC (permalink / raw)
  To: Stefan Agner; +Cc: Andre Przywara, kvmarm

On 25/07/16 17:52, Stefan Agner wrote:
> On 2016-07-25 01:11, Marc Zyngier wrote:
>> On 25/07/16 07:14, Stefan Agner wrote:
>>> On 2016-07-24 05:36, Marc Zyngier wrote:
>>>> On Sun, 24 Jul 2016 13:22:55 +0100
>>>> Marc Zyngier <marc.zyngier@arm.com> wrote:
>>>>
>>>>> On Fri, 22 Jul 2016 10:56:44 -0700
>>>>> Stefan Agner <stefan@agner.ch> wrote:
>>>>>
>>>>>> On 2016-07-22 10:49, Marc Zyngier wrote:
>>>>>>> On 22/07/16 18:38, Andrew Jones wrote:
>>>>>>>> On Fri, Jul 22, 2016 at 04:40:15PM +0100, Marc Zyngier wrote:
>>>>>>>>> On 22/07/16 15:35, Andrew Jones wrote:
>>>>>>>>>> On Fri, Jul 22, 2016 at 11:42:02AM +0100, Andre Przywara wrote:
>>>>>>>>>>> Hi Stefan,
>>>>>>>>>>>
>>>>>>>>>>> On 22/07/16 06:57, Stefan Agner wrote:
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I tried KVM on a Cortex-A7 platform (i.MX 7Dual SoC) and encountered
>>>>>>>>>>>> this stack trace immediately after invoking qemu-system-arm:
>>>>>>>>>>>>
>>>>>>>>>>>> Unable to handle kernel paging request at virtual address ffffffe4
>>>>>>>>>>>> pgd = 8ca52740
>>>>>>>>>>>> [ffffffe4] *pgd=80000080007003, *pmd=8ff7e003, *pte=00000000
>>>>>>>>>>>> Internal error: Oops: 207 [#1] SMP ARM
>>>>>>>>>>>> Modules linked in:
>>>>>>>>>>>> CPU: 0 PID: 329 Comm: qemu-system-arm Tainted: G        W
>>>>>>>>>>>> 4.7.0-rc7-00094-gea3ed2c #109
>>>>>>>>>>>> Hardware name: Freescale i.MX7 Dual (Device Tree)
>>>>>>>>>>>> task: 8ca3ee40 ti: 8d2b0000 task.ti: 8d2b0000
>>>>>>>>>>>> PC is at do_raw_spin_lock+0x8/0x1dc
>>>>>>>>>>>> LR is at kvm_vgic_flush_hwstate+0x8c/0x224
>>>>>>>>>>>> pc : [<8027c87c>]    lr : [<802172d4>]    psr: 60070013
>>>>>>>>>>>> sp : 8d2b1e38  ip : 8d2b0000  fp : 00000001
>>>>>>>>>>>> r10: 8d2b0000  r9 : 00010000  r8 : 8d2b8e54
>>>>>>>>>>>> fec 30be0000.ethernet eth0: MDIO read timeout
>>>>>>>>>>>> r7 : 8d2b8000  r6 : 8d2b8e74  r5 : 00000000  r4 : ffffffe0
>>>>>>>>>>>> r3 : 00004ead  r2 : 00000000  r1 : 00000000  r0 : ffffffe0
>>>>>>>>>>>> Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
>>>>>>>>>>>> Control: 30c5387d  Table: 8ca52740  DAC: fffffffd
>>>>>>>>>>>> Process qemu-system-arm (pid: 329, stack limit = 0x8d2b0210)
>>>>>>>>>>>> Stack: (0x8d2b1e38 to 0x8d2b2000)
>>>>>>>>>>>> 1e20:                                                       ffffffe0
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1e40: 8d2b8e74 8d2b8000 8d2b8e54 00010000 8d2b0000 802172d4 8d2b8000
>>>>>>>>>>>> 810074f8
>>>>>>>>>>>> 1e60: 81007508 8ca5f800 8d284000 00010000 8d2b0000 8020fbd4 8ce9a000
>>>>>>>>>>>> 8ca5f800
>>>>>>>>>>>> 1e80: 00000000 00010000 00000000 00ff0000 8d284000 00000000 00000000
>>>>>>>>>>>> 7ffbfeff
>>>>>>>>>>>> 1ea0: fffffffe 00000000 8d28b780 00000000 755fec6c 00000000 00000000
>>>>>>>>>>>> ffffe000
>>>>>>>>>>>> 1ec0: 8d2b8000 00000000 8d28b780 00000000 755fec6c 8020af90 00000000
>>>>>>>>>>>> 8023f248
>>>>>>>>>>>> 1ee0: 0000000a 755fe98c 8d2b1f08 00000008 8021aa84 ffffe000 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f00: 8a00d860 8d28b780 80334f94 00000000 8d2b0000 80334748 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f20: 00000000 8d28b780 00004000 00000009 8d28b500 00000024 8104ebee
>>>>>>>>>>>> 80bc2ec4
>>>>>>>>>>>> 1f40: 80bafa24 8034138c 00000000 00000000 80341248 00000000 755fec6c
>>>>>>>>>>>> 007c1e70
>>>>>>>>>>>> 1f60: 00000009 00004258 0000ae80 8d28b781 00000009 8d28b780 0000ae80
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> 1f80: 8d2b0000 00000000 755fec6c 80334f94 007c1e70 322a7400 00004258
>>>>>>>>>>>> 00000036
>>>>>>>>>>>> 1fa0: 8021aa84 8021a900 007c1e70 322a7400 00000009 0000ae80 00000000
>>>>>>>>>>>> 755feac0
>>>>>>>>>>>> 1fc0: 007c1e70 322a7400 00004258 00000036 7e9aff58 01151da4 76f8b4c0
>>>>>>>>>>>> 755fec6c
>>>>>>>>>>>> 1fe0: 0038192c 755fea9c 00048ae7 7697d66c 60070010 00000009 00000000
>>>>>>>>>>>> 00000000
>>>>>>>>>>>> [<8027c87c>] (do_raw_spin_lock) from [<802172d4>]
>>>>>>>>>>>> (kvm_vgic_flush_hwstate+0x8c/0x224)
>>>>>>>>>>>> [<802172d4>] (kvm_vgic_flush_hwstate) from [<8020fbd4>]
>>>>>>>>>>>> (kvm_arch_vcpu_ioctl_run+0x110/0x478)
>>>>>>>>>>>> [<8020fbd4>] (kvm_arch_vcpu_ioctl_run) from [<8020af90>]
>>>>>>>>>>>> (kvm_vcpu_ioctl+0x2e0/0x6d4)
>>>>>>>>>>>> [<8020af90>] (kvm_vcpu_ioctl) from [<80334748>]
>>>>>>>>>>>> (do_vfs_ioctl+0xa0/0x8b8)
>>>>>>>>>>>> [<80334748>] (do_vfs_ioctl) from [<80334f94>] (SyS_ioctl+0x34/0x5c)
>>>>>>>>>>>> [<80334f94>] (SyS_ioctl) from [<8021a900>] (ret_fast_syscall+0x0/0x1c)
>>>>>>>>>>>> Code: e49de004 ea09ea24 e92d47f0 e3043ead (e5902004)
>>>>>>>>>>>> ---[ end trace cb88537fdc8fa206 ]---
>>>>>>>>>>>>
>>>>>>>>>>>> I use CONFIG_KVM_NEW_VGIC=y. This happens to me with a rather minimal
>>>>>>>>>>>> qemu invocation (qemu-system-arm -enable-kvm -M virt -cpu host
>>>>>>>>>>>> -nographic -serial stdio -kernel zImage).
>>>>>>>>>>>>
>>>>>>>>>>>> Using a bit older Qemu version 2.4.0.
>>>>>>>>>>>
>>>>>>>>>>> I just tried with a self compiled QEMU 2.4.0 and the Ubuntu 14.04
>>>>>>>>>>> provided 2.0.0, it worked fine with Linus' current HEAD as a host kernel
>>>>>>>>>>> on a Midway (Cortex-A15).
>>>>>>>>>>
>>>>>>>>>> I can reproduce the issue with a latest QEMU build on AMD Seattle
>>>>>>>>>> (I haven't tried anywhere else yet)
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Can you try to disable the new VGIC, just to see if that's a regression?
>>>>>>>>>>
>>>>>>>>>> Disabling NEW_VGIC "fixes" guest boots.
>>>>>>>>>>
>>>>>>>>>> I'm not using defconfig for my host kernel. I'll do a couple more
>>>>>>>>>> tests and provide a comparison of my config vs. a defconfig in
>>>>>>>>>> a few minutes.
>>>>>>>>>
>>>>>>>>> Damn. It is not failing for me, so it has to be a kernel config thing...
>>>>>>>>> If you can narrow it down to the difference with defconfig, that'd be
>>>>>>>>> tremendously helpful.
>>>>>>>>
>>>>>>>> It's PAGE_SIZE; 64K doesn't work, 4K does, regardless of VA_BITS
>>>>>>>> selection.
>>>>>>>
>>>>>>> That definitely doesn't match Stefan's report (32bit only has 4k). I'll
>>>>>>
>>>>>> Hehe, was just plowing through code and came to that conclusion, glad I
>>>>>> got that right :-)
>>>>>>
>>>>>> What defconfig do you use? I could reproduce the issue also with
>>>>>> multi_v7_defconfig + ARM_LPAE + KVM.
>>>>>
>>>>> I'm now on -rc7 with multi_v7_defconfig + LPAE + KVM (and everything
>>>>> built-in to make my life simpler). The host works perfectly, and I can
>>>>> spawn VMs without any issue.
>>>>>
>>>>> I've tested with QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5exp)
>>>>> as packaged with Jessie from a while ago. I've also upgraded the box to
>>>>> something more recent (2.5), same effect.
>>>>>
>>>>>>
>>>>>> Btw, I am not exactly on vanilla 4.7-rc7, I merged Shawns for-next +
>>>>>> clock next to get to the bits and pieces required for my board...
>>>>>>
>>>>>> That said, it works fine otherwise, and the stacktrace looks rather
>>>>>> platform independent...
>>>>>
>>>>> Indeed, and if these clocks were doing anything unsavoury, we'd
>>>>> probably see other things exploding. So we need to find out where we
>>>>> are diverging.
>>>>>
>>>>> What compiler are you using? I just noticed that my build
>>>>> infrastructure is a bit outdated for 32bit ARM (gcc 4.9.2), so I'm
>>>>> going to upgrade that to gcc 5.3 and retest.
>>>>
>>>> Same thing. The damn thing stubbornly works.
>>>>
>>>> Please send your full configuration, compiler version, exact QEMU
>>>> command line, and any other detail that could be vaguely relevant. As
>>>> the old VGIC gets removed in 4.8, we definitely need to nail that
>>>> sucker right now.
>>>
>>> I built the kernel with
>>> gcc-linaro-5.2-2015.11-2-x86_64_arm-linux-gnueabihf the binaries built
>>> by Linaro (full config attached). For the Rootfs (and Qemu) I did use
>>> the same compiler version, but built using OpenEmbedded.
>>>
>>> Running on a Colibri module using NXP i.MX 7Dual SoC, I haven't used it
>>> that much on mainline but it seems to be rather stable so far.
>>>
>>> I can reproduce the issue with a minimal command such as this:
>>> qemu-system-arm -enable-kvm -M virt -cpu host
>>>
>>> [  179.430694] Unable to handle kernel paging request at virtual address
>>> fffffffc
>>> What is puzzling me a bit that the address the kernel tries to access is
>>> constantly 0xfffffffc. This would be -4, which would be -EINTR? A
>>> unhandled error return?
>>
>> Your initial report had 0xffffffe4 instead. Which looks a bit like a
>> "container_of" operation on a NULL pointer. Do you always get the same
>> backtrace? If so, any chance you could run a
>>
> 
> For completeness here, after changing to the multi_v7_defconfig, the
> stacktrace changed slightly. This is the stack trace using
> multi_v7_defconfig + LPAE + KVM.

For the record, and posterity:

Stefan's issue turned out to be a broken DT, which KVM fails to
gracefully handle, leaving the system pretty broken. Andrew's issue is
fairly similar (GIC setup incompatible with the page size), and the same
KVM issue hits.

I'm working on a fix.

Thanks all of you for all the traces and tests.

	M.
-- 
Jazz is not dead. It just smells funny...

^ permalink raw reply	[flat|nested] 45+ messages in thread

end of thread, other threads:[~2016-07-25 16:59 UTC | newest]

Thread overview: 45+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-22  5:57 KVM on ARM crashes with new VGIC v4.7-rc7 Stefan Agner
2016-07-22  7:47 ` Marc Zyngier
2016-07-22  7:52   ` Auger Eric
2016-07-22  7:59     ` Marc Zyngier
2016-07-22  8:10   ` Stefan Agner
2016-07-22  9:15 ` Marc Zyngier
2016-07-22 10:42 ` Andre Przywara
2016-07-22 14:35   ` Andrew Jones
2016-07-22 15:40     ` Marc Zyngier
2016-07-22 15:42       ` Auger Eric
2016-07-22 17:38       ` Andrew Jones
2016-07-22 17:47         ` Stefan Agner
2016-07-22 17:49         ` Marc Zyngier
2016-07-22 17:56           ` Stefan Agner
2016-07-22 18:11             ` Marc Zyngier
2016-07-23  7:45               ` Stefan Agner
2016-07-23 10:20                 ` Marc Zyngier
2016-07-23 16:33                   ` Stefan Agner
2016-07-24  9:30                     ` Marc Zyngier
2016-07-25  6:28                       ` Stefan Agner
2016-07-24 12:22             ` Marc Zyngier
2016-07-24 12:36               ` Marc Zyngier
2016-07-25  6:14                 ` Stefan Agner
2016-07-25  8:11                   ` Marc Zyngier
2016-07-25  8:17                     ` Marc Zyngier
2016-07-25 13:50                       ` Andre Przywara
2016-07-25 14:05                         ` Marc Zyngier
2016-07-25 14:28                           ` Andrew Jones
2016-07-25 14:39                             ` Marc Zyngier
2016-07-25 15:07                             ` Marc Zyngier
2016-07-25 15:25                               ` Andre Przywara
2016-07-25 15:29                               ` Andrew Jones
2016-07-25 15:38                                 ` Marc Zyngier
2016-07-25 16:52                     ` Stefan Agner
2016-07-25 17:06                       ` Marc Zyngier
2016-07-25  8:42                   ` Marc Zyngier
2016-07-25  6:36                 ` Stefan Agner
2016-07-25 13:33                   ` Andre Przywara
2016-07-25 16:18                     ` Stefan Agner
2016-07-22 18:06         ` Marc Zyngier
2016-07-22 19:45           ` Andrew Jones
2016-07-22 19:54             ` Marc Zyngier
2016-07-25  9:00               ` Andrew Jones
2016-07-25  9:05                 ` Marc Zyngier
2016-07-25  9:18                   ` Andrew Jones

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.