On Thu, 2017-05-25 at 08:23 +0530, Aneesh Kumar K.V wrote:
> Michael Neuling writes:
>
> > On Wed, 2017-05-24 at 14:26 +0530, Aneesh Kumar K.V wrote:
> > > Michael Neuling writes:
> > >
> > > > Currently if you disable CONFIG_PPC_RADIX_MMU you'll crash on boot on
> > > > a P9. This is because w
Hi Michal,
[auto build test WARNING on powerpc/next]
[also build test WARNING on v4.12-rc2 next-20170525]
[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/Michal-Suchanek/powerpc-fadump-return
- log an error message when registration fails and no error code listed
in the switch is returned
- translate the hv error code to posix error code and return it from
fw_register
- return the posix error code from fw_register to the process writing
to sysfs
- return EEXIST on re-registration
Do the checks that __flush_tlb_pending() does and check if
a local flush will do when batch->active is false inside of
hpte_need_flush(). I've checked the changes with tlbie tracing,
I see local flushes as applicable now and I've also run
some basic ltp testcases on top of these changes on a powern
On Thu, 25 May 2017, Abdul Haleem wrote:
> Hi,
>
> Test : boot
> Machine : Power 8 PowerVM LPAR
> Kernel version : 4.12.0-rc2-next-20170524
> Toolchain : gcc version 5.2.1
> Config : attached
>
> next-20170517 was last good version where we did not see the failure.
> from next-20170519 to today'
Hi Balbir,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.12-rc2 next-20170525]
[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/Balbir-Singh/Enable-STRICT_KERNEL_RWX
On Wed, 2017-05-24 at 21:50 +1000, Michael Ellerman wrote:
> Abdul Haleem writes:
> > Hi Cyril,
> >
> > I see a similar trace, but with 'tm-signal-stack' test for mainline
> > kernel 4.12.0-rc1 on PowerVM LPAR.
>
> I can't reproduce this here.
It is not reproducible all the times.
>
> Can you pl
[ 283.516559] Kernel BUG at c191c160 [verbose debug info unavailable]
[ 283.516573] Unexpected TM Bad Thing exception at c191c160
(msr 0x2a03030)
cpu 0x19: Vector: 700 (Program Check) at [c007d1a37920]
pc: c191c160: fast_exception_return+0xac/0xb4
lr: c
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Monday, May 15, 2017 5:31 PM
> Subject: Re: [PATCH] dt-bindings: net: move FMan binding
>
> From: Madalin Bucur
> Date: Mon, 15 May 2017 16:36:38 +0300
>
> > Besides the PPC SoCs, the QorIQ DPAA FMan is also p
Abdul Haleem writes:
> Hi,
>
> Test : boot
> Machine : Power 8 PowerVM LPAR
> Kernel version : 4.12.0-rc2-next-20170524
> Toolchain : gcc version 5.2.1
> Config : attached
>
> next-20170517 was last good version where we did not see the failure.
> from next-20170519 to today's next-20170524, we s
On Fri, 2017-05-19 at 01:37:45 UTC, Michael Ellerman wrote:
> The tm-resched-dscr test has started failing sometimes, depending on
> what compiler it's built with, eg:
>
> test: tm_resched_dscr
> Check DSCR TM context switch: tm-resched-dscr: tm-resched-dscr.c:76:
> test_body: Assertion `rv'
On Fri, 2017-05-19 at 20:56:35 UTC, Alistair Popple wrote:
> opal_npu_destroy_context() should be called with the NPU PHB, not the
> PCIe PHB.
>
> Signed-off-by: Alistair Popple
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/415ba3c157b9de7edc59468d19d48c
cheers
On Sat, 2017-05-20 at 04:29:49 UTC, Nicholas Piggin wrote:
> Providing "scv" support to userspace requires kernel support, so it
> must be advertised as independently to the base ISA 3 instruction set.
>
> The darn instruction relies on firmware enablement, so it has been
> decided to split this o
On Wed, 2017-05-24 at 06:49:59 UTC, Jeremy Kerr wrote:
> Change ac29c64089b7 swapped _PAGE_USER for _PAGE_PRIVILEGED, and
> introduced check_pte_access() which denied kernel access to
> non-_PAGE_PRIVILEGED pages.
>
> However, it didn't add _PAGE_PRIVILEGED to the hash fault handler for
> spufs' k
On Wed, 2017-05-24 at 07:03:26 UTC, Michael Neuling wrote:
> Currently if you disable CONFIG_PPC_RADIX_MMU you'll crash on boot on
> a P9. This is because we still set MMU_FTR_TYPE_RADIX via
> ibm,pa-features and MMU_FTR_TYPE_RADIX is what's used for code patching
> in much of the asm code (ie. slb
On 05/24/2017 11:56 PM, Matt Brown wrote:
> On Wed, May 24, 2017 at 11:36 PM, Paul Clarke wrote:
>> On 05/23/2017 06:45 PM, Matt Brown wrote:
>>> The xor_vmx.c file is used for the RAID5 xor operations. In these functions
>>> altivec is enabled to run the operation and then disabled. However due t
On 05/25/2017 01:19 AM, Michael Ellerman wrote:
> Michael Bringmann writes:
>
>> On 05/24/2017 06:19 AM, Michael Ellerman wrote:
>>> Michael Bringmann writes:
With or without 3af229f2071f, we would still need to add something,
somewhere to add new
bits to the 'node_possibl
On Mon, May 22, 2017 at 11:11:33PM +0200, Thomas Gleixner wrote:
> On Mon, 15 May 2017, Will Deacon wrote:
> > On Mon, May 15, 2017 at 03:07:42PM +0200, Jiri Slaby wrote:
> > > There is code duplicated over all architecture's headers for
> > > futex_atomic_op_inuser. Namely op decoding, access_ok c
Hello,
I'm working on a real-time application using POSIX timers running on a
QorIQ PowerPC platform with a 4.1 PREEMPT RT kernel and I'm trying to
understand whether the following can happen:
1. A thread with a core affinity #0 creates a timer which will invoke
a callback.
2. The kernel will setu
On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
The commit message for 3af229f2071f says:
In practice, we never see a system with 256 NUMA nodes, and in fact, we
do not support node hotplug on power in the first place, so the nodes
^
On 05/25/2017 10:10 AM, Reza Arbab wrote:
> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
>> The commit message for 3af229f2071f says:
>>
>>In practice, we never see a system with 256 NUMA nodes, and in fact, we
>>do not support node hotplug on power in the first place
Hi Balbir,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.12-rc2 next-20170525]
[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/Balbir-Singh/Enable-STRICT_KERNEL_RWX
powerpc/numa: Correct the currently broken capability to set the
topology for shared CPUs in LPARs. At boot time for shared CPU
lpars, the topology for each shared CPU is set to node zero, however,
this is now updated correctly using the Virtual Processor Home Node
(VPHN) capabilities information
Removing or adding memory via the PowerPC hotplug interface shows
anomalies in the association between memory and nodes. The code
was updated to ensure that all nodes found at boot are still available
to subsequent DLPAR hotplug-memory operations, even if they are not
needed at boot time.
Signed
If the affine portal for a specific CPU is offline at boot time
affine its interrupt to CPU 0. If the CPU is later brought online
the hotplug handler will correctly adjust the affinity.
Signed-off-by: Roy Pledge
---
drivers/soc/fsl/qbman/bman.c | 17 +
drivers/soc/fsl/qbman/qman.
Hi Michael,
On Thu, 25 May 2017 23:02:06 +1000 Michael Ellerman wrote:
>
> It'll be:
>
> ee35011fd032 ("initramfs: make initramfs honor CONFIG_DEVTMPFS_MOUNT")
And Andrew has asked me to drop that patch from linux-next which will
happen today.
--
Cheers,
Stephen Rothwell
On 05/25/2017 10:35 AM, Michael Bringmann wrote:
>
> powerpc/numa: Correct the currently broken capability to set the
> topology for shared CPUs in LPARs. At boot time for shared CPU
> lpars, the topology for each shared CPU is set to node zero, however,
> this is now updated correctly using the
On Thu, 25 May 2017 12:37:40 -0500
Michael Bringmann wrote:
> Removing or adding memory via the PowerPC hotplug interface shows
> anomalies in the association between memory and nodes. The code
> was updated to ensure that all nodes found at boot are still available
> to subsequent DLPAR hotplug
On Thu, 25 May 2017 10:10:11 -0500
Reza Arbab wrote:
> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
> >The commit message for 3af229f2071f says:
> >
> >In practice, we never see a system with 256 NUMA nodes, and in fact, we
> >do not support node hotplug on power in t
Reza Arbab writes:
> On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote:
>>The commit message for 3af229f2071f says:
>>
>>In practice, we never see a system with 256 NUMA nodes, and in fact, we
>>do not support node hotplug on power in the first place, so the nodes
>>^^^
Matt Brown writes:
> On Wed, May 24, 2017 at 11:36 PM, Paul Clarke wrote:
>> On 05/23/2017 06:45 PM, Matt Brown wrote:
>>> The xor_vmx.c file is used for the RAID5 xor operations. In these functions
>>> altivec is enabled to run the operation and then disabled. However due to
>>> compiler instru
Michael Bringmann writes:
> Removing or adding memory via the PowerPC hotplug interface shows
> anomalies in the association between memory and nodes.
What anomalies? Please describe the actual problem you're seeing, with
details, and why you think this is the correct fix.
This is a revert of 3
These are completely obvious as all they do is include the asm-generic
versions.
Signed-off-by: Stephen Rothwell
---
arch/powerpc/include/uapi/asm/Kbuild | 5 +
arch/powerpc/include/uapi/asm/param.h| 1 -
arch/powerpc/include/uapi/asm/poll.h | 1 -
arch/powerpc/include/uapi/asm/r
On 05/25/2017 04:24 PM, Stephen Rothwell wrote:
> Hi Michael,
>
> On Thu, 25 May 2017 23:02:06 +1000 Michael Ellerman
> wrote:
>>
>> It'll be:
>>
>> ee35011fd032 ("initramfs: make initramfs honor CONFIG_DEVTMPFS_MOUNT")
>
> And Andrew has asked me to drop that patch from linux-next which will
>
On Thu, 25 May 2017, Will Deacon wrote:
> On Mon, May 22, 2017 at 11:11:33PM +0200, Thomas Gleixner wrote:
> > On Mon, 15 May 2017, Will Deacon wrote:
> > > On Mon, May 15, 2017 at 03:07:42PM +0200, Jiri Slaby wrote:
> > > > There is code duplicated over all architecture's headers for
> > > > futex
35 matches
Mail list logo
