On Wed, 5 Jul 2017 14:21:39 -0700
Ram Pai wrote:
> Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6
> in the 64K backed HPTE pages. This along with the earlier
> patch will entirely free up the four bits from 64K PTE.
> The bit numbers are big-endian as defined in the ISA3.0
>
> Th
This configuration is used by the OpenPower firmware for it's
Linux-as-bootloader implementation. Also known as the Petitboot kernel,
this configuration broke in 4.12 (CPU_HOTPLUG=n), so add it to the
upstream tree in order to get better coverage.
Signed-off-by: Joel Stanley
---
arch/powerpc/con
On Sat, Jul 08, 2017 at 07:05:26PM +1000, Nicholas Piggin wrote:
> On Fri, 7 Jul 2017 23:07:10 +0530
> Gautham R Shenoy wrote:
>
> > On Fri, Jul 07, 2017 at 01:29:16AM +1000, Nicholas Piggin wrote:
> > > On Wed, 5 Jul 2017 22:08:16 +0530
> > > "Gautham R. Shenoy" wrote:
> > >
> > > > From: "
On Tue, Jul 11, 2017 at 9:53 AM, Dan Williams wrote:
> On Tue, Jun 27, 2017 at 3:28 AM, Oliver O'Halloran wrote:
>> struct device contains the ->of_node pointer so that devices can be
>> assoicated with the device-tree node that created them on DT platforms.
>> libnvdimm hides the struct device f
Hi Cyril,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.12 next-20170710]
[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/Cyril-Bur/Allow-opal-async-waiters-to-get
On Mon, Jul 10, 2017 at 9:50 PM, Michael Ellerman wrote:
> Oliver O'Halloran writes:
>
>> The workaround for the CELL timebase bug does not correctly mark cr0 as
>> being clobbered. This can result in GCC making some poor^W completely
>> broken optimisations.
>
> Fruit 'n oats, how did we never n
On 7/11/2017 10:28 AM, Michael Ellerman wrote:
"Jin, Yao" writes:
On 7/10/2017 9:46 PM, Peter Zijlstra wrote:
On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote:
PERF_BR_INT is triggered by instruction "int" .
PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jul 10, 2017 at 09:50:06PM +1000, Michael Ellerman wrote:
>> Oliver O'Halloran writes:
>>
>> > The workaround for the CELL timebase bug does not correctly mark cr0 as
>> > being clobbered. This can result in GCC making some poor^W completely
>> > bro
"Jin, Yao" writes:
> On 7/10/2017 9:46 PM, Peter Zijlstra wrote:
>> On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote:
>>
PERF_BR_INT is triggered by instruction "int" .
PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3
transition).
>>> So your "P
Segher Boessenkool writes:
> Hi!
>
> On Mon, Jul 10, 2017 at 07:46:17PM +0800, Jin, Yao wrote:
>> 1. We all agree these definitions:
>>
>> +PERF_BR_COND= 1,/* conditional */
>> +PERF_BR_UNCOND = 2,/* unconditional */
>> +PERF_BR_IND = 3,/*
This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag
because it doesn't copy anything from/to userspace to access the
argument.
Acked-by: Aleksa Sarai
Oops, I misunderstood what _IOR means semantically. TIL -- thanks!
--
Aleksa Sarai
Software Engineer (Containers)
SUSE Linux G
This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag
because it doesn't copy anything from/to userspace to access the
argument.
Fixes: 54ebbfb1 ("tty: add TIOCGPTPEER ioctl")
Signed-off-by: Gleb Fotengauer-Malinovskiy
---
arch/alpha/include/uapi/asm/ioctls.h | 2 +-
arch/mips/inc
On Mon, 2017-07-10 at 14:05 +, David Laight wrote:
> From: Cyril Bur
> > Sent: 10 July 2017 02:31
> > This patch adds an _interruptible version of opal_async_wait_response().
> > This is useful when a long running OPAL call is performed on behalf of a
> > userspace thread, for example, the opal
On Tue, Jun 27, 2017 at 3:28 AM, Oliver O'Halloran wrote:
> Adds powerpc64 implementations of:
>
> memcpy_flushcache()
> arch_wb_cache_pmem()
> arch_invalidate_pmem()
>
> Which form the architecture-specific portition of the persistent memory
> API. These functions provide
On Tue, Jun 27, 2017 at 3:28 AM, Oliver O'Halloran wrote:
> struct device contains the ->of_node pointer so that devices can be
> assoicated with the device-tree node that created them on DT platforms.
> libnvdimm hides the struct device for regions and nvdimm devices inside
> of an opaque structu
On Mon, 2017-07-10 at 18:17 +0300, Andy Shevchenko wrote:
> On Mon, Jul 10, 2017 at 5:37 PM, Abdul Haleem
> wrote:
> > On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote:
> >> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem
> >> wrote:
> >> > next-20170705 fails to build on powerpc with below
On Sun, Jul 09, 2017 at 11:05:44PM -0700, Ram Pai wrote:
> On Mon, Jul 10, 2017 at 11:13:23AM +0530, Anshuman Khandual wrote:
> > On 07/06/2017 02:51 AM, Ram Pai wrote:
.
>
> > do you have data points to show the difference in
> > performance between this version and the last one where
> > we
On 06/29, James Morse wrote:
>
> compat_ptrace_request() lacks handlers for PTRACE_{G,S}ETSIGMASK,
> instead using those in ptrace_request(). The compat variant should
> read a compat_sigset_t from userspace instead of ptrace_request()s
> sigset_t.
Acked-by: Oleg Nesterov
On Mon, Jul 10, 2017 at 5:37 PM, Abdul Haleem
wrote:
> On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote:
>> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem
>> wrote:
>> > next-20170705 fails to build on powerpc with below errors.
>> I had sent a fix yesterday. Had you chance to test it?
> d
Hi Peter,
On Mon, Jul 10, 2017 at 03:46:58PM +0200, Peter Zijlstra wrote:
> On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote:
>
> > > PERF_BR_INT is triggered by instruction "int" .
> > > PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3
> > > transition).
> >
On Fri, 2017-07-07 at 19:36 +0300, Andy Shevchenko wrote:
> On Thu, Jul 6, 2017 at 9:00 AM, Abdul Haleem
> wrote:
> > Hi Luis,
> >
> > next-20170705 fails to build on powerpc with below errors.
>
> Hi,
>
> I had sent a fix yesterday. Had you chance to test it?
>
>
Are these the one you are re
On 7/10/2017 9:46 PM, Peter Zijlstra wrote:
On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote:
PERF_BR_INT is triggered by instruction "int" .
PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3
transition).
So your "PERF_BR_INT" is a system call?
The "INT"
From: Cyril Bur
> Sent: 10 July 2017 02:31
> This patch adds an _interruptible version of opal_async_wait_response().
> This is useful when a long running OPAL call is performed on behalf of a
> userspace thread, for example, the opal_flash_{read,write,erase}
> functions performed by the powernv-fl
On Mon, Jul 10, 2017 at 08:10:50AM -0500, Segher Boessenkool wrote:
> > PERF_BR_INT is triggered by instruction "int" .
> > PERF_BR_IRQ is triggered by interrupts, traps, faults (the ring 0,3
> > transition).
>
> So your "PERF_BR_INT" is a system call?
The "INT" thing has indeed been used as s
Hi!
On Mon, Jul 10, 2017 at 09:50:06PM +1000, Michael Ellerman wrote:
> Oliver O'Halloran writes:
>
> > The workaround for the CELL timebase bug does not correctly mark cr0 as
> > being clobbered. This can result in GCC making some poor^W completely
> > broken optimisations.
>
> Fruit 'n oats,
Hi,
Following branch types should be common enough, right?
+ PERF_BR_COND= 1,/* conditional */
+ PERF_BR_UNCOND = 2,/* unconditional */
+ PERF_BR_IND = 3,/* indirect */
+ PERF_BR_CALL= 4,/* call */
+ PERF_
Hi!
On Mon, Jul 10, 2017 at 07:46:17PM +0800, Jin, Yao wrote:
> 1. We all agree these definitions:
>
> + PERF_BR_COND= 1,/* conditional */
> + PERF_BR_UNCOND = 2,/* unconditional */
> + PERF_BR_IND = 3,/* indirect */
> + PERF_BR_CALL
On Monday 10 July 2017 11:49 AM, Nicholas Piggin wrote:
POWER9 DD2 can see spurious PMU interrupts after state-loss idle in
some conditions.
A solution is to save and reload MMCR0 over state-loss idle.
Acked-by: Madhavan Srinivasan
Signed-off-by: Nicholas Piggin
---
arch/powerpc/kernel
Oliver O'Halloran writes:
> The workaround for the CELL timebase bug does not correctly mark cr0 as
> being clobbered. This can result in GCC making some poor^W completely
> broken optimisations.
Fruit 'n oats, how did we never notice that? Luck I guess. Or subtle
breakage that no one could pin
Hi Michael,
Please let me summarize for the new branch type definitions.
1. We all agree these definitions:
+ PERF_BR_COND= 1,/* conditional */
+ PERF_BR_UNCOND = 2,/* unconditional */
+ PERF_BR_IND = 3,/* indirect */
+ PERF_B
luigi burdo writes:
> Hi all, kernel here is not building.
Did it just stop working? That code is from 2014?
> attached file will explain better than my poor english.
>
> Host Machine BE Qoriq e5500 16GB ram
What userspace are you running? Is it 32-bit ?
> HOSTCC arch/powerpc/boot/addnote
Joel Stanley writes:
> In commit 900612315788 ("powerpc/powernv/smp: Add busy-wait loop as fall back
> for CPU-Hotplug") the idle code uses generic_check_cpu_restart(), but that
> function is not available when CONFIG_HOTPLUG_CPU is disabled.
>
> arch/powerpc/platforms/powernv/idle.c: In function
Benjamin Herrenschmidt writes:
> On Mon, 2017-07-10 at 13:51 +1000, Michael Ellerman wrote:
>> Benjamin Herrenschmidt writes:
>>
>> > On radix, the process table entry we want to clear when
>> > destroying a context is entry 0, not entry 1
>>
>> .. but has no real world consequence? Or causes
"Jin, Yao" writes:
> On 7/10/2017 2:05 PM, Michael Ellerman wrote:
>> Jin Yao writes:
>>
>>> It is often useful to know the branch types while analyzing branch
>>> data. For example, a call is very different from a conditional branch.
>>>
...
>>> To keep consistent on kernel and userspace and mak
On Thu, Jun 29, 2017 at 05:26:37PM +0100, James Morse wrote:
> compat_ptrace_request() lacks handlers for PTRACE_{G,S}ETSIGMASK,
> instead using those in ptrace_request(). The compat variant should
> read a compat_sigset_t from userspace instead of ptrace_request()s
> sigset_t.
>
> While compat_si
On 7/10/2017 2:05 PM, Michael Ellerman wrote:
Hi Jin Yao,
Sorry I haven't commented until now, but it got lost in the flood of
patches.
Never mind, it's no problem. :)
Just a few nit-picks below ...
Jin Yao writes:
It is often useful to know the branch types while analyzing branch
data.
Hello Wolfram,
On Thu, Jun 15, 2017 at 8:54 PM, Javier Martinez Canillas
wrote:
>
> This series is a follow-up to patch [0] that added an OF device ID table
> to the at24 EEPROM driver. As you suggested [1], this version instead of
> adding entries for every used tuple, only adds a single
> entr
Get the affine portal only once for the complete transaction.
Signed-off-by: Sebastian Huber
---
drivers/soc/fsl/qbman/bman.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/soc/fsl/qbman/bman.c b/drivers/soc/fsl/qbman/bman.c
index a3d6d7cfa929..0af206
38 matches
Mail list logo
