Re: [PATCH v1 1/3] powerpc/kernel: Split up pci_bus_add_device

Hi Bryant, [auto build test WARNING on powerpc/next] [also build test WARNING on v4.14-rc1 next-20170919] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Bryant-G-Ly/Prepartion-for-SR-IOV

Re: [PATCH] KVM: KVM_MAX_IRQ_ROUTES only defined with CONFIG_HAVE_KVM_IRQ_ROUTING

Apologies, just noticed 95e2a3b3ef177730019e3799917193595133b275 being the revert of 36ae3c0a36b7 On 20/09/17 11:31, Daniel Black wrote: > Commit 36ae3c0a36b7 introduced code using KVM_MAX_IRQ_ROUTES. This > define isn't available on all platforms. As it is dependent on >

Re: [PATCH] powerpc/eeh: Disable EEH stack dump by default

Jose Ricardo Ziviani writes: > Today, each EEH causes a stack dump to be printed in the logs. In > production environment it's not quite necessary. Thus, this patch I'm unconvinced. A production environment is exactly where you don't want to be getting an EEH, and so

Re: Traceback due to 'powerpc/mm: Fix kernel RAM protection...' when running ppc image in qemu

On 09/19/2017 08:05 PM, Michael Ellerman wrote: Guenter Roeck writes: Hi, I see a the following traceback when running an SMP image based on 85xx/mpc85xx_cds_defconfig in qemu. [ cut here ] WARNING: CPU: 0 PID: 1 at kernel/smp.c:416

Re: [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

On 09/17/2017 08:51 AM, Henrique de Moraes Holschuh wrote: > On Sat, 16 Sep 2017, Rob Landley wrote: >> So, I added a workaround with a printk in hopes of embarassing them into >> someday fixing it. > > Oh, it will be fixed in Debian alright. Cool! But part of the problem is people upgrade the

Re: Traceback due to 'powerpc/mm: Fix kernel RAM protection...' when running ppc image in qemu

Guenter Roeck writes: > Hi, > > I see a the following traceback when running an SMP image based on > 85xx/mpc85xx_cds_defconfig in qemu. > > [ cut here ] > WARNING: CPU: 0 PID: 1 at kernel/smp.c:416 smp_call_function_many+0xcc/0x2fc > CPU: 0 PID: 1

Re: [PATCH 3/5] powerpc64: Add .opd based function descriptor dereference

Sergey Senozhatsky writes: > On (09/19/17 20:22), Michael Ellerman wrote: >> > On 2017/09/16 12:53PM, Sergey Senozhatsky wrote: >> >> We are moving towards separate kernel and module function descriptor >> >> dereference callbacks. This patch enables it for

[PATCH] KVM: KVM_MAX_IRQ_ROUTES only defined with CONFIG_HAVE_KVM_IRQ_ROUTING

Commit 36ae3c0a36b7 introduced code using KVM_MAX_IRQ_ROUTES. This define isn't available on all platforms. As it is dependent on CONFIG_HAVE_KVM_IRQ_ROUTING this define is used to enable the code in 36ae3c0a36b7. Fixes: 36ae3c0a36b7 ("KVM: Don't accept obviously wrong gsi values via KVM_IRQFD")

Re: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

On (09/19/17 22:03), Helge Deller wrote: [..] > Your implementation of dereference_module_function_descriptor() in > arch/parisc/kernel/module.c is faulty. > mod->arch.fdesc_offset is relative to the base address of the module, > so you need to add to mod->core_layout.base. aha, got it. I should

[PATCH] powerpc/sstep: mullw should calculate a 64 bit signed result

From: Anton Blanchard mullw should do a 32 bit signed multiply and create a 64 bit signed result. It currently truncates the result to 32 bits. Signed-off-by: Anton Blanchard --- arch/powerpc/lib/sstep.c | 5 +++-- 1 file changed, 3 insertions(+), 2

Re: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

On 19.09.2017 15:38, David Laight wrote: From: Sergey Senozhatsky Sent: 19 September 2017 03:06 ... I'll simply convert everything to `unsigned long'. including the dereference_function_descriptor() function [I believe there are still some casts happening when we pass addr from kernel/module

Re: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

* Helge Deller : > On 19.09.2017 04:05, Sergey Senozhatsky wrote: > >On (09/18/17 20:39), Helge Deller wrote: > >>I did tried your testcases [on parisc] too. > ... > >>and here is "modprobe zram": > >> printk#7 __UNIQUE_ID_vermagic8+0xb9a4/0xbd04 [zram] > >> printk#8

Traceback due to 'powerpc/mm: Fix kernel RAM protection...' when running ppc image in qemu

Hi, I see a the following traceback when running an SMP image based on 85xx/mpc85xx_cds_defconfig in qemu. [ cut here ] WARNING: CPU: 0 PID: 1 at kernel/smp.c:416 smp_call_function_many+0xcc/0x2fc CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0-rc1-9-g0666f56 #1

Re: [PATCH] drivers: of: static DT reservations incorrectly added to dynamic list

On Thu, Sep 14, 2017 at 5:24 AM, Stewart Smith wrote: > There are two types of memory reservations firmware can ask the kernel > to make in the device tree: static and dynamic. > See Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt > > If you have

Re: [PATCH] powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline

Hi Michael, Any comments on this patch ? On 09/06/2017 02:32 PM, pavrampu wrote: On 2017-08-31 17:17, Gautham R. Shenoy wrote: > From: "Gautham R. Shenoy" > > commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via > stop-api only on Hotplug") clears the PECE1

[PATCH] powerpc/eeh: Disable EEH stack dump by default

Today, each EEH causes a stack dump to be printed in the logs. In production environment it's not quite necessary. Thus, this patch adds a new command line argument in order to enable the stack dump for debugging purposes. For example, instead of the following: [ 131.778661] EEH: Frozen

Re: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

On 19.09.2017 04:05, Sergey Senozhatsky wrote: On (09/18/17 20:39), Helge Deller wrote: I did tried your testcases [on parisc] too. ... and here is "modprobe zram": printk#7 __UNIQUE_ID_vermagic8+0xb9a4/0xbd04 [zram] printk#8 __UNIQUE_ID_vermagic8+0xb9a4/0xbd04 [zram] printk#9

Applied "ASoC: fsl_ssi: Caculate bit clock rate using slot number and width" to the asoc tree

The patch ASoC: fsl_ssi: Caculate bit clock rate using slot number and width has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: fsl-asoc-card: Don't error out if ENOTSUPP" to the asoc tree

The patch ASoC: fsl-asoc-card: Don't error out if ENOTSUPP has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

RE: [PATCH 0/5] [RFC] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers

From: Sergey Senozhatsky > Sent: 19 September 2017 03:06 ... > I'll simply convert everything to `unsigned long'. including the > dereference_function_descriptor() function [I believe there are > still some casts happening when we pass addr from kernel/module > dereference functions to

Re: [mainline][DLPAR][Oops] OF: ERROR: Bad of_node_put() on /cpus

On Fri, 2017-09-15 at 07:52 -0500, Rob Herring wrote: > On Fri, Sep 15, 2017 at 6:04 AM, abdul wrote: > > Hi, > > > > Mainline kernel panics during DLPAR CPU add/remove operation. > > > > Machine Type: Power8 PowerVM LPAR > > kernel 4.13.0 > > Did 4.12 work or when

Re: [linux-next][DLPAR CPU][Oops] Bad kernel stack pointer

On Mon, 2017-09-18 at 07:44 -0500, Rob Herring wrote: > On Mon, Sep 18, 2017 at 5:08 AM, Abdul Haleem > wrote: > > Hi, > > > > Dynamic CPU remove operation resulted in Kernel Panic on today's > > next-20170915 kernel. > > > > Machine Type: Power 7 PowerVM LPAR > >

[PATCH 6/6] crypto: talitos - fix memory corruption on SEC2

On SEC2, when using the old descriptors type (hmac snoop no afeu) for doing IPsec, the CICV out pointeur points out of the allocated memory. [2.502554] = [2.510740] BUG dma-kmalloc-256 (Not tainted): Redzone

[PATCH 5/6] crypto: talitos - use kzalloc instead of kmalloc

Use kzalloc() to zeroize the extended descriptor at allocation and further zeorising Signed-off-by: Christophe Leroy --- drivers/crypto/talitos.c | 23 +-- drivers/crypto/talitos.h | 2 -- 2 files changed, 1 insertion(+), 24 deletions(-) diff --git

[PATCH 4/6] crypto: talitos - fix AEAD test failures

AEAD tests fail when destination SG list has more than 1 element. [2.058752] alg: aead: Test 1 failed on encryption for authenc-hmac-sha1-cbc-aes-talitos [2.066965] : 53 69 6e 67 6c 65 20 62 6c 6f 63 6b 20 6d 73 67 0010: c0 43 ff 74 c0 43 ff e0 de 83 d1 20 de 84 8e 54

[PATCH 3/6] crypto: talitos - fix sha224

Kernel crypto tests report the following error at startup [2.752626] alg: hash: Test 4 failed for sha224-talitos [2.757907] : 30 e2 86 e2 e7 8a dd 0d d7 eb 9f d5 83 fe f1 b0 0010: 2d 5a 6c a5 f9 55 ea fd 0e 72 05 22 This patch fixes it Signed-off-by: Christophe Leroy

[PATCH 2/6] crypto: talitos - fix hashing

md5sum on some files gives wrong result Exemple: With the md5sum from libkcapi: c15115c05bad51113f81bdaee735dd09 test With the original md5sum: bbdf41d80ba7e8b2b7be3a0772be76cb test This patch fixes this issue Signed-off-by: Christophe Leroy ---

[PATCH 1/6] crypto: talitos - Don't provide setkey for non hmac hashing algs.

Today, md5sum fails with error -ENOKEY because a setkey function is set for non hmac hashing algs, see strace output below: mmap(NULL, 378880, PROT_READ, MAP_SHARED, 6, 0) = 0x77f5 accept(3, 0, NULL) = 7 vmsplice(5,

[PATCH 0/6] crypto: talitos - various fixes

This serie provide various fixes on the talitos driver. Christophe Leroy (6): crypto: talitos - Don't provide setkey for non hmac hashing algs. crypto: talitos - fix hashing crypto: talitos - fix sha224 crypto: talitos - fix AEAD test failures crypto: talitos - use kzalloc instead of

Re: [PATCH v1 0/3] powerpc: memcmp() optimization

Hi Could you in the email/patch subject and in the commit texts write powerpc/64 instead of powerpc as it doesn't apply to powerpc/32 Christophe Le 19/09/2017 à 12:03, wei.guo.si...@gmail.com a écrit : From: Simon Guo There is some room to optimize memcmp() in

Re: [PATCH v1 1/3] powerpc: Align bytes before fall back to .Lshort in powerpc memcmp

Hi Could you in the email/patch subject write powerpc/64 instead pof powerpc as it doesn't apply to powerpc/32 Le 19/09/2017 à 12:03, wei.guo.si...@gmail.com a écrit : From: Simon Guo Currently memcmp() in powerpc will fall back to .Lshort (compare per byte Say

[PATCH 2/2] powerpc/sstep: Fix issues with mcrf

From: Anton Blanchard mcrf broke when we changed analyse_instr() to not modify the register state. The instruction writes to the CR, so we need to store the result in op->ccval, not op->val. Fixes: 3cdfcbfd32b9 ("powerpc: Change analyse_instr so it doesn't modify *regs")

[PATCH 1/2] powerpc/sstep: Fix issues with set_cr0()

From: Anton Blanchard set_cr0() broke when we changed analyse_instr() to not modify the register state. Instead of looking at regs->gpr[x] which has not been updated yet, we need to look at op->val. Fixes: 3cdfcbfd32b9 ("powerpc: Change analyse_instr so it doesn't modify

Re: linux-4.14-rc1/arch/powerpc/perf/hv-24x7.c:541: bad condition ?

David Binderman writes: > Hello there, > > linux-4.14-rc1/arch/powerpc/perf/hv-24x7.c:543]: (warning) Identical > condition 's1 > Source code is > > if (s1 < s2) > return 1; > if (s2 > s1) > return -1; > >

Re: [PATCH 3/5] powerpc64: Add .opd based function descriptor dereference

On (09/19/17 20:22), Michael Ellerman wrote: > > On 2017/09/16 12:53PM, Sergey Senozhatsky wrote: > >> We are moving towards separate kernel and module function descriptor > >> dereference callbacks. This patch enables it for powerpc64. > >> > >> For pointers that belong to the kernel > >> -

Re: [PATCH 3/5] powerpc64: Add .opd based function descriptor dereference

"Naveen N. Rao" writes: > On 2017/09/16 12:53PM, Sergey Senozhatsky wrote: >> We are moving towards separate kernel and module function descriptor >> dereference callbacks. This patch enables it for powerpc64. >> >> For pointers that belong to the kernel >> -

Re: [PATCH 2/2] powerpc: Handle MCE on POWER9 with only DSISR bit 33 set

On Fri, Sep 15, 2017 at 3:25 PM, Michael Neuling wrote: > On POWER9 DD2.1 and below, it's possible to get Machine Check > Exception (MCE) where only DSISR bit 33 is set. This will result in > the linux MCE handler seeing an unknown event, which triggers linux to > crash. > > We

RE: [PATCH v1 1/3] powerpc: Align bytes before fall back to .Lshort in powerpc memcmp

From: wei.guo.si...@gmail.com > Sent: 19 September 2017 11:04 > Currently memcmp() in powerpc will fall back to .Lshort (compare per byte > mode) if either src or dst address is not 8 bytes aligned. It can be > opmitized if both addresses are with the same offset with 8 bytes boundary. > >

Re: [PATCH] powerpc/sysrq: Fix oops whem ppmu is not registered

On Tuesday 19 September 2017 03:30 PM, Michael Ellerman wrote: Ravi Bangoria writes: Kernel crashes if power pmu is not registered and user tries to dump regs with 'echo p > /proc/sysrq-trigger'. Sample log: Unable to handle kernel paging request for

[PATCH v1 3/3] powerpc:selftest update memcmp selftest according to kernel change

From: Simon Guo This patch adjust selftest files related with memcmp so that memcmp selftest can be compiled successfully. Signed-off-by: Simon Guo --- .../selftests/powerpc/copyloops/asm/ppc_asm.h | 2 +-

[PATCH v1 2/3] powerpc: enhance memcmp() with VMX instruction for long bytes comparision

From: Simon Guo This patch add VMX primitives to do memcmp() in case the compare size exceeds 4K bytes. Test result with following test program: -- tools/testing/selftests/powerpc/stringloops# cat memcmp.c int test_memcmp(const void *s1, const void *s2, size_t n);

[PATCH v1 1/3] powerpc: Align bytes before fall back to .Lshort in powerpc memcmp

From: Simon Guo Currently memcmp() in powerpc will fall back to .Lshort (compare per byte mode) if either src or dst address is not 8 bytes aligned. It can be opmitized if both addresses are with the same offset with 8 bytes boundary. memcmp() can align the src/dst

[PATCH v1 0/3] powerpc: memcmp() optimization

From: Simon Guo There is some room to optimize memcmp() in powerpc for following 2 cases: (1) Even src/dst addresses are not aligned with 8 bytes at the beginning, memcmp() can align them and go with .Llong comparision mode without fallback to .Lshort comparision mode do

Re: [PATCH] powerpc/sysrq: Fix oops whem ppmu is not registered

Ravi Bangoria writes: > Kernel crashes if power pmu is not registered and user tries to dump > regs with 'echo p > /proc/sysrq-trigger'. Sample log: > > Unable to handle kernel paging request for data at address 0x0008 > Faulting instruction address:

[PATCH 5/5] arm64: dts: ls1046a: add PCIe controller DT nodes

From: Hou Zhiqiang LS1046a implements 3 PCIe 3.0 controllers. Signed-off-by: Hou Zhiqiang --- arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 75 ++ 1 file changed, 75 insertions(+) diff --git

[PATCH 4/5] arm64: dts: ls1012a: Add PCIe controller DT node

From: Hou Zhiqiang Add PCIe controller node for ls1012a platform. Signed-off-by: Hou Zhiqiang --- arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 24 1 file changed, 24 insertions(+) diff --git

[PATCH 3/5] PCI: layerscape: Add support for ls1012a

From: Hou Zhiqiang Signed-off-by: Hou Zhiqiang --- Documentation/devicetree/bindings/pci/layerscape-pci.txt | 1 + drivers/pci/dwc/pci-layerscape.c | 1 + 2 files changed, 2 insertions(+) diff --git

[PATCH 2/5] arm64: dts: ls1012a: Add MSI controller DT node

From: Hou Zhiqiang Add MSI controller node for ls1012a platform. Signed-off-by: Hou Zhiqiang --- arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi

[PATCH 1/5] irqchip/ls-scfg-msi: add LS1012a MSI support

From: Hou Zhiqiang The ls1012a implement only 1 msi controller, and it is the same as ls1043a. Signed-off-by: Hou Zhiqiang --- .../devicetree/bindings/interrupt-controller/fsl,ls-scfg-msi.txt | 1 + drivers/irqchip/irq-ls-scfg-msi.c

[PATCH 0/5] arm64: add ls1012a and ls1046a pcie support

From: Hou Zhiqiang This patch set adds ls1012a MSI and PCIe support, including driver and device tree nodes. The ls1046a's MSI support patch and PCIe driver patch has been applied, so only adds the PCIe device tree nodes. Hou Zhiqiang (5): irqchip/ls-scfg-msi: add

[PATCH] powerpc/sysrq: Fix oops whem ppmu is not registered

Kernel crashes if power pmu is not registered and user tries to dump regs with 'echo p > /proc/sysrq-trigger'. Sample log: Unable to handle kernel paging request for data at address 0x0008 Faulting instruction address: 0xc00d52f0 NIP [c00d52f0]