Michal Hocko writes:
> On Mon 13-11-17 22:34:50, Michael Ellerman wrote:
>> Hi Michal,
>>
>> Michal Hocko writes:
>> > On Mon 13-11-17 10:20:06, Michal Hocko wrote:
>> >> [Cc arm and ppc maintainers]
>> >
>> > Hmm, it turned out to be a problem on other architectures as well.
>> > CCing more ma
Michal Hocko writes:
> On Mon 13-11-17 13:00:57, Michal Hocko wrote:
> [...]
>> Yes, I have mentioned that in the previous email but the amount of code
>> would be even larger. Basically every arch which reimplements
>> arch_get_unmapped_area would have to special case new MAP_FIXED flag to
>> do
On Tue 14-11-17 19:54:59, Michael Ellerman wrote:
> Michal Hocko writes:
[...]
> > So this was the most simple solution I could come up
> > with. If there was a general interest for MAP_FIXED_SAFE then we can
> > introduce it later of course. I would just like the hardening merged
> > sooner rathe
Michal Hocko writes:
> [Sorry for spamming, this one is the last attempt hopefully]
>
> On Mon 13-11-17 16:49:39, Michal Hocko wrote:
>> On Mon 13-11-17 16:16:41, Michal Hocko wrote:
>> > On Mon 13-11-17 13:00:57, Michal Hocko wrote:
>> > [...]
>> > > Yes, I have mentioned that in the previous em
On Tue 14-11-17 20:18:04, Michael Ellerman wrote:
> Michal Hocko writes:
>
> > [Sorry for spamming, this one is the last attempt hopefully]
> >
> > On Mon 13-11-17 16:49:39, Michal Hocko wrote:
> >> On Mon 13-11-17 16:16:41, Michal Hocko wrote:
> >> > On Mon 13-11-17 13:00:57, Michal Hocko wrote:
This patchset drop the approach of creating new stub type for livepatch
symbols and offloads the issue of handling local function becoming global
to kpatch tool via gcc-plugin.
In function restore_r2(), a check for sibling call is added and also
improves the error message on unexpected op-code.
v
Livepatch re-uses module loader function apply_relocate_add() to write
relocations, instead of managing them by arch-dependent
klp_write_module_reloc() function.
apply_relocate_add() doesn't understand livepatch symbols (marked with
SHN_LIVEPATCH symbol section index) and assumes them to be local
From: Josh Poimboeuf
When attempting to load a livepatch module, I got the following error:
module_64: patch_module: Expect noop after relocate, got 3c82
The error was triggered by the following code in
unregister_netdevice_queue():
14c: 00 00 00 48 b 14c
From: Josh Poimboeuf
Print the function address associated with the restore_r2() error to
make it easier to debug the problem.
Also clarify the wording a bit.
Before:
module_64: patch_foo: Expect noop after relocate, got 3c82
After:
module_64: patch_foo: Expected noop after call, got
On 64-bit Book3s, when we take an instruction fault the reason for the
fault may be reported in SRR1. For data faults the reason is reported
in DSISR (Data Storage Instruction Status Register).
The reasons reported in each do not necessarily correspond, so we mask
the SRR1 bits before copying them
Masahiro Yamada writes:
> Hi Nicholas,
>
>
> 2017-11-11 17:45 GMT+09:00 Nicholas Piggin :
>> On Fri, 10 Nov 2017 23:41:49 +0800
>> kbuild test robot wrote:
>>
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>> master
>>> head: 1c9dbd4615fd751e5e0b99807a3c7c8612
Nathan Fontenot writes:
> On 11/12/2017 06:43 AM, Michael Ellerman wrote:
...
>> The bigger problem we have though is that you're trying to allocate
>> memory, in order to find out what memory we have :)
>>
>> I suspect it works in some cases because you hit the memory@0 node first
>> in the devi
Kamalesh Babulal wrote:
From: Josh Poimboeuf
When attempting to load a livepatch module, I got the following error:
module_64: patch_module: Expect noop after relocate, got 3c82
The error was triggered by the following code in
unregister_netdevice_queue():
14c: 00 00 00 48 b
On Mon, 2017-06-26 at 14:06:01 UTC, Michal Suchanek wrote:
> Currently sysfs store handlers in fadump use if buf[0] == 'char'.
>
> This means input "100foo" is interpreted as '1' and "01" as '0'.
>
> Change to kstrtoint so leading zeroes and the like is handled in
> expected way.
>
> Signed-off-
On Tue, 2017-07-11 at 11:26:26 UTC, Michal Suchanek wrote:
> In commit e6f81a92015b ("powerpc/mm/hash: Support 68 bit VA") the
> masking is folded into ASM_VSID_SCRAMBLE but the comment about masking
> is removed only from the firt use of ASM_VSID_SCRAMBLE.
>
> Signed-off-by: Michal Suchanek
App
On Wed, 2017-08-23 at 18:58:41 UTC, Vaidyanathan Srinivasan wrote:
> On PowerNV platforms, firmware provides exit latency and
> target residency for each of the idle states in nano
> seconds. Cpuidle framework expects the values in micro
> seconds. Round up to nearest micro seconds to avoid error
On Thu, 2017-08-31 at 16:25:57 UTC, "Naveen N. Rao" wrote:
> When a uprobe is installed on an instruction that we currently do not
> emulate, we copy the instruction into a xol buffer and single step
> that instruction. If that instruction generates a fault, we abort the
> single stepping before in
On Wed, 2017-09-06 at 01:48:59 UTC, Alistair Popple wrote:
> With the optimisations introduced by commit a46cc7a908 ("powerpc/mm/radix:
> Improve TLB/PWC flushes"), flush_tlb_mm() no longer flushes the page walk
> cache with radix. Switch to using flush_all_mm() to ensure the pwc and tlb
> are prop
On Mon, 2017-09-25 at 06:43:02 UTC, Haren Myneni wrote:
> [PATCH 1/2] crypto/nx: Use percpu send window for NX requests
>
> For P9 NX, the send window is opened for each crypto session and closed
> upon free. But VAS supports 64K windows per chip for all coprocessors
> including in user space supp
On Fri, 2017-10-13 at 04:36:41 UTC, Shriya wrote:
> The call to /proc/cpuinfo in turn calls cpufreq_quick_get() which
> returns the last frequency requested by the kernel, but may not
> reflect the actual frequency the processor is running at.
> This patch makes a call to cpufreq_get() instead whic
On Mon, 2017-10-16 at 05:21:35 UTC, Balbir Singh wrote:
> When using the radix MMU on Power9 DD1, to work around a hardware
> problem, radix__pte_update() is required to do a two stage update of
> the PTE. First we write a zero value into the PTE, then we flush the
> TLB, and then we write the new
On Thu, 2017-10-19 at 07:13:54 UTC, Oliver O'Halloran wrote:
> Implement the architecture specific cache maintence functions that make
> up the "PMEM API". Currently the writeback and invalidate functions
> are the same since the function of the DCBST (data cache block store)
> instruction is typic
On Mon, 2017-10-23 at 08:05:07 UTC, Nicholas Piggin wrote:
> OPAL boot does not insert secondaries at 0x60 to wait at the secondary
> hold spinloop. Instead they are started later, and inserted at
> generic_secondary_smp_init(), which is after the secondary hold
> spinloop.
>
> Avoid waiting on th
On Mon, 2017-10-23 at 16:37:38 UTC, "Naveen N. Rao" wrote:
> Per Documentation/kprobes.txt, probe handlers need to be invoked with
> preemption disabled. Update optimized_callback() to do so. Also move
> get_kprobe_ctlblk() invocation post preemption disable, since it
> accesses pre-cpu data.
>
>
On Tue, 2017-10-24 at 11:44:44 UTC, Nicholas Piggin wrote:
> Take the DSCR value set by firmware as the dscr_default value,
> rather than zero.
>
> POWER9 recommends DSCR default to a non-zero value.
>
> From: Nicholas Piggin
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/16
On Tue, 2017-11-07 at 07:53:05 UTC, Nicholas Piggin wrote:
> Short range flushes issue a sequences of tlbie(l) instructions for
> individual effective addresses. These do not all require individual
> barrier sequences, only one covering all tlbie(l) instructions.
>
> Commit f7327e0ba3 ("powerpc/mm
On Mon, 2017-10-30 at 11:01:12 UTC, Balbir Singh wrote:
> It would be nice to be able to dump page tables in a particular
> context.
>
> eg: dumping vmalloc space:
>
> 0:mon> dv 0xd00037f0
> pgd @ 0xc17c
> pgdp @ 0xc17c00d8 = 0xf10b1000
> pudp @ 0xc000
On Wed, 2017-11-01 at 19:23:41 UTC, Gustavo Romero wrote:
> Add a self test to check if FP/VEC/VSX registers are sane (restored
> correctly) after a FP/VEC/VSX unavailable exception is caught during a
> transaction.
>
> This test checks all possibilities in a thread regarding the combination
> of
On Thu, 2017-11-02 at 06:49:36 UTC, Stephen Rothwell wrote:
> Hi all,
>
> After merging the powerpc tree, today's linux-next build (powerpc64
> allnoconfig) failed like this:
>
> arch/powerpc/kernel/irq.o: In function `.replay_system_reset':
> irq.c:(.text+0x10): undefined reference to `.ppc_save
On Tue, 2017-11-07 at 03:43:01 UTC, Alexey Kardashevskiy wrote:
> DMA windows can only have a size of power of two on IODA2 hardware and
> using memory_hotplug_max() to determine the upper limit won't work
> correcly if it returns not power of two value.
>
> This removes the check as the platform
On Tue, 2017-11-07 at 07:53:06 UTC, Nicholas Piggin wrote:
> Move the barriers and range iteration down into the _tlbie* level,
> which improves readability.
>
> Signed-off-by: Nicholas Piggin
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/d665767e39fa4a9e725f92d77ba206
chee
On Tue, 2017-11-07 at 07:53:07 UTC, Nicholas Piggin wrote:
> Currently for radix, flush_tlb_range flushes the entire PID, because
> the Linux mm code does not tell us about page size here for THP vs
> regular pages. This is quite sub-optimal for small mremap / mprotect
> / change_protection.
>
> S
On Tue, 2017-11-07 at 07:53:08 UTC, Nicholas Piggin wrote:
> The single page flush ceiling is the cut-off point at which we switch
> from invalidating individual pages, to invalidating the entire process
> address space in response to a range flush.
>
> Introduce a local variant of this heuristic
On Tue, 2017-11-07 at 07:53:09 UTC, Nicholas Piggin wrote:
> Unmaps that free page tables always flush the entire PID, which is
> sub-optimal. Provide TLB range flushing with an additional PWC flush
> that can be use for va range invalidations with PWC flush.
>
> Time to munmap N pages of mem
On Wed, 2017-11-08 at 02:23:41 UTC, Sukadev Bhattiprolu wrote:
> Initialize a few missing window context fields from the window attributes
> specified by the caller. These fields are currently set to their default
> values by the caller (NX-842), but would be good to apply them anyway.
>
> Signed-
On Thu, 2017-11-09 at 17:27:36 UTC, Nicholas Piggin wrote:
> When allocating VA space with a hint that crosses 128TB, the SLB addr_limit
> variable is not expanded if addr is not > 128TB, but the slice allocation
> looks at task_size, which is 512TB. This results in slice_check_fit()
> incorrectly
From: Desnes Augusto Nunes do Rosario
Date: Mon, 13 Nov 2017 15:59:19 -0200
> This patch implements and enables VDP support for the ibmvnic driver.
> Moreover, it includes the implementation of suitable structs, signal
> transmission/handling and functions which allows the retrival of firmware
>
From: Colin Ian King
Trivial fix to spelling mistake in pr_err error message text
Signed-off-by: Colin Ian King
---
drivers/crypto/nx/nx-842-powernv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/nx/nx-842-powernv.c
b/drivers/crypto/nx/nx-842-powernv.c
in
On Tue, 14 Nov 2017, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in pr_err error message text
>
> Signed-off-by: Colin Ian King
> ---
> drivers/crypto/nx/nx-842-powernv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/n
On Fri, Nov 10, 2017 at 11:42 PM, Deepa Dinamani wrote:
> The series is a preparation series for individual architectures
> to use 64 bit time_t syscalls in compat and 32 bit emulation modes.
>
> This is a follow up to the series Arnd Bergmann posted:
> https://sourceware.org/ml/libc-alpha/2015-05
From: Colin Ian King
Trivial fix to spelling mistake in pr_err error message text. Also
fix spelling mistake in proceeding comment.
Signed-off-by: Colin Ian King
---
drivers/crypto/nx/nx-842-powernv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/nx/nx-
On 14/11/17 13:45, Julia Lawall wrote:
>
>
> On Tue, 14 Nov 2017, Colin King wrote:
>
>> From: Colin Ian King
>>
>> Trivial fix to spelling mistake in pr_err error message text
>>
>> Signed-off-by: Colin Ian King
>> ---
>> drivers/crypto/nx/nx-842-powernv.c | 2 +-
>> 1 file changed, 1 insert
On Tue, 2017-11-14 at 10:04 +0100, Michal Hocko wrote:
> If there is a general consensus that this is the preferred way to go,
> I
> will post the patch as an RFC to linux-api
>
> [1] http://lkml.kernel.org/r/20171113160637.jhekbdyfpccme3be@dhcp22.s
> use.cz
I prefer the new flag. It is cleaner a
On 11/13/17 7:07 PM, Daniel Axtens wrote:
> Hi Bryant,
>
> A few things:
>
> 1) The commit message could probably be trimmed, especially the stack
> traces.
Yes, I can trim it.
> 2) What exactly are you changing and why does it fix the issue? I
> couldn't figure that out from the commit message
The following patch ensures that the bounce_buffer is not null
prior to using it within skb_copy_from_linear_data.
The problem can be recreated toggling on/off Large send offload.
The following script when run (along with some iperf traffic recreates the
crash within 5-10 mins or so).
while true
On Tue, Nov 14, 2017 at 03:59:21PM +0530, Naveen N. Rao wrote:
> Kamalesh Babulal wrote:
> > From: Josh Poimboeuf
> >
> > When attempting to load a livepatch module, I got the following error:
> >
> > module_64: patch_module: Expect noop after relocate, got 3c82
> >
> > The error was trig
Sorry for my mistake. Thanks.
Acked-by: Haren Myneni
On 11/14/2017 06:32 AM, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in pr_err error message text. Also
> fix spelling mistake in proceeding comment.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/cryp
On Tue, Nov 14, 2017 at 02:32:17PM +, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in pr_err error message text. Also
> fix spelling mistake in proceeding comment.
s/proceeding/preceding/ ?
>
> Signed-off-by: Colin Ian King
> ---
> drivers/crypto/nx/nx-842
From: Boqun Feng
Call the rseq_handle_notify_resume() function on return to userspace if
TIF_NOTIFY_RESUME thread flag is set.
Increment the event counter and perform fixup on the pre-signal when a
signal is delivered on top of a restartable sequence critical section.
Signed-off-by: Boqun Feng
From: Boqun Feng
Wire up the rseq system call on powerpc.
This provides an ABI improving the speed of a user-space getcpu
operation on powerpc by skipping the getcpu system call on the fast
path, as well as improving the speed of user-space operations on per-cpu
data compared to using load-reser
Signed-off-by: Mathieu Desnoyers
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Michael Ellerman
CC: Boqun Feng
CC: Peter Zijlstra
CC: "Paul E. McKenney"
CC: linuxppc-dev@lists.ozlabs.org
---
arch/powerpc/include/asm/systbl.h | 1 +
arch/powerpc/include/asm/unistd.h | 2 +-
arc
Allow PowerPC to skip the full memory barrier in switch_mm(), and
only issue the barrier when scheduling into a task belonging to a
process that has registered to use expedited private.
Threads targeting the same VM but which belong to different thread
groups is a tricky case. It has a few consequ
Hi all,
Commit
f23ab3efb1b3 ("powerpc: Fix DABR match on hash based systems")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
Hi Bryant,
This looks a bit better, but...
> The following patch ensures that the bounce_buffer is not null
> prior to using it within skb_copy_from_linear_data.
How would this occur?
Looking at ibmveth.c, I see bounce_buffer being freed in ibmveth_close()
and allocated in ibmveth_open() only.
Recently we added a CPU feature for Power9 DD2.0, to capture the fact
that some workarounds are required only on Power9 DD1 and DD2.0 but
not DD2.1 or later.
Then in commit 9d2f510a66ec ("powerpc/64s/idle: avoid POWER9 DD1 and
DD2.0 ERAT workaround on DD2.1") and commit e3646330cf66
"powerpc/64s/i
On Wed, 2017-11-15 at 13:47 +1100, Daniel Axtens wrote:
> Hi Bryant,
>
> This looks a bit better, but...
>
> > The following patch ensures that the bounce_buffer is not null
> > prior to using it within skb_copy_from_linear_data.
>
> How would this occur?
>
> Looking at ibmveth.c, I see bounce_
Hi Mathieu,
Today's linux-next merge of the rseq tree got a conflict in:
arch/powerpc/Kconfig
between commit:
32ce3862af3c ("powerpc/lib: Implement PMEM API")
from the powerpc tree and commit:
ba4b152f3f2f ("membarrier: powerpc: Skip memory barrier in switch_mm() (v7)")
from the rseq t
On Tuesday 14 November 2017 09:23 PM, Josh Poimboeuf wrote:
On Tue, Nov 14, 2017 at 03:59:21PM +0530, Naveen N. Rao wrote:
Kamalesh Babulal wrote:
From: Josh Poimboeuf
When attempting to load a livepatch module, I got the following error:
module_64: patch_module: Expect noop after relocate
58 matches
Mail list logo
