RE: [PATCH 2/3] kbuild: add real-prereqs shorthand for $(filter-out FORCE, $^)

Hi Alexey, > What is this series made on top of? This does not apply on top of master > from > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git If you want to apply this series cleanly, please apply the following first: https://patchwork.kernel.org/patch/10761625/ https://

Re: [PATCH] pseries/hotplug: Add more delay in pseries_cpu_die while waiting for rtas-stop

Hello Michael, On Mon, Jan 14, 2019 at 12:11:44PM -0600, Michael Bringmann wrote: > On 1/9/19 12:08 AM, Gautham R Shenoy wrote: > > > I did some testing during the holidays. Here are the observations: > > > > 1) With just your patch (without any additional debug patch), if I run > > DLPAR on /of

Re: [PATCH 2/3] kbuild: add real-prereqs shorthand for $(filter-out FORCE, $^)

On 17/01/2019 15:10, Masahiro Yamada wrote: > In Kbuild, if_changed and friends must have FORCE as a prerequisite. > > Hence, $(filter-out FORCE,$^) or $(filter-out $(PHONY),$^) is a common > pattern to get the names of all the prerequisites except phony targets. > > Add real-prereqs as a shor

[PATCH 2/3] kbuild: add real-prereqs shorthand for $(filter-out FORCE, $^)

In Kbuild, if_changed and friends must have FORCE as a prerequisite. Hence, $(filter-out FORCE,$^) or $(filter-out $(PHONY),$^) is a common pattern to get the names of all the prerequisites except phony targets. Add real-prereqs as a shorthand. Note: We cannot replace $(filter %.o,$^) in cmd_lin

Re: [RESENDING PATCH] powerpc/wii: properly disable use of BATs when requested.

Hi again, On Tue, Jan 15, 2019 at 04:43:20PM +, Christophe Leroy wrote: > 'nobats' kernel parameter or some options like CONFIG_DEBUG_PAGEALLOC > deny the use of BATS for mapping memory. > > This patch makes sure that the specific wii RAM mapping function > takes it into account as well. > >

Re: powerpc/syscalls: Fix syscall tracing

On Tue, 2019-01-15 at 06:37:28 UTC, Michael Ellerman wrote: > Recently in commit fbf508da7440 ("powerpc: split compat syscall table > out from native table") we changed the layout of the system call > table. Instead of having two entries for each syscall number, one for > the regular entry point an

Re: powerpc/4xx/ocm: Fix fix for phys_addr_t printf warnings

On Mon, 2019-01-14 at 00:32:55 UTC, Michael Ellerman wrote: > My recent commit to fix the printf warnings in ocm.c got the format > specifier wrong, because I copied it from the documentation without > realising the square brackets are not meant as literals. > > This results in the address being s

Re: powerpc: PCI does not require PowerNV

On Tue, 2019-01-15 at 00:47:45 UTC, "Jason A. Donenfeld" wrote: > Commit 0e759bd75285 moved around the declaration of pnv_npu2_init, but > did not conditionalize it inside of the PCI pSeries driver. This meant > that CONFIG_PCI && CONFIG_PPC_PSERIES && !CONFIG_PPC_POWERNV resulted > in: > > powerp

Re: [PATCH v2 00/15] powerpc/32s: Use BATs/LTLBs for STRICT_KERNEL_RWX

On Wed, Jan 16, 2019 at 02:34:53PM +0100, Christophe Leroy wrote: > Le 16/01/2019 à 14:16, Jonathan Neuschäfer a écrit : > > On Wed, Jan 16, 2019 at 07:55:29AM +0100, Christophe Leroy wrote: > > > Le 16/01/2019 à 01:35, Jonathan Neuschäfer a écrit : > > > > Thinning the kernel down a bit actually m

Re: [PATCH] powerpc/ps3: Use struct_size() in kzalloc()

Hi Geoff, On 1/16/19 11:21 AM, Geoff Levand wrote: Hi Gustavo, On 1/8/19 1:00 PM, Gustavo A. R. Silva wrote: One of the more common cases of allocation size calculations is finding the size of a structure that has a zero-sized array at the end, along with memory for some number of elements for

Re: [PATCH 15/21] sparc: add checks for the return value of memblock_alloc*()

From: Mike Rapoport Date: Wed, 16 Jan 2019 15:44:15 +0200 > Add panic() calls if memblock_alloc*() returns NULL. > > Most of the changes are simply addition of > > if(!ptr) > panic(); > > statements after the calls to memblock_alloc*() variants. > > Exceptions are pcpu

Re: [PATCH] powerpc/ps3: Use struct_size() in kzalloc()

Hi Gustavo, On 1/8/19 1:00 PM, Gustavo A. R. Silva wrote: > One of the more common cases of allocation size calculations is finding the > size of a structure that has a zero-sized array at the end, along with memory > for some number of elements for that array. For example: > > struct foo { >

[PATCH v3 2/2] powerpc: use probe_user_read()

Instead of opencoding, use probe_user_read() to failessly read a user location. Signed-off-by: Christophe Leroy --- v3: No change v2: Using probe_user_read() instead of probe_user_address() arch/powerpc/kernel/process.c | 12 +--- arch/powerpc/mm/fault.c | 6 +- arch/p

[PATCH v3 1/2] mm: add probe_user_read()

In powerpc code, there are several places implementing safe access to user data. This is sometimes implemented using probe_kernel_address() with additional access_ok() verification, sometimes with get_user() enclosed in a pagefault_disable()/enable() pair, etc. : show_user_instructions() ba

[PATCH] powerpc/tm: Avoid machine crash on rt_sigreturn

There is a kernel crash that happens if rt_sigreturn is called inside a transactional block. This crash happens if the kernel hits an in-kernel page fault when accessing userspace memory, usually through copy_ckvsx_to_user(). A major page fault calls might_sleep() function, which can cause a task

Re: [PATCH 19/21] treewide: add checks for the return value of memblock_alloc*()

On Wed, Jan 16, 2019 at 7:46 AM Mike Rapoport wrote: > > Add check for the return value of memblock_alloc*() functions and call > panic() in case of error. > The panic message repeats the one used by panicing memblock allocators with > adjustment of parameters to include only relevant ones. > > Th

Re: [PATCH 08/21] memblock: drop __memblock_alloc_base()

On Wed, Jan 16, 2019 at 7:45 AM Mike Rapoport wrote: > > The __memblock_alloc_base() function tries to allocate a memory up to the > limit specified by its max_addr parameter. Depending on the value of this > parameter, the __memblock_alloc_base() can is replaced with the appropriate > memblock_ph

Re: [PATCH 19/21] treewide: add checks for the return value of memblock_alloc*()

On Wed, Jan 16, 2019 at 03:27:35PM +0100, Geert Uytterhoeven wrote: > Hi Mike, > > On Wed, Jan 16, 2019 at 2:46 PM Mike Rapoport wrote: > > Add check for the return value of memblock_alloc*() functions and call > > panic() in case of error. > > The panic message repeats the one used by panicing m

Re: [alsa-devel] [PATCH v2 4/4] ASoC: add imx-audmix DT binding documentation

On Wed, Jan 16, 2019 at 2:22 AM Daniel Baluta wrote: > > On Tue, Jan 15, 2019 at 10:58 PM Rob Herring wrote: > > > > On Tue, Jan 08, 2019 at 01:05:51PM +, Viorel Suman wrote: > > > Add the DT binding documentation for Audio Mixer > > > machine driver. > > > > > > Signed-off-by: Viorel Suman

Re: [PATCH] kbuild: mark prepare0 as PHONY to fix external module build

On Tue, Jan 15, 2019 at 5:07 PM Masahiro Yamada wrote: > > Commit c3ff2a5193fa ("powerpc/32: add stack protector support") > caused kernel panic on PowerPC if an external module is used with > CONFIG_STACKPROTECTOR because the 'prepare' target was not executed > for the external module build. > >

Re: [Xen-devel] [PATCH 19/21] treewide: add checks for the return value of memblock_alloc*()

On 16/01/2019 14:44, Mike Rapoport wrote: > Add check for the return value of memblock_alloc*() functions and call > panic() in case of error. > The panic message repeats the one used by panicing memblock allocators with > adjustment of parameters to include only relevant ones. > > The replacement

Re: [PATCH 19/21] treewide: add checks for the return value of memblock_alloc*()

Hi Mike, On Wed, Jan 16, 2019 at 2:46 PM Mike Rapoport wrote: > Add check for the return value of memblock_alloc*() functions and call > panic() in case of error. > The panic message repeats the one used by panicing memblock allocators with > adjustment of parameters to include only relevant ones

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed, Jan 16, 2019 at 02:47:16PM +0100, Christophe Leroy wrote: > Le 16/01/2019 à 14:18, Matthew Wilcox a écrit : > > I disagree with your objective. Making more code common is a great idea, > > but this patch is too unambitious. We should be heading towards one or > > two page table allocation

Re: [PATCH 13/21] arch: don't memset(0) memory returned by memblock_alloc()

On Wed, Jan 16, 2019 at 2:45 PM Mike Rapoport wrote: > memblock_alloc() already clears the allocated memory, no point in doing it > twice. > > Signed-off-by: Mike Rapoport > arch/m68k/mm/mcfmmu.c | 1 - For m68k part: Acked-by: Geert Uytterhoeven > --- a/arch/m68k/mm/mcfmmu.c > +++ b/ar

Re: [RFC PATCH v2 5/5] powerpc/syscalls: Allow none instead of sys_ni_syscall

On Wed, Jan 16, 2019 at 2:27 PM Michael Ellerman wrote: > > sys_ni_syscall is the "not-implemented" syscall syscall, which just > returns -ENOSYS. > > But unless you know that it's not obvious what it does, and even if > you do know what it means it doesn't stand out that well from other > real sy

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

Le 16/01/2019 à 14:18, Matthew Wilcox a écrit : On Wed, Jan 16, 2019 at 06:42:22PM +0530, Anshuman Khandual wrote: On 01/16/2019 06:00 PM, Matthew Wilcox wrote: On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: All architecture

[PATCH 21/21] memblock: drop memblock_alloc_*_nopanic() variants

As all the memblock allocation functions return NULL in case of error rather than panic(), the duplicates with _nopanic suffix can be removed. Signed-off-by: Mike Rapoport --- arch/arc/kernel/unwind.c | 3 +-- arch/sh/mm/init.c | 2 +- arch/x86/kernel/setup_percpu.c | 10 +++

[PATCH 20/21] memblock: memblock_alloc_try_nid: don't panic

As all the memblock_alloc*() users are now checking the return value and panic() in case of error, the panic() call can be removed from the core memblock allocator, namely memblock_alloc_try_nid(). Signed-off-by: Mike Rapoport --- mm/memblock.c | 15 +-- 1 file changed, 5 insertions(

[PATCH 19/21] treewide: add checks for the return value of memblock_alloc*()

Add check for the return value of memblock_alloc*() functions and call panic() in case of error. The panic message repeats the one used by panicing memblock allocators with adjustment of parameters to include only relevant ones. The replacement was mostly automated with semantic patches like the o

[PATCH 18/21] swiotlb: add checks for the return value of memblock_alloc*()

Add panic() calls if memblock_alloc() returns NULL. The panic() format duplicates the one used by memblock itself and in order to avoid explosion with long parameters list replace open coded allocation size calculations with a local variable. Signed-off-by: Mike Rapoport --- kernel/dma/swiotlb.

[PATCH 17/21] init/main: add checks for the return value of memblock_alloc*()

Add panic() calls if memblock_alloc() returns NULL. The panic() format duplicates the one used by memblock itself and in order to avoid explosion with long parameters list replace open coded allocation size calculations with a local variable. Signed-off-by: Mike Rapoport --- init/main.c | 26 ++

[PATCH 16/21] mm/percpu: add checks for the return value of memblock_alloc*()

Add panic() calls if memblock_alloc() returns NULL. The panic() format duplicates the one used by memblock itself and in order to avoid explosion with long parameters list replace open coded allocation size calculations with a local variable. Signed-off-by: Mike Rapoport --- mm/percpu.c | 73 ++

[PATCH 14/21] ia64: add checks for the return value of memblock_alloc*()

Add panic() calls if memblock_alloc*() returns NULL. Most of the changes are simply addition of if(!ptr) panic(); statements after the calls to memblock_alloc*() variants. Exceptions are create_mem_map_page_table() and ia64_log_init() that were slightly refactored to acc

[PATCH 15/21] sparc: add checks for the return value of memblock_alloc*()

Add panic() calls if memblock_alloc*() returns NULL. Most of the changes are simply addition of if(!ptr) panic(); statements after the calls to memblock_alloc*() variants. Exceptions are pcpu_populate_pte() and kernel_map_range() that were slightly refactored to accommod

[PATCH 13/21] arch: don't memset(0) memory returned by memblock_alloc()

memblock_alloc() already clears the allocated memory, no point in doing it twice. Signed-off-by: Mike Rapoport --- arch/c6x/mm/init.c | 1 - arch/h8300/mm/init.c| 1 - arch/ia64/kernel/mca.c | 2 -- arch/m68k/mm/mcfmmu.c | 1 - arch/microblaze/mm/init.c | 6 ++

[PATCH 12/21] arch: use memblock_alloc() instead of memblock_alloc_from(size, align, 0)

The last parameter of memblock_alloc_from() is the lower limit for the memory allocation. When it is 0, the call is equivalent to memblock_alloc(). Signed-off-by: Mike Rapoport --- arch/alpha/kernel/core_cia.c | 2 +- arch/alpha/kernel/pci_iommu.c | 4 ++-- arch/alpha/kernel/setup.c | 2

[PATCH 11/21] memblock: make memblock_find_in_range_node() and choose_memblock_flags() static

These functions are not used outside memblock. Make them static. Signed-off-by: Mike Rapoport --- include/linux/memblock.h | 4 mm/memblock.c| 4 ++-- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/include/linux/memblock.h b/include/linux/memblock.h index cf4cd9c

[PATCH 10/21] memblock: refactor internal allocation functions

Currently, memblock has several internal functions with overlapping functionality. They all call memblock_find_in_range_node() to find free memory and then reserve the allocated range and mark it with kmemleak. However, there is difference in the allocation constraints and in fallback strategies.

[PATCH 09/21] memblock: drop memblock_alloc_base()

The memblock_alloc_base() function tries to allocate a memory up to the limit specified by its max_addr parameter and panics if the allocation fails. Replace its usage with memblock_phys_alloc_range() and make the callers check the return value and panic in case of error. Signed-off-by: Mike Rapop

[PATCH 08/21] memblock: drop __memblock_alloc_base()

The __memblock_alloc_base() function tries to allocate a memory up to the limit specified by its max_addr parameter. Depending on the value of this parameter, the __memblock_alloc_base() can is replaced with the appropriate memblock_phys_alloc*() variant. Signed-off-by: Mike Rapoport --- arch/sh

[PATCH 07/21] memblock: memblock_phys_alloc(): don't panic

Make the memblock_phys_alloc() function an inline wrapper for memblock_phys_alloc_range() and update the memblock_phys_alloc() callers to check the returned value and panic in case of error. Signed-off-by: Mike Rapoport --- arch/arm/mm/init.c | 4 arch/arm64/mm/mmu.c

[PATCH 06/21] memblock: memblock_phys_alloc_try_nid(): don't panic

The memblock_phys_alloc_try_nid() function tries to allocate memory from the requested node and then falls back to allocation from any node in the system. The memblock_alloc_base() fallback used by this function panics if the allocation fails. Replace the memblock_alloc_base() fallback with the di

[PATCH 05/21] memblock: emphasize that memblock_alloc_range() returns a physical address

Rename memblock_alloc_range() to memblock_phys_alloc_range() to emphasize that it returns a physical address. While on it, remove the 'enum memblock_flags' parameter from this function as its only user anyway sets it to MEMBLOCK_NONE, which is the default for the most of memblock allocations. Sign

[PATCH 04/21] memblock: drop memblock_alloc_base_nid()

The memblock_alloc_base_nid() is a oneliner wrapper for memblock_alloc_range_nid() without any side effect. Replace it's usage by the direct calls to memblock_alloc_range_nid(). Signed-off-by: Mike Rapoport --- include/linux/memblock.h | 3 --- mm/memblock.c| 15 --- 2 f

[PATCH 03/21] memblock: replace memblock_alloc_base(ANYWHERE) with memblock_phys_alloc

The calls to memblock_alloc_base(size, align, MEMBLOCK_ALLOC_ANYWHERE) and memblock_phys_alloc(size, align) are equivalent as both try to allocate 'size' bytes with 'align' alignment anywhere in the memory and panic if hte allocation fails. The conversion is done using the following semantic patch

[PATCH 02/21] powerpc: use memblock functions returning virtual address

From: Christophe Leroy Since only the virtual address of allocated blocks is used, lets use functions returning directly virtual address. Those functions have the advantage of also zeroing the block. [ MR: - updated error message in alloc_stack() to be more verbose - convereted several additi

[PATCH 01/21] openrisc: prefer memblock APIs returning virtual address

The allocation of the page tables memory in openrics uses memblock_phys_alloc() and then converts the returned physical address to virtual one. Use memblock_alloc_raw() and add a panic() if the allocation fails. Signed-off-by: Mike Rapoport --- arch/openrisc/mm/init.c | 5 - 1 file changed,

[PATCH 00/21] Refine memblock API

Hi, Current memblock API is quite extensive and, which is more annoying, duplicated. Except the low-level functions that allow searching for a free memory region and marking it as reserved, memblock provides three (well, two and a half) sets of functions to allocate memory. There are several overl

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed 16-01-19 18:57:13, Anshuman Khandual wrote: > > > On 01/16/2019 06:14 PM, Michal Hocko wrote: > > On Wed 16-01-19 04:30:18, Matthew Wilcox wrote: > >> On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > >>> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > All architect

Re: [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: e1c3743e1a20 powerpc/tm: Set MSR[TS] just prior to recheckpoint. The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93, v4.9.150. v4.20.2: Failed to apply! Possible d

Re: [PATCH v2 00/15] powerpc/32s: Use BATs/LTLBs for STRICT_KERNEL_RWX

Le 16/01/2019 à 14:16, Jonathan Neuschäfer a écrit : On Wed, Jan 16, 2019 at 07:55:29AM +0100, Christophe Leroy wrote: Le 16/01/2019 à 01:35, Jonathan Neuschäfer a écrit : Thinning the kernel down a bit actually makes it boot again. Ooops...! Maybe enabling CONFIG_STRICT_KERNEL_RWX has made

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed 16-01-19 05:18:27, Matthew Wilcox wrote: > On Wed, Jan 16, 2019 at 06:42:22PM +0530, Anshuman Khandual wrote: > > On 01/16/2019 06:00 PM, Matthew Wilcox wrote: > > > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > > >> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > > >>

[RFC PATCH v2 5/5] powerpc/syscalls: Allow none instead of sys_ni_syscall

sys_ni_syscall is the "not-implemented" syscall syscall, which just returns -ENOSYS. But unless you know that it's not obvious what it does, and even if you do know what it means it doesn't stand out that well from other real syscalls. So teach the scripts to treat "none" as a synonym for "sys_ni

[RFC PATCH v2 4/5] powerpc/syscalls: Split SPU-ness out of ABI

Using the ABI field to encode whether a syscall is usable by SPU programs or not is a bit of kludge. The ABI of the syscall doesn't change depending on the SPU-ness, but in order to make the syscall generation work we have to pretend that it does. It also means we have more duplicated syscall lin

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On 01/16/2019 06:14 PM, Michal Hocko wrote: > On Wed 16-01-19 04:30:18, Matthew Wilcox wrote: >> On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: >>> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | >

[RFC PATCH v2 3/5] powerpc/syscalls: Remove unused prefix parameter

We never pass a prefix so remove the logic for it. Signed-off-by: Michael Ellerman --- arch/powerpc/kernel/syscalls/Makefile | 3 +-- arch/powerpc/kernel/syscalls/syscallhdr.sh | 4 +--- 2 files changed, 2 insertions(+), 5 deletions(-) v2: No change. diff --git a/arch/powerpc/kernel/sysca

[RFC PATCH v2 1/5] powerpc/syscalls: Use the number when building SPU syscall table

Currently the macro that inserts entries into the SPU syscall table doesn't actually use the "nr" (syscall number) parameter. This does work, but it relies on the exact right number of syscall entries being emitted in order for the syscal numbers to line up with the array entries. If for example w

[RFC PATCH v2 2/5] powerpc/syscalls: Remove unused offset parameter

We never pass a value for offset, nor do we need to, so remove the offset logic. Signed-off-by: Michael Ellerman --- arch/powerpc/kernel/syscalls/Makefile | 6 ++ arch/powerpc/kernel/syscalls/syscallhdr.sh | 10 ++ arch/powerpc/kernel/syscalls/syscalltbl.sh | 8 ++-- 3 fil

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed, Jan 16, 2019 at 06:42:22PM +0530, Anshuman Khandual wrote: > On 01/16/2019 06:00 PM, Matthew Wilcox wrote: > > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > >> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > >>> All architectures have been defining their own PGALLOC_G

Re: [PATCH v2 00/15] powerpc/32s: Use BATs/LTLBs for STRICT_KERNEL_RWX

On Wed, Jan 16, 2019 at 07:55:29AM +0100, Christophe Leroy wrote: > Le 16/01/2019 à 01:35, Jonathan Neuschäfer a écrit : > > Thinning the kernel down a bit actually makes it boot again. Ooops...! > > Maybe enabling CONFIG_STRICT_KERNEL_RWX has made it just large enough to > > fail the hash table al

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On 01/16/2019 06:00 PM, Matthew Wilcox wrote: > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: >> On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: >>> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | >>> __GFP_ZERO) and using it for allocating page tab

Re: [RFC PATCH 1/5] powerpc/syscalls: Remove unused offset parameter

Arnd Bergmann writes: > On Wed, Jan 16, 2019 at 1:31 AM Michael Ellerman wrote: >> >> Arnd Bergmann writes: >> > On Mon, Jan 14, 2019 at 12:36 PM Michael Ellerman >> > wrote: >> >> >> >> We never pass a value for offset, nor do we need to, so remove the >> >> offset logic. >> >> >> >> Signed-o

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On 01/16/2019 12:25 PM, Mike Rapoport wrote: > On Wed, Jan 16, 2019 at 11:51:32AM +0530, Anshuman Khandual wrote: >> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | >> __GFP_ZERO) and using it for allocating page table pages. This causes some >> code duplication which

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed 16-01-19 04:30:18, Matthew Wilcox wrote: > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > > On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > > > All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL > > > | > > > __GFP_ZERO) and using it for allocati

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On 01/16/2019 12:40 PM, Christophe Leroy wrote: > > > Le 16/01/2019 à 07:21, Anshuman Khandual a écrit : >> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | >> __GFP_ZERO) and using it for allocating page table pages. This causes some >> code duplication which can be

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed, Jan 16, 2019 at 04:30:18AM -0800, Matthew Wilcox wrote: > On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > > On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > > > All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL > > > | > > > __GFP_ZERO) and using

Re: [PATCH V2] mm: Introduce GFP_PGTABLE

On Wed, Jan 16, 2019 at 07:57:03AM +0100, Michal Hocko wrote: > On Wed 16-01-19 11:51:32, Anshuman Khandual wrote: > > All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL | > > __GFP_ZERO) and using it for allocating page table pages. This causes some > > code duplication whic

Re: [RFC PATCH 1/5] powerpc/syscalls: Remove unused offset parameter

On Wed, Jan 16, 2019 at 1:31 AM Michael Ellerman wrote: > > Arnd Bergmann writes: > > On Mon, Jan 14, 2019 at 12:36 PM Michael Ellerman > > wrote: > >> > >> We never pass a value for offset, nor do we need to, so remove the > >> offset logic. > >> > >> Signed-off-by: Michael Ellerman > > > > T

[PATCH V5 5/5] arch/powerpc/mm/hugetlb: NestMMU workaround for hugetlb mprotect RW upgrade

NestMMU requires us to mark the pte invalid and flush the tlb when we do a RW upgrade of pte. We fixed a variant of this in the fault path in commit Fixes: bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang") Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/inclu

[PATCH V5 4/5] mm/hugetlb: Add prot_modify_start/commit sequence for hugetlb update

Architectures like ppc64 require to do a conditional tlb flush based on the old and new value of pte. Follow the regular pte change protection sequence for hugetlb too. This allows the architectures to override the update sequence. Signed-off-by: Aneesh Kumar K.V --- include/linux/hugetlb.h | 20

[PATCH V5 3/5] arch/powerpc/mm: Nest MMU workaround for mprotect RW upgrade.

NestMMU requires us to mark the pte invalid and flush the tlb when we do a RW upgrade of pte. We fixed a variant of this in the fault path in commit Fixes: bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang") Do the same for mprotect upgrades. Hugetlb is handled i

[PATCH V5 2/5] mm: update ptep_modify_prot_commit to take old pte value as arg

Architectures like ppc64 require to do a conditional tlb flush based on the old and new value of pte. Enable that by passing old pte value as the arg. Signed-off-by: Aneesh Kumar K.V --- arch/s390/include/asm/pgtable.h | 3 ++- arch/s390/mm/pgtable.c | 2 +- arch/x86/include/asm/paravir

[PATCH V5 1/5] mm: Update ptep_modify_prot_start/commit to take vm_area_struct as arg

Some architecture may want to call flush_tlb_range from these helpers. Signed-off-by: Aneesh Kumar K.V --- arch/s390/include/asm/pgtable.h | 4 ++-- arch/s390/mm/pgtable.c| 6 -- arch/x86/include/asm/paravirt.h | 11 ++- arch/x86/include/asm/paravirt_typ

[PATCH V5 0/5] NestMMU pte upgrade workaround for mprotect

We can upgrade pte access (R -> RW transition) via mprotect. We need to make sure we follow the recommended pte update sequence as outlined in commit bd5050e38aec ("powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang") for such updates. This patch series do that. Changes from V4:

Re: [alsa-devel] [PATCH v2 4/4] ASoC: add imx-audmix DT binding documentation

On Tue, Jan 15, 2019 at 10:58 PM Rob Herring wrote: > > On Tue, Jan 08, 2019 at 01:05:51PM +, Viorel Suman wrote: > > Add the DT binding documentation for Audio Mixer > > machine driver. > > > > Signed-off-by: Viorel Suman > > --- > > .../devicetree/bindings/sound/imx-audmix.txt | 24