Re: DEBUG_LOCKS_WARN_ON(!current->hardirqs_enabled)

On 11/7/15, Li RongQing wrote: > Does Anyone see this calltrace? I see it from 3.19 to 4.3, did not > test it on other older release. http://www.gossamer-threads.com/lists/linux/kernel/2297694 > > > EXT4-fs (hda): recovery complete > EXT4-fs (hda): mounted filesystem

Re: [PATCH] powerpc: allow cross-compilation of ppc64 kernel

Le 07/11/2015 00:12, Benjamin Herrenschmidt a écrit : > On Fri, 2015-11-06 at 15:09 -0600, Scott Wood wrote: >> On Thu, 2015-11-05 at 12:47 +0100, Laurent Vivier wrote: >>> When I try to cross compile a ppc64 kernel, it generally >>> fails on the VDSO stage. This is true for powerpc64 cross- >>>

Re: [PATCH] powerpc: allow cross-compilation of ppc64 kernel

Le 07/11/2015 00:32, Segher Boessenkool a écrit : > On Fri, Nov 06, 2015 at 04:55:49PM -0600, Segher Boessenkool wrote: >> On Fri, Nov 06, 2015 at 03:09:40PM -0600, Scott Wood wrote: >>> Why is GCC building ppc64 object files but telling the linker --oformat >>> elf32- >>> powerpcle? Are

[PATCH V13 4/9] powerpc/eeh: Cache only BARs, not windows or IOV BARs

This restricts the EEH address cache to use only the first 7 BARs. This makes __eeh_addr_cache_insert_dev() ignore PCI bridge window and IOV BARs. As the result of this change, eeh_addr_cache_get_dev() will return VFs from VF's resource addresses instead of parent PFs. This removes extra check

[PATCH V13 5/9] powerpc/powernv: EEH device for VF

VFs and their corresponding pci_dn instances are created and released dynamically as their PF's SRIOV capability is enabled and disabled. The patch creates and releases EEH devices for VFs when creating and releasing their pci_dn instances, which means EEH devices and pci_dn instances have same

[PATCH V13 8/9] powerpc/powernv: Support PCI config restore for VFs

After PE reset, OPAL API opal_pci_reinit() is called on all devices contained in the PE to reinitialize them. While skiboot is not aware of VFs, we have to implement the function in kernel to reinitialize VFs after reset on PE for VFs. In this patch, two functions pnv_pci_fixup_vf_mps() and

[PATCH V13 9/9] powerpc/eeh: Support error recovery for VF PE

PFs are enumerated on PCI bus, while VFs are created by PF's driver. In EEH recovery, it has two cases: 1. Device and driver is EEH aware, error handlers are called. 2. Device and driver is not EEH aware, un-plug the device and plug it again by enumerating it. The special thing happens on the

[PATCH V13 3/9] powerpc/pci: Remove VFs prior to PF

As commit ac205b7bb72f ("PCI: make sriov work with hotplug remove") indicates, VFs which is on the same PCI bus as their PF, should be removed before the PF. Otherwise, the PCI hot unplugging of PCI devices on the PCI bus would cause kernel crash. The patch applies the above pattern to PowerPC

[PATCH V13 7/9] powerpc/powernv: Support EEH reset for VF PE

PEs for VFs don't have primary bus. So they have to have their own reset backend, which is used during EEH recovery. The patch implements the reset backend for VF's PE by issuing FLR or AF FLR to the VFs, which are contained in the PE. Signed-off-by: Wei Yang ---

[PATCH V13 2/9] PCI: Add pcibios_bus_add_device() weak function

Add a weak function pcibios_bus_add_device() for arch dependent code could do proper setup. For example, powerpc could setup EEH related resources. Signed-off-by: Wei Yang Acked-by: Bjorn Helgaas --- drivers/pci/bus.c | 3 +++ 1 file changed, 3

[PATCH V13 1/9] PCI/IOV: Rename and export virtfn_add/virtfn_remove

During EEH recovery, hotplug is applied to the devices which don't have drivers or their drivers don't support EEH. However, the hotplug, which was implemented based on PCI bus, can't be applied to VF directly. Rename virtn_{add,remove}() and export them so they can be used in PCI hotplug during

[PATCH V13 0/9] VF EEH on Power8

This patchset enables EEH on SRIOV VFs. The general idea is to create proper VF edev and VF PE and handle them properly. Different from the Bus PE, VF PE just contain one VF. This introduces the difference of EEH error handling on a VF PE. Generally, it has several differences. First, the VF's

[PATCH V13 6/9] powerpc/eeh: Create PE for VFs

The patch creates PEs for VFs in the weak function pcibios_bus_add_device(). Those PEs for VFs are identified with newly introduced flag EEH_PE_VF so that we handle them differently during EEH recovery. Signed-off-by: Wei Yang --- arch/powerpc/include/asm/eeh.h

Re: [PATCH v2 00/20] Fix handling of compat_siginfo_t

On Wed, Nov 4, 2015 at 4:50 PM, Amanieu d'Antras wrote: > One issue that isn't resolved in this series is sending signals between a > 32-bit > process and 64-bit process. Sending a si_int will work correctly, but a si_ptr > value will likely get corrupted due to the different

Re: DEBUG_LOCKS_WARN_ON(!current->hardirqs_enabled)

On Sat, Nov 7, 2015 at 9:01 PM, Denis Kirjanov wrote: >> Does Anyone see this calltrace? I see it from 3.19 to 4.3, did not >> test it on other older release. > > http://www.gossamer-threads.com/lists/linux/kernel/2297694 I see this calltrace on 3.19, so it should not