Re: POWER: Unexpected fault when writing to brk-allocated memory

On Mon, 06 Nov 2017 11:48:06 +0530 "Aneesh Kumar K.V" wrote: > Nicholas Piggin writes: > > > On Fri, 3 Nov 2017 18:05:20 +0100 > > Florian Weimer wrote: > > > >> We are seeing an issue on ppc64le and ppc64 (and perhaps

Re: [PATCH] powerpc/opal: Fix EBUSY bug in acquiring tokens

> On Nov 4, 2017, at 2:14 AM, Michael Ellerman > wrote: > > "William A. Kennington III" > writes: > >> The current code checks the completion map to look for the first token >> that is complete. In some

Re: POWER: Unexpected fault when writing to brk-allocated memory

Nicholas Piggin writes: > On Fri, 3 Nov 2017 18:05:20 +0100 > Florian Weimer wrote: > >> We are seeing an issue on ppc64le and ppc64 (and perhaps on some arm >> variant, but I have not seen it on our own builders) where running >> localedef as part of

Re: [RFC PATCH kernel] powerpc/pci: Get rid of unused @parent pointer in pci_controller

On 06/11/17 14:33, Benjamin Herrenschmidt wrote: > On Mon, 2017-11-06 at 14:24 +1100, Alexey Kardashevskiy wrote: >> The @parent pointer is supposed to point to a device which represents >> a PCI controller, however it is never set to anything and remains NULL; >> it is also quite common to pass

Re: [RFC PATCH kernel] powerpc/pci: Get rid of unused @parent pointer in pci_controller

On Mon, 2017-11-06 at 14:24 +1100, Alexey Kardashevskiy wrote: > The @parent pointer is supposed to point to a device which represents > a PCI controller, however it is never set to anything and remains NULL; > it is also quite common to pass NULL to pci_create_root_bus(). > > Signed-off-by:

Re: [PATCH] powerpc: eeh: stop using do_gettimeofday()

On Sat, 2017-11-04 at 22:26 +0100, Arnd Bergmann wrote: > This interface is inefficient and deprecated because of the y2038 > overflow. > > ktime_get_seconds() is an appropriate replacement here, since it > has sufficient granularity but is more efficient and uses monotonic > time. > >

Re: [PATCH] powerpc: eeh: stop using do_gettimeofday()

On 05/11/17 08:26, Arnd Bergmann wrote: This interface is inefficient and deprecated because of the y2038 overflow. ktime_get_seconds() is an appropriate replacement here, since it has sufficient granularity but is more efficient and uses monotonic time. Signed-off-by: Arnd Bergmann

[RFC PATCH kernel] powerpc/pci: Get rid of unused @parent pointer in pci_controller

The @parent pointer is supposed to point to a device which represents a PCI controller, however it is never set to anything and remains NULL; it is also quite common to pass NULL to pci_create_root_bus(). Signed-off-by: Alexey Kardashevskiy --- This @parent is NULL for every PHB

Re: [PATCH] selftests/powerpc: Check FP/VEC on exception in TM

On Fri, 2017-11-03 at 10:28 -0200, Gustavo Romero wrote: > Hi Cyril! > > On 01-11-2017 20:10, Cyril Bur wrote: > > Thanks Gustavo, > > > > I do have one more thought on an improvement for this test which is > > that: > > + /* Counter for busy wait * > > + uint64_t counter = 0x1ff00; > >

Re: POWER: Unexpected fault when writing to brk-allocated memory

On 11/05/2017 01:18 PM, Nicholas Piggin wrote: Something like the following patch may help if you could test. The patch appears to fix it: # /lib64/ld64.so.1 ./a.out initial brk value: 0x7fffe459 probing at 0x8001fffc I used the follow simplified reproducer: #include #include

Re: POWER: Unexpected fault when writing to brk-allocated memory

On Sun, 5 Nov 2017 13:35:40 +0100 Florian Weimer wrote: > On 11/05/2017 01:18 PM, Nicholas Piggin wrote: > > > There was a recent change to move to 128TB address space by default, > > and option for 512TB addresses if explicitly requested. > > Do you have a commit hash

Re: POWER: Unexpected fault when writing to brk-allocated memory

On 11/05/2017 01:18 PM, Nicholas Piggin wrote: There was a recent change to move to 128TB address space by default, and option for 512TB addresses if explicitly requested. Do you have a commit hash for the introduction of 128TB by default? Thanks. Your brk request asked for > 128TB which

[PATCH] KVM: PPC: Book3S HV: Handle host system reset in guest mode

If the host takes a system reset interrupt while a guest is running, the CPU must exit the guest before processing the host exception handler. After this patch, taking a sysrq+x with a CPU running in a guest gives a trace like this: cpu 0x27: Vector: 100 (System Reset) at [c00fdf5776f0]

Re: POWER: Unexpected fault when writing to brk-allocated memory

On Fri, 3 Nov 2017 18:05:20 +0100 Florian Weimer wrote: > We are seeing an issue on ppc64le and ppc64 (and perhaps on some arm > variant, but I have not seen it on our own builders) where running > localedef as part of the glibc build crashes with a segmentation fault. > >