[PATCH 20/20] arm64:ilp32: add ARM64_ILP32 to Kconfig

From: Andrew Pinski This patch adds the config option for ILP32. Signed-off-by: Andrew Pinski Signed-off-by: Philipp Tomsich Signed-off-by: Christoph Muellner

[PATCH 17/20] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext

From: Andrew Pinski ILP32 uses AARCH32 compat structures and syscall handlers for signals. But ILP32 struct rt_sigframe and ucontext differs from both LP64 and AARCH32. So some specific mechanism is needed to take care of it. Signed-off-by: Andrew Pinski

[PATCH 14/20] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

From: Andrew Pinski Add a separate syscall-table for ILP32, which dispatches either to native LP64 system call implementation or to compat-syscalls, as appropriate. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov

[PATCH 20/20] arm64:ilp32: add ARM64_ILP32 to Kconfig

From: Andrew Pinski This patch adds the config option for ILP32. Signed-off-by: Andrew Pinski Signed-off-by: Philipp Tomsich Signed-off-by: Christoph Muellner Signed-off-by: Yury Norov Reviewed-by: David Daney --- arch/arm64/Kconfig | 10 +- 1 file changed, 9 insertions(+), 1

[PATCH 17/20] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext

From: Andrew Pinski ILP32 uses AARCH32 compat structures and syscall handlers for signals. But ILP32 struct rt_sigframe and ucontext differs from both LP64 and AARCH32. So some specific mechanism is needed to take care of it. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov ---

[PATCH 14/20] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

From: Andrew Pinski Add a separate syscall-table for ILP32, which dispatches either to native LP64 system call implementation or to compat-syscalls, as appropriate. Signed-off-by: Andrew Pinski Signed-off-by: Yury Norov Signed-off-by: Bamvor Jian Zhang --- arch/arm64/include/asm/unistd.h

[PATCH 18/20] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

ILP32 has context-related structures different from both aarch32 and aarch64/lp64. In this patch compat_arch_ptrace() renamed to compat_a32_ptrace(), and compat_arch_ptrace() only makes choice between compat_a32_ptrace() and new compat_ilp32_ptrace() handler. compat_ilp32_ptrace() calls generic

[PATCH 18/20] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

ILP32 has context-related structures different from both aarch32 and aarch64/lp64. In this patch compat_arch_ptrace() renamed to compat_a32_ptrace(), and compat_arch_ptrace() only makes choice between compat_a32_ptrace() and new compat_ilp32_ptrace() handler. compat_ilp32_ptrace() calls generic

[PATCH 15/20] arm64: signal: share lp64 signal routines to ilp32

After that, it will be possible to reuse it in ilp32. Signed-off-by: Yury Norov Signed-off-by: Bamvor Jian Zhang --- arch/arm64/include/asm/signal_common.h | 33 arch/arm64/kernel/signal.c | 93

[PATCH 15/20] arm64: signal: share lp64 signal routines to ilp32

After that, it will be possible to reuse it in ilp32. Signed-off-by: Yury Norov Signed-off-by: Bamvor Jian Zhang --- arch/arm64/include/asm/signal_common.h | 33 arch/arm64/kernel/signal.c | 93 +- 2 files changed, 92 insertions(+), 34

Re: [PATCH 4/9] mm: remove unnecessary reclaimability check from NUMA balancing target

On Tue 28-02-17 16:40:02, Johannes Weiner wrote: > NUMA balancing already checks the watermarks of the target node to > decide whether it's a suitable balancing target. Whether the node is > reclaimable or not is irrelevant when we don't intend to reclaim. I guess the original intention was to

Re: [PATCH 4/9] mm: remove unnecessary reclaimability check from NUMA balancing target

On Tue 28-02-17 16:40:02, Johannes Weiner wrote: > NUMA balancing already checks the watermarks of the target node to > decide whether it's a suitable balancing target. Whether the node is > reclaimable or not is irrelevant when we don't intend to reclaim. I guess the original intention was to

[PATCH 12/20] arm64: ilp32: introduce binfmt_ilp32.c

Like binfmt_elf32.c, binfmt_ilp32.c is needed to handle ILP32 binaries Signed-off-by: Yury Norov Signed-off-by: Bamvor Jian Zhang --- arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/binfmt_ilp32.c | 85

[PATCH 12/20] arm64: ilp32: introduce binfmt_ilp32.c

Like binfmt_elf32.c, binfmt_ilp32.c is needed to handle ILP32 binaries Signed-off-by: Yury Norov Signed-off-by: Bamvor Jian Zhang --- arch/arm64/kernel/Makefile | 1 + arch/arm64/kernel/binfmt_ilp32.c | 85 2 files changed, 86 insertions(+)

[PATCH 11/20] arm64: introduce binfmt_elf32.c

As we support more than one compat formats, it looks more reasonable to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32 specific definitions there and make code more maintainable and readable. Signed-off-by: Yury Norov --- arch/arm64/Kconfig

[PATCH 11/20] arm64: introduce binfmt_elf32.c

As we support more than one compat formats, it looks more reasonable to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32 specific definitions there and make code more maintainable and readable. Signed-off-by: Yury Norov --- arch/arm64/Kconfig | 1 -

[PATCH 0/2] HID: allocation neatening and code size reduction

Joe Perches (2): HID: Use krealloc HID: Remove unnecessary OOM messages drivers/hid/hid-a4tech.c | 4 +--- drivers/hid/hid-apple.c | 4 +--- drivers/hid/hid-asus.c| 5 + drivers/hid/hid-core.c| 24 +++-

[PATCH 0/2] HID: allocation neatening and code size reduction

Joe Perches (2): HID: Use krealloc HID: Remove unnecessary OOM messages drivers/hid/hid-a4tech.c | 4 +--- drivers/hid/hid-apple.c | 4 +--- drivers/hid/hid-asus.c| 5 + drivers/hid/hid-core.c| 24 +++-

[PATCH 2/2] HID: Remove unnecessary OOM messages

Allocation failures from k.alloc and dev_k.alloc calls already have a generic stack dump and these additional logging messages just make the code larger and the allocations more likely to fail. Remove them. Signed-off-by: Joe Perches --- drivers/hid/hid-a4tech.c | 4

[PATCH 2/2] HID: Remove unnecessary OOM messages

Allocation failures from k.alloc and dev_k.alloc calls already have a generic stack dump and these additional logging messages just make the code larger and the allocations more likely to fail. Remove them. Signed-off-by: Joe Perches --- drivers/hid/hid-a4tech.c | 4 +---

Re: rsync: page allocation stalls in kernel 4.9.10 to a VessRAID NAS

On Wed 01-03-17 13:06:57, Robert Kudyba wrote: [...] > Does this ever finish? Once there is no memory pressure > The output file seems to grow really quickly. Here are a few lines and > I can upload the file somewhere if you think it’d be helpful: [...] > kswapd0-52[001]

Re: rsync: page allocation stalls in kernel 4.9.10 to a VessRAID NAS

On Wed 01-03-17 13:06:57, Robert Kudyba wrote: [...] > Does this ever finish? Once there is no memory pressure > The output file seems to grow really quickly. Here are a few lines and > I can upload the file somewhere if you think it’d be helpful: [...] > kswapd0-52[001]

net/sctp: use-after-free in sctp_association_put

Hello, I've got the following report while running syzkaller fuzzer on linux-next/8813198236a044b76e251dcae937b180dd527999: BUG: KASAN: use-after-free in sctp_association_destroy net/sctp/associola.c:416 [inline] at addr 8801c0fa415c BUG: KASAN: use-after-free in

net/sctp: use-after-free in sctp_association_put

Hello, I've got the following report while running syzkaller fuzzer on linux-next/8813198236a044b76e251dcae937b180dd527999: BUG: KASAN: use-after-free in sctp_association_destroy net/sctp/associola.c:416 [inline] at addr 8801c0fa415c BUG: KASAN: use-after-free in

Re: [PATCH 6/9] mm: don't avoid high-priority reclaim on memcg limit reclaim

On Wed 01-03-17 12:36:28, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 04:40:27PM +0100, Michal Hocko wrote: > > On Tue 28-02-17 16:40:04, Johannes Weiner wrote: > > > 246e87a93934 ("memcg: fix get_scan_count() for small targets") sought > > > to avoid high reclaim priorities for memcg by

[PATCH 2/2] efi: arm: Fix boot crash with CONFIG_CPUMASK_OFFSTACK=y

On ARM and arm64, we use a dedicated mm_struct to map the UEFI Runtime Services regions, which allows us to map those regions on demand, and in a way that is guaranteed to be compatible with incoming kernels across kexec. As it turns out, we don't fully initialize the mm_struct in the same way as

Re: [PATCH 6/9] mm: don't avoid high-priority reclaim on memcg limit reclaim

On Wed 01-03-17 12:36:28, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 04:40:27PM +0100, Michal Hocko wrote: > > On Tue 28-02-17 16:40:04, Johannes Weiner wrote: > > > 246e87a93934 ("memcg: fix get_scan_count() for small targets") sought > > > to avoid high reclaim priorities for memcg by

[PATCH 2/2] efi: arm: Fix boot crash with CONFIG_CPUMASK_OFFSTACK=y

On ARM and arm64, we use a dedicated mm_struct to map the UEFI Runtime Services regions, which allows us to map those regions on demand, and in a way that is guaranteed to be compatible with incoming kernels across kexec. As it turns out, we don't fully initialize the mm_struct in the same way as

[GIT PULL 0/2] EFI fixes for v4.11-rc

The following changes since commit 6053dc981449718d90a429933e99b441e1adaea6: Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2017-03-01 10:32:30 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git

[GIT PULL 0/2] EFI fixes for v4.11-rc

The following changes since commit 6053dc981449718d90a429933e99b441e1adaea6: Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2017-03-01 10:32:30 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git

[PATCH v14 5/5] mfd: Move binding document

The bindings, which are now used in MFD, need also to be documented in the MFD binding document. Signed-off-by: Ksenija Stanojevic Reviewed-by: Marek Vasut Acked-by: Lee Jones --- Changes in v14: - none Changes in v13: -

[PATCH v14 5/5] mfd: Move binding document

The bindings, which are now used in MFD, need also to be documented in the MFD binding document. Signed-off-by: Ksenija Stanojevic Reviewed-by: Marek Vasut Acked-by: Lee Jones --- Changes in v14: - none Changes in v13: - none Changes in v12: - none Changes in v11: - none Changes in

[PATCH 1/2] efi: libstub: Treat missing SecureBoot variable as S/B disabled

The newly refactored code that infers the firmware's Secure Boot state prints the following error when the EFI variable 'SecureBoot' does not exist: EFI stub: ERROR: Could not determine UEFI Secure Boot status. However, this variable is only guaranteed to be defined on a system that is Secure

[PATCH 1/2] efi: libstub: Treat missing SecureBoot variable as S/B disabled

The newly refactored code that infers the firmware's Secure Boot state prints the following error when the EFI variable 'SecureBoot' does not exist: EFI stub: ERROR: Could not determine UEFI Secure Boot status. However, this variable is only guaranteed to be defined on a system that is Secure

Re: [PATCH v2 4/5] perf: kretprobes: offset from reloc_sym if kernel supports it

On 2017/02/25 08:55AM, Masami Hiramatsu wrote: > On Fri, 24 Feb 2017 17:11:03 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Sat, Feb 25, 2017 at 02:29:17AM +0900, Masami Hiramatsu escreveu: > > > On Fri, 24 Feb 2017 00:46:08 +0530 > > > "Naveen N. Rao"

Re: [PATCH v2 4/5] perf: kretprobes: offset from reloc_sym if kernel supports it

On 2017/02/25 08:55AM, Masami Hiramatsu wrote: > On Fri, 24 Feb 2017 17:11:03 -0300 > Arnaldo Carvalho de Melo wrote: > > > Em Sat, Feb 25, 2017 at 02:29:17AM +0900, Masami Hiramatsu escreveu: > > > On Fri, 24 Feb 2017 00:46:08 +0530 > > > "Naveen N. Rao" wrote: > > > > Thanks. I hope that's an

Re: [PATCH v2] ARM: OMAP2+: Fix device node reference counts

* Guenter Roeck [170228 11:55]: > After commit 'of: fix of_node leak caused in of_find_node_opts_by_path', > the following error may be reported when running omap images. > > OF: ERROR: Bad of_node_put() on /ocp@6800 > CPU: 0 PID: 0 Comm: swapper Not tainted

Re: [PATCH v2] ARM: OMAP2+: Fix device node reference counts

* Guenter Roeck [170228 11:55]: > After commit 'of: fix of_node leak caused in of_find_node_opts_by_path', > the following error may be reported when running omap images. > > OF: ERROR: Bad of_node_put() on /ocp@6800 > CPU: 0 PID: 0 Comm: swapper Not tainted 4.10.0-rc7-next-20170210 #1 >

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

Hi Guenter, Tobias and Sandra, thanks for your effort here. On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote: > On Tue, Feb 28, 2017 at 10:53:56AM -0700, Sandra Loosemore wrote: > > On 02/28/2017 08:53 AM, Tobias Klauser wrote: > > >(adding Sandra Loosemore to Cc due to possible

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

Hi Guenter, Tobias and Sandra, thanks for your effort here. On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote: > On Tue, Feb 28, 2017 at 10:53:56AM -0700, Sandra Loosemore wrote: > > On 02/28/2017 08:53 AM, Tobias Klauser wrote: > > >(adding Sandra Loosemore to Cc due to possible

Re: [GIT PULL] HID for 4.11

On Wed, Mar 1, 2017 at 1:03 AM, Benjamin Tissoires wrote: > > As Peter mentioned in the bug, there is a missing property on the kernel > node (INPUT_PROP_BUTTONPAD). > > The thing is this property is solely driven in the current driver by the > provided

Re: [GIT PULL] HID for 4.11

On Wed, Mar 1, 2017 at 1:03 AM, Benjamin Tissoires wrote: > > As Peter mentioned in the bug, there is a missing property on the kernel > node (INPUT_PROP_BUTTONPAD). > > The thing is this property is solely driven in the current driver by the > provided platform_data, so there is no way we ever

Re: [PATCH v2 1/1] serial: 8250_dw: Allow hardware flow control to be used

On Wed, 2017-03-01 at 18:02 +, James Hogan wrote: > On 11 January 2017 at 19:48, Jason Uy wrote: > > In the most common use case, the Synopsys DW UART driver does not > > set the set_termios callback function.  This prevents UPSTAT_AUTOCTS > > from being set when the

Re: [PATCH v2 1/1] serial: 8250_dw: Allow hardware flow control to be used

On Wed, 2017-03-01 at 18:02 +, James Hogan wrote: > On 11 January 2017 at 19:48, Jason Uy wrote: > > In the most common use case, the Synopsys DW UART driver does not > > set the set_termios callback function.  This prevents UPSTAT_AUTOCTS > > from being set when the UART flag CRTSCTS is set. 

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Wed 01-03-17 13:31:49, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 02:36:24PM +0100, Michal Hocko wrote: > > On Fri 24-02-17 13:31:49, Shaohua Li wrote: > > > show MADV_FREE pages info of each vma in smaps. The interface is for > > > diganose or monitoring purpose, userspace could use it

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Wed 01-03-17 13:31:49, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 02:36:24PM +0100, Michal Hocko wrote: > > On Fri 24-02-17 13:31:49, Shaohua Li wrote: > > > show MADV_FREE pages info of each vma in smaps. The interface is for > > > diganose or monitoring purpose, userspace could use it

[PATCH 1/2 RESEND] drm/vc4: Fulfill user BO creation requests from the kernel BO cache.

The from_cache flag was actually "the BO is invisible to userspace", so we can repurpose it to just zero out a cached BO and return it to userspace. Improves wall time for a loop of 5 glsl-algebraic-add-add-1 by -1.44989% +/- 0.862891% (n=28, 1 outlier removed from each that appeared to be other

[PATCH 2/2 RESEND] drm/vc4: Fix OOPSes from trying to cache a partially constructed BO.

If a CMA allocation failed, the partially constructed BO would be unreferenced through the normal path, and we might choose to put it in the BO cache. If we then reused it before it expired from the cache, the kernel would OOPS. Signed-off-by: Eric Anholt Fixes: c826a6e10644

[PATCH 1/2 RESEND] drm/vc4: Fulfill user BO creation requests from the kernel BO cache.

The from_cache flag was actually "the BO is invisible to userspace", so we can repurpose it to just zero out a cached BO and return it to userspace. Improves wall time for a loop of 5 glsl-algebraic-add-add-1 by -1.44989% +/- 0.862891% (n=28, 1 outlier removed from each that appeared to be other

[PATCH 2/2 RESEND] drm/vc4: Fix OOPSes from trying to cache a partially constructed BO.

If a CMA allocation failed, the partially constructed BO would be unreferenced through the normal path, and we might choose to put it in the BO cache. If we then reused it before it expired from the cache, the kernel would OOPS. Signed-off-by: Eric Anholt Fixes: c826a6e10644 ("drm/vc4: Add a BO

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

On Wed, Mar 01, 2017 at 11:08:52AM -0700, Shuah Khan wrote: > On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > >> Current CMA size of 64 Mbytes is right on the edge of being small when > >> several drivers need to allocate large

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

On Wed, Mar 01, 2017 at 11:08:52AM -0700, Shuah Khan wrote: > On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: > >> Current CMA size of 64 Mbytes is right on the edge of being small when > >> several drivers need to allocate large

fs: use-after-free in userfaultfd_exit

Hello, I've got the following use-after-free report while running syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760: == BUG: KASAN: use-after-free in userfaultfd_exit+0x251/0x270 fs/userfaultfd.c:803 at addr

fs: use-after-free in userfaultfd_exit

Hello, I've got the following use-after-free report while running syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760: == BUG: KASAN: use-after-free in userfaultfd_exit+0x251/0x270 fs/userfaultfd.c:803 at addr

v4.11-rc0: Chromium crashes due to data ulimit

Hi! I got this today: [ 841.056790] mmap: chromium (4142): VmData 2161451008 exceed data ulimit 2147483647. Update limits or use boot option ignore_rlimit_data. Normally chromium works well for me... but I only got x220 few days ago. 32-bit kernel on 6GiB 64-bit thinkpad X220... In shell, I

v4.11-rc0: Chromium crashes due to data ulimit

Hi! I got this today: [ 841.056790] mmap: chromium (4142): VmData 2161451008 exceed data ulimit 2147483647. Update limits or use boot option ignore_rlimit_data. Normally chromium works well for me... but I only got x220 few days ago. 32-bit kernel on 6GiB 64-bit thinkpad X220... In shell, I

Re: Passionate Partner

Dear Sir, Did you recieved my mail? I have sent it twice without a response. Mr Masella Giuseppe

Re: Passionate Partner

Dear Sir, Did you recieved my mail? I have sent it twice without a response. Mr Masella Giuseppe

[PATCH fixes v3] pinctrl: Really force states during suspend/resume

In case a platform only defaults a "default" set of pins, but not a "sleep" set of pins, and this particular platform suspends and resumes in a way that the pin states are not preserved by the hardware, when we resume, we would call pinctrl_single_resume() -> pinctrl_force_default() ->

[PATCH fixes v3] pinctrl: Really force states during suspend/resume

In case a platform only defaults a "default" set of pins, but not a "sleep" set of pins, and this particular platform suspends and resumes in a way that the pin states are not preserved by the hardware, when we resume, we would call pinctrl_single_resume() -> pinctrl_force_default() ->

Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param

On 2017-02-27 19:24, Martin K. Petersen wrote: "Michal" == Potomski, MichalX writes: Michal> Since in UFS 2.1 specification some of the descriptor lengths Michal> differs from 2.0 specification and some devices, which are Michal> reporting spec version 2.0 have

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-01 10:44+0100, Dmitry Vyukov: > On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >>> Hello, >>> >>> The following program triggers WARNING in nested_vmx_vmexit: >>>

Re: kvm: WARNING in nested_vmx_vmexit

2017-03-01 10:44+0100, Dmitry Vyukov: > On Wed, Mar 1, 2017 at 7:13 AM, Wanpeng Li wrote: >> 2017-02-28 20:15 GMT+08:00 Dmitry Vyukov : >>> Hello, >>> >>> The following program triggers WARNING in nested_vmx_vmexit: >>>

Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param

On 2017-02-27 19:24, Martin K. Petersen wrote: "Michal" == Potomski, MichalX writes: Michal> Since in UFS 2.1 specification some of the descriptor lengths Michal> differs from 2.0 specification and some devices, which are Michal> reporting spec version 2.0 have different descriptor lengths we

[PATCH v14 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

Add core files for low resolution analog-to-digital converter (mxs-lradc) MFD driver. Signed-off-by: Ksenija Stanojevic Acked-by: Lee Jones --- Changes in v14: - none Changes in v13: - none Changes in v12: - use BIT macro Changes in v11:

[PATCH v14 1/5] mfd: mxs-lradc: Add support for mxs-lradc MFD

Add core files for low resolution analog-to-digital converter (mxs-lradc) MFD driver. Signed-off-by: Ksenija Stanojevic Acked-by: Lee Jones --- Changes in v14: - none Changes in v13: - none Changes in v12: - use BIT macro Changes in v11: - create static struct mfd_cells - don't set

Re: [PATCH] Input: sparse-keymap - add managed version of sparse_keymap_setup()

On Wed, Mar 01, 2017 at 11:37:14AM +0100, Michał Kępień wrote: > > On Tue, Feb 28, 2017 at 10:45:25AM +0100, Michał Kępień wrote: > > > Some platform drivers use devm_input_allocate_device() together with > > > sparse_keymap_setup() in their .probe callbacks. While using the former > > >

Re: [PATCH] Input: sparse-keymap - add managed version of sparse_keymap_setup()

On Wed, Mar 01, 2017 at 11:37:14AM +0100, Michał Kępień wrote: > > On Tue, Feb 28, 2017 at 10:45:25AM +0100, Michał Kępień wrote: > > > Some platform drivers use devm_input_allocate_device() together with > > > sparse_keymap_setup() in their .probe callbacks. While using the former > > >

[PATCH v2 5/5] MIPS: microMIPS: Fix decoding of swsp16 instruction

When the immediate encoded in the instruction is accessed, it is sign extended due to being a signed value being assigned to a signed integer. The ISA specifies that this operation is an unsigned operation. The sign extension leads us to incorrectly decode: 801e9c8e: cbf1sw

[PATCH v2 5/5] MIPS: microMIPS: Fix decoding of swsp16 instruction

When the immediate encoded in the instruction is accessed, it is sign extended due to being a signed value being assigned to a signed integer. The ISA specifies that this operation is an unsigned operation. The sign extension leads us to incorrectly decode: 801e9c8e: cbf1sw

Re: [PATCH/RFC] arm64: pmu: add Qualcomm Technologies extensions

Hi Neil, On Wed, Mar 01, 2017 at 11:18:05AM -0500, Neil Leeder wrote: > Adds CPU PMU perf events support for Qualcomm Technologies' Falkor CPU. > > The Qualcomm Technologies CPU PMU is named qcom_pmuv3 and provides > extensions to the architected PMU events. Is this is a strict superset of

Re: [PATCH/RFC] arm64: pmu: add Qualcomm Technologies extensions

Hi Neil, On Wed, Mar 01, 2017 at 11:18:05AM -0500, Neil Leeder wrote: > Adds CPU PMU perf events support for Qualcomm Technologies' Falkor CPU. > > The Qualcomm Technologies CPU PMU is named qcom_pmuv3 and provides > extensions to the architected PMU events. Is this is a strict superset of

Re: [PATCH fixes v2] pinctrl: Really force states during suspend/resume

On 02/27/2017 03:06 PM, Florian Fainelli wrote: > In case a platform only defaults a "default" set of pins, but not a > "sleep" set of pins, and this particular platform suspends and resumes > in a way that the pin states are not preserved by the hardware, when we > resume, we would call

Re: [PATCH fixes v2] pinctrl: Really force states during suspend/resume

On 02/27/2017 03:06 PM, Florian Fainelli wrote: > In case a platform only defaults a "default" set of pins, but not a > "sleep" set of pins, and this particular platform suspends and resumes > in a way that the pin states are not preserved by the hardware, when we > resume, we would call

Re: [PATCH 6/9] mm: don't avoid high-priority reclaim on memcg limit reclaim

On Wed, Mar 01, 2017 at 04:40:27PM +0100, Michal Hocko wrote: > On Tue 28-02-17 16:40:04, Johannes Weiner wrote: > > 246e87a93934 ("memcg: fix get_scan_count() for small targets") sought > > to avoid high reclaim priorities for memcg by forcing it to scan a > > minimum amount of pages when

Re: [PATCH 6/9] mm: don't avoid high-priority reclaim on memcg limit reclaim

On Wed, Mar 01, 2017 at 04:40:27PM +0100, Michal Hocko wrote: > On Tue 28-02-17 16:40:04, Johannes Weiner wrote: > > 246e87a93934 ("memcg: fix get_scan_count() for small targets") sought > > to avoid high reclaim priorities for memcg by forcing it to scan a > > minimum amount of pages when

[RFC v0 0/2] Introduce on-chip interconnect API

Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point

[RFC v0 0/2] Introduce on-chip interconnect API

Modern SoCs have multiple processors and various dedicated cores (video, gpu, graphics, modem). These cores are talking to each other and can generate a lot of data flowing through the on-chip interconnects. These interconnect buses could form different topologies such as crossbar, point to point

[RFC v0 1/2] interconnect: Add generic interconnect controller API

This patch introduce a new API to get the requirement and configure the interconnect buses across the entire chipset to fit with the current demand. The API is using a consumer/provider-based model, where the providers are the interconnect controllers and the consumers could be various drivers.

[RFC v0 1/2] interconnect: Add generic interconnect controller API

This patch introduce a new API to get the requirement and configure the interconnect buses across the entire chipset to fit with the current demand. The API is using a consumer/provider-based model, where the providers are the interconnect controllers and the consumers could be various drivers.

[RFC v0 2/2] interconnect: Add Qualcomm msm8916 interconnect provider driver

Add driver for the Qualcomm interconnect controllers found in msm8916 based platforms. Signed-off-by: Georgi Djakov --- drivers/interconnect/Kconfig | 1 + drivers/interconnect/Makefile| 2 + drivers/interconnect/qcom/Kconfig

[RFC v0 2/2] interconnect: Add Qualcomm msm8916 interconnect provider driver

Add driver for the Qualcomm interconnect controllers found in msm8916 based platforms. Signed-off-by: Georgi Djakov --- drivers/interconnect/Kconfig | 1 + drivers/interconnect/Makefile| 2 + drivers/interconnect/qcom/Kconfig| 11 +

[PATCH v2] objtool, module: discard objtool annotation sections for modules

The '__unreachable' and '__func_stack_frame_non_standard' sections are only used at compile time. They're discarded for vmlinux but they should also be discarded for modules. Since this is a recurring pattern, prefix the section names with ".discard.". It's a nice convention and vmlinux.lds.h

[PATCH v2] objtool, module: discard objtool annotation sections for modules

The '__unreachable' and '__func_stack_frame_non_standard' sections are only used at compile time. They're discarded for vmlinux but they should also be discarded for modules. Since this is a recurring pattern, prefix the section names with ".discard.". It's a nice convention and vmlinux.lds.h

Re: [PATCH] hid: usbhid: usbkbd: fix checkpatch.pl issues

Hi Avraham, On Tue, Feb 21, 2017 at 07:26:50PM +0200, Avraham Shukron wrote: > - Broke long lines > - Added spaces where needed > - Removed unnecessary / trailing whitespaces > - Extracted assignments outside of 'if' statements > > Signed-off-by: Avraham Shukron > ---

Re: [PATCH] hid: usbhid: usbkbd: fix checkpatch.pl issues

Hi Avraham, On Tue, Feb 21, 2017 at 07:26:50PM +0200, Avraham Shukron wrote: > - Broke long lines > - Added spaces where needed > - Removed unnecessary / trailing whitespaces > - Extracted assignments outside of 'if' statements > > Signed-off-by: Avraham Shukron > --- >

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: >> Current CMA size of 64 Mbytes is right on the edge of being small when >> several drivers need to allocate large CMA buffers. >> >> For example, if the s5p-mfc driver needs to

Re: [PATCH v2] ARM: exynos_defconfig: increase CONFIG_CMA_SIZE_MBYTES to 96

On 03/01/2017 10:09 AM, Krzysztof Kozlowski wrote: > On Tue, Feb 28, 2017 at 12:12:21PM -0700, Shuah Khan wrote: >> Current CMA size of 64 Mbytes is right on the edge of being small when >> several drivers need to allocate large CMA buffers. >> >> For example, if the s5p-mfc driver needs to

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

Re: gcc7 log2 compile issues in kernel/time/timekeeping.c

On 1 March 2017 at 00:00, Laura Abbott wrote: > On 02/25/2017 03:50 AM, Ard Biesheuvel wrote: >> >> >>> On 25 Feb 2017, at 11:23, Ard Biesheuvel wrote: >>> >>> On 25 February 2017 at 11:09, Markus Trippelsdorf >>> wrote:

Re: gcc7 log2 compile issues in kernel/time/timekeeping.c

On 1 March 2017 at 00:00, Laura Abbott wrote: > On 02/25/2017 03:50 AM, Ard Biesheuvel wrote: >> >> >>> On 25 Feb 2017, at 11:23, Ard Biesheuvel wrote: >>> >>> On 25 February 2017 at 11:09, Markus Trippelsdorf >>> wrote: On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote: >> On 25

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Wed, Mar 01, 2017 at 02:36:24PM +0100, Michal Hocko wrote: > On Fri 24-02-17 13:31:49, Shaohua Li wrote: > > show MADV_FREE pages info of each vma in smaps. The interface is for > > diganose or monitoring purpose, userspace could use it to understand > > what happens in the application. Since

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Wed, Mar 01, 2017 at 02:36:24PM +0100, Michal Hocko wrote: > On Fri 24-02-17 13:31:49, Shaohua Li wrote: > > show MADV_FREE pages info of each vma in smaps. The interface is for > > diganose or monitoring purpose, userspace could use it to understand > > what happens in the application. Since

Re: [GIT PULL] HID for 4.11

Hi Benjamin, On Wed, Mar 01, 2017 at 10:06:35AM +0100, Benjamin Tissoires wrote: > [I forgot to add Dmitry in the loop, sorry for the noise.] > > On Mar 01 2017 or thereabouts, Benjamin Tissoires wrote: > > On Feb 28 2017 or thereabouts, Linus Torvalds wrote: > > > On Tue, Feb 28, 2017 at 7:24

Re: [GIT PULL] HID for 4.11

Hi Benjamin, On Wed, Mar 01, 2017 at 10:06:35AM +0100, Benjamin Tissoires wrote: > [I forgot to add Dmitry in the loop, sorry for the noise.] > > On Mar 01 2017 or thereabouts, Benjamin Tissoires wrote: > > On Feb 28 2017 or thereabouts, Linus Torvalds wrote: > > > On Tue, Feb 28, 2017 at 7:24

Re: [PATCH 2/2] iproute2: add support for invisible qdisc dumping

On Sat, 25 Feb 2017 22:29:17 +0100 (CET) Jiri Kosina wrote: > From: Jiri Kosina > > Support the new TCA_DUMP_INVISIBLE netlink attribute that allows asking > kernel to perform 'full qdisc dump', as for historical reasons some of the > default qdiscs are

Re: [PATCH 2/2] iproute2: add support for invisible qdisc dumping

On Sat, 25 Feb 2017 22:29:17 +0100 (CET) Jiri Kosina wrote: > From: Jiri Kosina > > Support the new TCA_DUMP_INVISIBLE netlink attribute that allows asking > kernel to perform 'full qdisc dump', as for historical reasons some of the > default qdiscs are being hidden by the kernel. > > The

Re: [PATCH v3 2/7] mmc: bcm2835: Add new driver for the sdhost controller.

Gerd Hoffmann writes: > From: Eric Anholt > > The 2835 has two SD controllers: The Arasan sdhci controller (supported > by the iproc driver) and a custom sdhost controller. This patch adds a > driver for the latter. > > The sdhci controller supports both

Re: [PATCH v3 2/7] mmc: bcm2835: Add new driver for the sdhost controller.

Gerd Hoffmann writes: > From: Eric Anholt > > The 2835 has two SD controllers: The Arasan sdhci controller (supported > by the iproc driver) and a custom sdhost controller. This patch adds a > driver for the latter. > > The sdhci controller supports both sdcard and sdio. The sdhost >

<    3   4   5   6   7   8   9   10   11   12   >