On 06/17/2017 09:22 AM, Ram Pai wrote:
> The value of the AMR register at the time of exception
> is made available in gp_regs[PT_AMR] of the siginfo.
>
> This field can be used to reprogram the permission bits of
> any valid pkey.
>
> Similarly the value of the pkey, whose protection got violate
On 06/19/2017 11:29 PM, Ram Pai wrote:
> On Mon, Jun 19, 2017 at 09:06:13PM +1000, Michael Ellerman wrote:
>> Ram Pai writes:
>>
>>> Signed-off-by: Ram Pai
>>> ---
>>> arch/powerpc/kernel/exceptions-64s.S | 16 ++--
>>> 1 file changed, 10 insertions(+), 6 deletions(-)
>>>
>>> diff --
On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
> This patch exports current(A) sensors in inband sensors copied to
> main memory by OCC.
>
> Signed-off-by: Shilpasri G Bhat
Reviewed-by: Cédric Le Goater
Thanks,
C.
> ---
> Changes from V1:
> - Rebased on top of Cedric's patch to remove legay
On 06/17/2017 09:22 AM, Ram Pai wrote:
> Added test support for PowerPC implementation off protection keys.
>
> Signed-off-by: Ram Pai
First of all, there are a lot of instances where we use *pkru*
named functions on power even the real implementations have
taken care of doing appropriate things
Since trace_clock is in a different file and already marked with notrace,
enable tracing in time.c by removing it from the disabled list in Makefile.
Also annotate clocksource read functions and sched_clock with notrace.
Testing: Timer and ftrace selftests run with different trace clocks.
CC: Nav
On 06/17/2017 09:22 AM, Ram Pai wrote:
> The Documentaton file is moved from x86 into the generic area,
> since this feature is now supported by more than one archs.
>
> Signed-off-by: Ram Pai
> ---
> Documentation/vm/protection-keys.txt | 110
> ++
> Documentat
On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
> From: Cédric Le Goater
>
> Today, the type of a PowerNV sensor system is determined with the
> "compatible" property for legacy Firmwares and with the "sensor-type"
> for newer ones. The same array of strings is used for both to do the
> matching
On 06/20/2017 10:40 AM, Balbir Singh wrote:
> On Fri, 2017-06-16 at 20:52 -0700, Ram Pai wrote:
>> Memory protection keys enable applications to protect its
>> address space from inadvertent access or corruption from
>> itself.
>
> I presume by itself you mean protection between threads?
Between
Hi Michael,
Any thoughts/suggestions on the approach ?
On Tuesday 13 June 2017 12:20 PM, Kamalesh Babulal wrote:
R_PPC64_REL24 relocation type is used for a function call, where the
function symbol address is resolved and stub code (a.k.a trampoline)
is constructed to jump into the global entr
On Fri, 2017-06-16 at 20:52 -0700, Ram Pai wrote:
> Memory protection keys enable applications to protect its
> address space from inadvertent access or corruption from
> itself.
I presume by itself you mean protection between threads?
>
> The overall idea:
>
> A process allocates a key and
This patch exports current(A) sensors in inband sensors copied to
main memory by OCC.
Signed-off-by: Shilpasri G Bhat
---
Changes from V1:
- Rebased on top of Cedric's patch to remove legay-compatible type for
the current(A) sensor.
drivers/hwmon/ibmpowernv.c | 4 +++-
1 file changed, 3 inser
From: Cédric Le Goater
Today, the type of a PowerNV sensor system is determined with the
"compatible" property for legacy Firmwares and with the "sensor-type"
for newer ones. The same array of strings is used for both to do the
matching and this raises some issue to introduce new sensor types.
L
The first patch from Cedric in the patchset cleans up the driver to
provide a neater way to define new sensor types. The second patch adds
current sensor.
Cédric Le Goater (1):
hwmon: (ibmpowernv) introduce a legacy_compatibles array
Shilpasri G Bhat (1):
hwmon: (ibmpowernv) Add current(A) se
Hi Cedric,
On 06/19/2017 06:22 PM, Cédric Le Goater wrote:
> On 06/19/2017 11:25 AM, Shilpasri G Bhat wrote:
>> This patch exports current(A) sensors in inband sensors copied to
>> main memory by OCC.
>>
>> Signed-off-by: Shilpasri G Bhat
>> ---
>> drivers/hwmon/ibmpowernv.c | 4 +++-
>> 1 file
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
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
powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU
or memory resources, it may occur that the new resources are to be
inserted into nodes that were not used for these resources at bootup.
In the kernel, any node that is used must be defined and initialized
at boot. In order to
On Power systems with shared configurations of CPUs and memory, there
are some issues with association of additional CPUs and memory to nodes
when hot-adding resources. These patches address some of those problems.
powerpc/hotplug: On systems like PowerPC which allow 'hot-add' of CPU
or memory r
The bits of BWC, DAHTS and SAHTS in the DMA mode register must be cleared
before a new value can be or-ed in.
Signed-off-by: Thomas Breitung
Signed-off-by: Wolfgang Ocker
---
drivers/dma/fsldma.c | 5 -
drivers/dma/fsldma.h | 4
2 files changed, 8 insertions(+), 1 deletion(-)
diff --g
On 2017/06/19 03:21PM, Aneesh Kumar K.V wrote:
> > @@ -1445,8 +1446,8 @@ do_hash_page:
> > handle_page_fault:
> > andis. r0,r4,DSISR_DABRMATCH@h
> > bne-handle_dabr_fault
> > - ld r4,_DAR(r1)
> > - ld r5,_DSISR(r1)
> > + mr r5,r4
> > + mr r4,r3
> > addi
On Mon, Jun 19, 2017 at 09:06:13PM +1000, Michael Ellerman wrote:
> Ram Pai writes:
>
> > Signed-off-by: Ram Pai
> > ---
> > arch/powerpc/kernel/exceptions-64s.S | 16 ++--
> > 1 file changed, 10 insertions(+), 6 deletions(-)
> >
> > diff --git a/arch/powerpc/kernel/exceptions-64s.S
On Mon, Jun 19, 2017 at 12:52:14PM +0530, Anshuman Khandual wrote:
> On 06/17/2017 09:30 PM, Ram Pai wrote:
> >
> > This fix, resolved the OOM seen while running subpage_prot selftest, in a
> > infinite loop.
>
> The OOM is caused because of memory leaks by wrong freeing
> of the subpage_prot_tab
On Mon, 19 Jun 2017 21:45:06 +1000
Michael Ellerman wrote:
> Nicholas Piggin writes:
>
> > The EXCEPTION_PROLOG_1 used by SLB miss already saves CTR when the
> > kernel is built with CONFIG_RELOCATABLE. So it does not have to be
> > saved and reloaded when branching to slb_miss_realmode. It can
On Mon, 19 Jun 2017 14:48:37 +1000
Michael Ellerman wrote:
> Nicholas Piggin writes:
>
> > diff --git a/arch/powerpc/kernel/exceptions-64s.S
> > b/arch/powerpc/kernel/exceptions-64s.S
> > index 486e205cc762..6ba4c4c6ae69 100644
> > --- a/arch/powerpc/kernel/exceptions-64s.S
> > +++ b/arch/powe
On 16/06/17 19:10, Christoph Hellwig wrote:
> DMA_ERROR_CODE is not a public API and will go away soon. dma dma-iommu
> driver already implements a proper ->mapping_error method, so it's only
> using the value internally. Add a new local define using the value
> that arm64 which is the only curre
Make sure dma_ops are set, to be later used by the Ethernet driver.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/fman/mac.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/ethernet/freescale/fman/mac.c
b/drivers/net/ethernet/freescale/fman/mac.c
index 0b31f8
Remove the use of arch_setup_dma_ops() that was not exported
and was breaking loadable module compilation.
Signed-off-by: Madalin Bucur
---
drivers/net/ethernet/freescale/dpaa/dpaa_eth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/freescale/dpaa/dpaa_
The DPAA Ethernet makes use of a symbol that is not exported.
Address the issue by propagating the dma_ops rather than calling
arch_setup_dma_ops().
Madalin Bucur (2):
fsl/fman: propagate dma_ops
dpaa_eth: reuse the dma_ops provided by the FMan MAC device
drivers/net/ethernet/freescale/dpaa/
Le 15/06/2017 à 14:36, Frederic Barrat a écrit :
Salut Christophe,
A few comments below, nothing major...
Le 14/06/2017 à 15:29, Christophe Lombard a écrit :
This patch exports a in-kernel 'library' API which can be called by
other drivers to help interacting with an IBM XSL on a POWER9 system
On Monday 19 June 2017 09:25 AM, Anton Blanchard wrote:
From: Anton Blanchard
The POWER9 branch event is wrong, and we always get a count of zero:
...
0 branches
3844 branch-misses #0.00% of all branches
Replace it with the correct
On 06/19/2017 11:25 AM, Shilpasri G Bhat wrote:
> This patch exports current(A) sensors in inband sensors copied to
> main memory by OCC.
>
> Signed-off-by: Shilpasri G Bhat
> ---
> drivers/hwmon/ibmpowernv.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hw
Forwarded Message
Subject: Debian 9 "Stretch" released
Resent-Date: Sun, 18 Jun 2017 06:26:39 + (UTC)
Resent-From: debian-annou...@lists.debian.org
Date: Sat, 17 Jun 2017 20:22:36 -1000
From: Ana Guerrero Lopez
To: debian-annou...@lists.debian.org
--
On Tue, 2017-06-13 at 13:05:57 UTC, Nicholas Piggin wrote:
> 2*mfmsr and 2*mtmsr can be avoided in the idle sleep/wake code
> because we know the MSR[EE] is clear.
>
> Acked-by: Vaidyanathan Srinivasan
> Signed-off-by: Nicholas Piggin
Applied to powerpc next, thanks.
https://git.kernel.org/pow
On Tue, 2017-06-13 at 13:05:52 UTC, Nicholas Piggin wrote:
> In a busy system, idle wakeups can be expected from IPIs and device
> interrupts.
>
> Reviewed-by: Gautham R. Shenoy
> Signed-off-by: Nicholas Piggin
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/95acdc07124f329ef
On Tue, 2017-06-13 at 13:05:51 UTC, Nicholas Piggin wrote:
> Idle code now always runs at the 0xc... effective address whether
> in real or virtual mode. This means rfid can be ditched, along
> with a lot of SRR manipulations.
>
> In the wakeup path, carry SRR1 around in r12. Use mtmsrd to change
On Tue, 2017-06-13 at 13:05:50 UTC, Nicholas Piggin wrote:
> Have the system reset idle wakeup handlers branched to in real mode
> with the 0xc... kernel address applied. This allows simplifications of
> avoiding rfid when switching to virtual mode in the wakeup handler.
>
> Signed-off-by: Nichola
On Tue, 2017-06-13 at 13:05:49 UTC, Nicholas Piggin wrote:
> The __replay_interrupt code is branched to with bl, but the caller is
> returned to directly with rfid from the interrupt.
>
> Instead, rfid to a stub that returns to the caller with blr, which
> should keep the return branch predictor b
On Tue, 2017-06-13 at 13:05:48 UTC, Nicholas Piggin wrote:
> msgsnd doorbell exceptions are cleared when the doorbell interrupt is
> taken. However if a doorbell exception causes a system reset interrupt
> wake from power saving state, the message is not cleared. Processing
> the doorbell from the
On Tue, 2017-06-13 at 13:05:47 UTC, Nicholas Piggin wrote:
> When the CPU wakes from low power state, it begins at the system reset
> interrupt with the exception that caused the wakeup encoded in SRR1.
>
> Today, powernv idle wakeup ignores the wakeup reason (except a special
> case for HMI), and
On Tue, 2017-06-13 at 13:05:46 UTC, Nicholas Piggin wrote:
> Rather than concern ourselves with any soft-mask logic in the CPU
> hotplug handler, just hard disable interrupts. This ensures there
> are no lazy-irqs pending, which means we can call directly to idle
> instruction in order to sleep.
>
On Tue, 2017-06-13 at 13:05:45 UTC, Nicholas Piggin wrote:
> This simplifies the asm and fixes irq-off tracing over sleep
> instructions.
>
> Also move powersave_nap check for POWER8 into C code, and move
> PSSCR register value calculation for POWER9 into C.
>
> Reviewed-by: Gautham R. Shenoy
>
On Thu, 2017-06-08 at 15:36:06 UTC, Nicholas Piggin wrote:
> Commit 4387e9ff25 ("[POWERPC] Fix PMU + soft interrupt disable bug")
> hard disabled interrupts over the low level context switch, because
> the SLB management can't cope with a PMU interrupt accesing the stack
> in that window.
>
> Radi
On Thu, 2017-06-08 at 15:35:04 UTC, Nicholas Piggin wrote:
> After bc3551257a ("powerpc/64: Allow for relocation-on interrupts from
> guest to host"), a getppid() system call goes from 307 cycles to 358
> cycles (+17%) on POWER8. This is due significantly to the scratch SPR
> used by the hypercall
On Tue, 2017-06-06 at 05:48:57 UTC, Michael Ellerman wrote:
> Currently we map the whole linear mapping with PAGE_KERNEL_X. Instead we
> should check if the page overlaps the kernel text and only then add
> PAGE_KERNEL_X.
>
> Note that we still use 1G pages if they're available, so this will
> typ
On Mon, 2017-05-29 at 13:26:28 UTC, Murilo Opsfelder Araujo wrote:
> drivers/watchdog/wdrtas.c uses symbols defined in arch/powerpc/kernel/rtas.c,
> which are exported iff CONFIG_PPC_RTAS is selected. Building wdrtas.c without
> setting CONFIG_PPC_RTAS throws the following errors:
>
> ERROR: "
On Thu, 2017-06-15 at 13:46:48 UTC, Ravi Bangoria wrote:
> When a kthread makes a call_usermodehelper() call the steps are:
> a. allocates current->mm
> b. load_elf_binary()
> c. populates current->thread.regs
>
> While doing this, interrupts are not disabled. If there is a perf
> interrupt in
On Tue, 2017-06-13 at 18:42:00 UTC, "Naveen N. Rao" wrote:
> On P9, trying to use data breakpoints throws the splat shown below (*).
> This is because the check for a data breakpoint in DSISR is in
> do_hash_page(). Move this check to handle_page_fault() so as to catch
> data breakpoints in both ha
On Thu, 2017-06-01 at 10:48:16 UTC, "Naveen N. Rao" wrote:
> For DYNAMIC_FTRACE_WITH_REGS, we should be passing-in the original set
> of registers in pt_regs, to capture the state _before_ ftrace_caller.
> However, we are instead passing the stack pointer *after* allocating a
> stack frame in ftrac
On Thu, 2017-06-01 at 10:48:17 UTC, "Naveen N. Rao" wrote:
> ftrace_caller() depends on a modified regs->nip to detect if a certain
> function has been livepatched. However, with KPROBES_ON_FTRACE, it is
> possible for regs->nip to have been modified by the kprobes pre_handler
> (jprobes, for insta
On Thu, 2017-06-01 at 10:48:15 UTC, "Naveen N. Rao" wrote:
> This fixes a crash when function_graph and jprobes are used together.
> This is essentially commit 237d28db036e ("ftrace/jprobes/x86: Fix
> conflict between jprobes and function graph tracing"), but for powerpc.
>
> Jprobes breaks functi
Hi Ram,
Ram Pai writes:
> Sys_pkey_alloc() allocates and returns available pkey
> Sys_pkey_free() frees up the pkey.
>
> Total 32 keys are supported on powerpc. However pkey 0,1 and 31
> are reserved. So effectively we have 29 pkeys.
>
> Signed-off-by: Ram Pai
> ---
> include/linux/mm.h
Nicholas Piggin writes:
> The EXCEPTION_PROLOG_1 used by SLB miss already saves CTR when the
> kernel is built with CONFIG_RELOCATABLE. So it does not have to be
> saved and reloaded when branching to slb_miss_realmode. It can be
> restored from the PACA as usual.
>
> Signed-off-by: Nicholas Pigg
Ram Pai writes:
> Signed-off-by: Ram Pai
> ---
> arch/powerpc/kernel/exceptions-64s.S | 16 ++--
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/arch/powerpc/kernel/exceptions-64s.S
> b/arch/powerpc/kernel/exceptions-64s.S
> index 8db9ef8..a4de1b4 100644
> --- a
Ram Pai writes:
> Added test support for PowerPC implementation off protection keys.
>
> Signed-off-by: Ram Pai
> ---
> tools/testing/selftests/vm/Makefile |1 +
> tools/testing/selftests/vm/pkey-helpers.h | 365 +++
> tools/testing/selftests/vm/protection_keys.c | 1451
On 2017/06/19 03:21PM, Aneesh Kumar K.V wrote:
> "Naveen N. Rao" writes:
>
> > On 2017/06/16 03:16PM, Michael Ellerman wrote:
> >> "Naveen N. Rao" writes:
> >>
> >> > diff --git a/arch/powerpc/kernel/exceptions-64s.S
> >> > b/arch/powerpc/kernel/exceptions-64s.S
> >> > index ae418b85c17c..17ee
On 06/18/17 07:05, Rob Herring wrote:
> On Tue, Jun 13, 2017 at 07:49:04PM -0700, frowand.l...@gmail.com wrote:
>> From: Frank Rowand
>>
>> The Devicetree Specification has superseded the ePAPR as the
>> base specification for bindings. Update files in Documentation
>> to reference the new docume
"Naveen N. Rao" writes:
> On 2017/06/16 03:16PM, Michael Ellerman wrote:
>> "Naveen N. Rao" writes:
>>
>> > diff --git a/arch/powerpc/kernel/exceptions-64s.S
>> > b/arch/powerpc/kernel/exceptions-64s.S
>> > index ae418b85c17c..17ee701b8336 100644
>> > --- a/arch/powerpc/kernel/exceptions-64s.S
This patch exports current(A) sensors in inband sensors copied to
main memory by OCC.
Signed-off-by: Shilpasri G Bhat
---
drivers/hwmon/ibmpowernv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/hwmon/ibmpowernv.c b/drivers/hwmon/ibmpowernv.c
index 862b832..e0557
On 06/17/2017 09:30 PM, Ram Pai wrote:
>
> This fix, resolved the OOM seen while running subpage_prot selftest, in a
> infinite loop.
The OOM is caused because of memory leaks by wrong freeing
of the subpage_prot_table previously ?
59 matches
Mail list logo
