summaryrefslogtreecommitdiff
path: root/dissector_80211.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-06-17 23:12:18 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-06-17 23:12:18 +0200
commit2652683811a8dd4e057f92fe669a285c7e2e7c60 (patch)
tree0cc3fabf1b124d79d6871631b379a9a13809f39a /dissector_80211.c
parentc3c2cb8d011f1c3e28b22584ea11fa544402c89b (diff)
dissector: explicitly init array
Use explicit form to initialize array. Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'dissector_80211.c')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-07-04 23:24:37 +0000
88e957d6e47f ("xen: introduce xen_vcpu_id mapping") broke SMP ARM guests on Xen. When FIFO-based event channels are in use (this is the default), evtchn_fifo_alloc_control_block() is called on CPU_UP_PREPARE event and this happens before we set up xen_vcpu_id mapping in xen_starting_cpu. Temporary fix the issue by setting direct Linux CPU id <-> Xen vCPU id mapping for all possible CPUs at boot. We don't currently support kexec/kdump on Xen/ARM so these ids always match. In future, we have several ways to solve the issue, e.g.: - Eliminate all hypercalls from CPU_UP_PREPARE, do them from the starting CPU. This can probably be done for both x86 and ARM and, if done, will allow us to get Xen's idea of vCPU id from CPUID/MPIDR on the starting CPU directly, no messing with ACPI/device tree required. - Save vCPU id information from ACPI/device tree on ARM and use it to initialize xen_vcpu_id mapping. This is the same trick we currently do on x86. Reported-by: Julien Grall <julien.grall@arm.com> Tested-by: Wei Chen <Wei.Chen@arm.com> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com> Acked-by: Stefano Stabellini <sstabellini@kernel.org> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'Documentation/i2c/fault-codes')