linux-next: Tree for May 9

Hi all, Changes since 20160506: Dropped tree: hsi (at the maintainer's request) The f2fs tree gained a conflict against the ext4 tree. The libata tree gained a build failure so I used the version from next-20160506 for today. The net-next tree gained conflicts against the wireless-drivers and

linux-next: Tree for May 9

Hi all, Changes since 20160506: Dropped tree: hsi (at the maintainer's request) The f2fs tree gained a conflict against the ext4 tree. The libata tree gained a build failure so I used the version from next-20160506 for today. The net-next tree gained conflicts against the wireless-drivers and

Re: [PATCH v2 1/2] mm, kasan: improve double-free detection

On Sun, May 8, 2016 at 11:17 AM, Yury Norov wrote: > On Sat, May 07, 2016 at 03:15:59PM +, Luruo, Kuthonuzo wrote: >> Thank you for the review! >> >> > > + switch (alloc_data.state) { >> > > + case KASAN_STATE_QUARANTINE: >> > > + case KASAN_STATE_FREE: >> > > +

Re: [PATCH v2 1/2] mm, kasan: improve double-free detection

On Sun, May 8, 2016 at 11:17 AM, Yury Norov wrote: > On Sat, May 07, 2016 at 03:15:59PM +, Luruo, Kuthonuzo wrote: >> Thank you for the review! >> >> > > + switch (alloc_data.state) { >> > > + case KASAN_STATE_QUARANTINE: >> > > + case KASAN_STATE_FREE: >> > > + kasan_report((unsigned

Re: [PATCH v7 7/9] clk: mediatek: Enable critical clocks for MT2701

Hi Stephen, On Fri, 2016-05-06 at 16:12 -0700, Stephen Boyd wrote: > On 04/14, James Liao wrote: > > Some system clocks should be turned on by default on MT2701. > > This patch enable these clocks when related clocks have > > been registered. > > > > Signed-off-by: James Liao

Re: [PATCH v7 7/9] clk: mediatek: Enable critical clocks for MT2701

Hi Stephen, On Fri, 2016-05-06 at 16:12 -0700, Stephen Boyd wrote: > On 04/14, James Liao wrote: > > Some system clocks should be turned on by default on MT2701. > > This patch enable these clocks when related clocks have > > been registered. > > > > Signed-off-by: James Liao > > --- > >

Re: [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16()

On 5/9/16, Stephen Rothwell wrote: > Hi Josh, > > On Fri, 6 May 2016 09:22:25 -0500 Josh Poimboeuf > wrote: >> >> I've also seen no problems on powerpc with 4.4 and 4.8. I suspect it's >> specific to gcc 4.6. Stephen, can you confirm this patch fixes

Re: [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16()

On 5/9/16, Stephen Rothwell wrote: > Hi Josh, > > On Fri, 6 May 2016 09:22:25 -0500 Josh Poimboeuf > wrote: >> >> I've also seen no problems on powerpc with 4.4 and 4.8. I suspect it's >> specific to gcc 4.6. Stephen, can you confirm this patch fixes it? > > That will obviously fix the problem

Re: [PATCH 0/6] Intel Secure Guard Extensions

On Fri, May 06, 2016 at 01:54:14PM +0200, Thomas Gleixner wrote: > On Fri, 6 May 2016, Jarkko Sakkinen wrote: > > > On Tue, May 03, 2016 at 04:06:27AM -0500, Dr. Greg Wettstein wrote: > > > It would be helpful and instructive for anyone involved in this debate > > > to review the following URL

Re: [PATCH 0/6] Intel Secure Guard Extensions

On Fri, May 06, 2016 at 01:54:14PM +0200, Thomas Gleixner wrote: > On Fri, 6 May 2016, Jarkko Sakkinen wrote: > > > On Tue, May 03, 2016 at 04:06:27AM -0500, Dr. Greg Wettstein wrote: > > > It would be helpful and instructive for anyone involved in this debate > > > to review the following URL

Re: [PATCH v7 8/9] clk: mediatek: Add config options for MT2701 subsystem clocks

HI Stephen, On Fri, 2016-05-06 at 16:02 -0700, Stephen Boyd wrote: > On 04/14, James Liao wrote: > > MT2701 subsystem clocks are optional and should be enabled only if > > their subsystem drivers are ready to control these clocks. > > > > Signed-off-by: James Liao > >

Re: [PATCH v7 8/9] clk: mediatek: Add config options for MT2701 subsystem clocks

HI Stephen, On Fri, 2016-05-06 at 16:02 -0700, Stephen Boyd wrote: > On 04/14, James Liao wrote: > > MT2701 subsystem clocks are optional and should be enabled only if > > their subsystem drivers are ready to control these clocks. > > > > Signed-off-by: James Liao > > --- > > Why is this patch

Re: [PATCH 1/4] locking/rwsem: Avoid stale ->count for rwsem_down_write_failed()

On 05/08/2016 09:56 PM, Davidlohr Bueso wrote: > The field is obviously updated w.o the lock and needs a READ_ONCE > while waiting for lock holder(s) to go away, just like we do with > all other ->count accesses. This isn't actually fixing a bug because it's passed through several full barriers

Re: [PATCH 1/4] locking/rwsem: Avoid stale ->count for rwsem_down_write_failed()

On 05/08/2016 09:56 PM, Davidlohr Bueso wrote: > The field is obviously updated w.o the lock and needs a READ_ONCE > while waiting for lock holder(s) to go away, just like we do with > all other ->count accesses. This isn't actually fixing a bug because it's passed through several full barriers

Re: [PATCH v2 2/2] kasan: add kasan_double_free() test

On Fri, May 6, 2016 at 1:50 PM, Kuthonuzo Luruo wrote: > This patch adds a new 'test_kasan' test for KASAN double-free error > detection when the same slab object is concurrently deallocated. > > Signed-off-by: Kuthonuzo Luruo > --- > Changes in

Re: [PATCH v2 2/2] kasan: add kasan_double_free() test

On Fri, May 6, 2016 at 1:50 PM, Kuthonuzo Luruo wrote: > This patch adds a new 'test_kasan' test for KASAN double-free error > detection when the same slab object is concurrently deallocated. > > Signed-off-by: Kuthonuzo Luruo > --- > Changes in v2: > - This patch is new for v2. > --- >

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

On Fri, Apr 29, 2016 at 03:22:19PM -0700, Jethro Beekman wrote: > On 29-04-16 13:04, Jarkko Sakkinen wrote: > >>> Why would you want to do that? > >> > >> ... > > > > Do you see this as a performance issue or why do you think that this > > would hurt that much? > > I don't think it's a

Re: [PATCH 3/6] intel_sgx: driver for Intel Secure Guard eXtensions

On Fri, Apr 29, 2016 at 03:22:19PM -0700, Jethro Beekman wrote: > On 29-04-16 13:04, Jarkko Sakkinen wrote: > >>> Why would you want to do that? > >> > >> ... > > > > Do you see this as a performance issue or why do you think that this > > would hurt that much? > > I don't think it's a

Re: [PATCH 1/1] xen/gntdev: kmalloc structure gntdev_copy_batch

On 07/05/16 10:17, Heinrich Schuchardt wrote: > Commit a4cdb556cae0 ("xen/gntdev: add ioctl for grant copy") > leads to a warning > xen/gntdev.c: In function ‘gntdev_ioctl_grant_copy’: > xen/gntdev.c:949:1: warning: the frame size of 1248 bytes > is larger than 1024 bytes [-Wframe-larger-than=] >

Re: [PATCH 1/1] xen/gntdev: kmalloc structure gntdev_copy_batch

On 07/05/16 10:17, Heinrich Schuchardt wrote: > Commit a4cdb556cae0 ("xen/gntdev: add ioctl for grant copy") > leads to a warning > xen/gntdev.c: In function ‘gntdev_ioctl_grant_copy’: > xen/gntdev.c:949:1: warning: the frame size of 1248 bytes > is larger than 1024 bytes [-Wframe-larger-than=] >

Re: [PATCH] kdump: Fix gdb macros work work with newer and 64-bit kernels

Hi Corey, I am trying to review this patch now, and these fixes contained are very great. Just several concerns are added in inline comment. By the way, did you run this in your side? Hi Vivek, Member variable was added into task_struct in below commit replacing pids[PIDTYPE_TGID], and from

Re: [PATCH] kdump: Fix gdb macros work work with newer and 64-bit kernels

Hi Corey, I am trying to review this patch now, and these fixes contained are very great. Just several concerns are added in inline comment. By the way, did you run this in your side? Hi Vivek, Member variable was added into task_struct in below commit replacing pids[PIDTYPE_TGID], and from

RE: [Patch v3 5/8] firmware: qcom: scm: Convert to streaming DMA APIS

Hi, > This patch converts the Qualcomm SCM driver to use the streaming DMA > APIs for communication buffers. > > Signed-off-by: Andy Gross > --- Reviewed-by: sricha...@codeaurora.org Regards, Sricharan > drivers/firmware/qcom_scm-32.c | 152

RE: [Patch v3 5/8] firmware: qcom: scm: Convert to streaming DMA APIS

Hi, > This patch converts the Qualcomm SCM driver to use the streaming DMA > APIs for communication buffers. > > Signed-off-by: Andy Gross > --- Reviewed-by: sricha...@codeaurora.org Regards, Sricharan > drivers/firmware/qcom_scm-32.c | 152 + > >

Re: [PATCH 4/4] x86/kasan: Instrument user memory access API

On Fri, May 6, 2016 at 2:45 PM, Andrey Ryabinin wrote: > Exchange between user and kernel memory is coded in assembly language. > Which means that such accesses won't be spotted by KASAN as a compiler > instruments only C code. > Add explicit KASAN checks to user memory

Re: [PATCH 4/4] x86/kasan: Instrument user memory access API

On Fri, May 6, 2016 at 2:45 PM, Andrey Ryabinin wrote: > Exchange between user and kernel memory is coded in assembly language. > Which means that such accesses won't be spotted by KASAN as a compiler > instruments only C code. > Add explicit KASAN checks to user memory access API to ensure that

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

On Fri, May 06, 2016 at 06:33:42PM +0900, Sergey Senozhatsky wrote: > On (05/06/16 18:08), Sergey Senozhatsky wrote: > [..] > > and it's not 45 iterations that we are getting rid of, but around 31: > > not every class reaches it's ideal 100% ratio on the first iteration. > > so, no, sorry, I don't

[PATCH 2/4] locking/rwsem: Drop superfluous waiter refcount

Read waiters are currently reference counted from the time it enters the slowpath until the lock is released and the waiter is awoken. This is fragile and superfluous considering everything occurs within down_read() without returning to the caller, and the very nature of the primitive does not

Re: [PATCH] mm/zsmalloc: avoid unnecessary iteration in get_pages_per_zspage()

On Fri, May 06, 2016 at 06:33:42PM +0900, Sergey Senozhatsky wrote: > On (05/06/16 18:08), Sergey Senozhatsky wrote: > [..] > > and it's not 45 iterations that we are getting rid of, but around 31: > > not every class reaches it's ideal 100% ratio on the first iteration. > > so, no, sorry, I don't

[PATCH 2/4] locking/rwsem: Drop superfluous waiter refcount

Read waiters are currently reference counted from the time it enters the slowpath until the lock is released and the waiter is awoken. This is fragile and superfluous considering everything occurs within down_read() without returning to the caller, and the very nature of the primitive does not

[PATCH 3/4] locking/rwsem: Enable lockless waiter wakeup(s)

As wake_qs gain users, we can teach rwsems about them such that waiters can be awoken without the wait_lock. This is for both readers and writer, the former being the most ideal candidate as we can batch the wakeups shortening the critical region that much more -- ie writer task blocking a bunch

[PATCH 1/4] locking/rwsem: Avoid stale ->count for rwsem_down_write_failed()

The field is obviously updated w.o the lock and needs a READ_ONCE while waiting for lock holder(s) to go away, just like we do with all other ->count accesses. Signed-off-by: Davidlohr Bueso --- kernel/locking/rwsem-xadd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 3/4] locking/rwsem: Enable lockless waiter wakeup(s)

As wake_qs gain users, we can teach rwsems about them such that waiters can be awoken without the wait_lock. This is for both readers and writer, the former being the most ideal candidate as we can batch the wakeups shortening the critical region that much more -- ie writer task blocking a bunch

[PATCH 1/4] locking/rwsem: Avoid stale ->count for rwsem_down_write_failed()

The field is obviously updated w.o the lock and needs a READ_ONCE while waiting for lock holder(s) to go away, just like we do with all other ->count accesses. Signed-off-by: Davidlohr Bueso --- kernel/locking/rwsem-xadd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] locking/rwsem: Rework zeroing reader waiter->task

Readers that are awoken will expect a nil ->task indicating that a wakeup has occurred. There is a mismatch between the smp_mb() and its documentation, in that the serialization is done between reading the task and the nil store. Furthermore, in addition to having the overlapping of loads and

[PATCH 4/4] locking/rwsem: Rework zeroing reader waiter->task

Readers that are awoken will expect a nil ->task indicating that a wakeup has occurred. There is a mismatch between the smp_mb() and its documentation, in that the serialization is done between reading the task and the nil store. Furthermore, in addition to having the overlapping of loads and

[PATCH -tip 0/4] locking/rwsem (xadd): Reader waiter optimizations

Hi, This is a follow up series while reviewing Waiman's reader-owned state work[1]. While I have based it on -tip instead of that change, I can certainly rebase the series in some future iteration. Changes are mainly around reader-waiter optimizations, in no particular order. Has passed numerous

[PATCH -tip 0/4] locking/rwsem (xadd): Reader waiter optimizations

Hi, This is a follow up series while reviewing Waiman's reader-owned state work[1]. While I have based it on -tip instead of that change, I can certainly rebase the series in some future iteration. Changes are mainly around reader-waiter optimizations, in no particular order. Has passed numerous

[GIT] Networking

1) Check klogctl failure correctly, from Colin Ian King. 2) Prevent OOM when under memory pressure in flowcache, from Steffen Klassert. 3) Fix info leak in llc and rtnetlink ifmap code, from Kangjie Lu. 4) Memory barrier and multicast handling fixes in bnxt_en, from Michael Chan. 5)

[GIT] Networking

1) Check klogctl failure correctly, from Colin Ian King. 2) Prevent OOM when under memory pressure in flowcache, from Steffen Klassert. 3) Fix info leak in llc and rtnetlink ifmap code, from Kangjie Lu. 4) Memory barrier and multicast handling fixes in bnxt_en, from Michael Chan. 5)

Re: [PATCH 2/2] net: Use ns_capable_noaudit() when determining net sysctl permissions

Quoting Tyler Hicks (tyhi...@canonical.com): > The capability check should not be audited since it is only being used > to determine the inode permissions. A failed check does not indicate a > violation of security policy but, when an LSM is enabled, a denial audit > message was being generated. >

Re: [PATCH 2/2] net: Use ns_capable_noaudit() when determining net sysctl permissions

Quoting Tyler Hicks (tyhi...@canonical.com): > The capability check should not be audited since it is only being used > to determine the inode permissions. A failed check does not indicate a > violation of security policy but, when an LSM is enabled, a denial audit > message was being generated. >

Re: [PATCH 1/2] kernel: Add noaudit variant of ns_capable()

Quoting Tyler Hicks (tyhi...@canonical.com): > When checking the current cred for a capability in a specific user > namespace, it isn't always desirable to have the LSMs audit the check. > This patch adds a noaudit variant of ns_capable() for when those > situations arise. > > The common logic

Re: [PATCH 1/2] kernel: Add noaudit variant of ns_capable()

Quoting Tyler Hicks (tyhi...@canonical.com): > When checking the current cred for a capability in a specific user > namespace, it isn't always desirable to have the LSMs audit the check. > This patch adds a noaudit variant of ns_capable() for when those > situations arise. > > The common logic

RE:Drawstring bags

Dear purchasing manager, We have rich experience in manufacturing and exporting all kinds of bags, We have our own production base with advanced machine equipment, and employ professional workforce of technicians and engineers. Our products range from tote bags, drawstring bags, luggage bags,

RE:Drawstring bags

Dear purchasing manager, We have rich experience in manufacturing and exporting all kinds of bags, We have our own production base with advanced machine equipment, and employ professional workforce of technicians and engineers. Our products range from tote bags, drawstring bags, luggage bags,

Re: [PATCH] Use pid_t instead of int

Somewhere else, pid_t is a typedef for an int. Rene On 09.05.2016 03:25, Andy Lutomirski wrote: > On Sun, May 8, 2016 at 12:38 PM, René Nyffenegger > wrote: >> Use pid_t instead of int in the declarations of sys_kill, sys_tgkill, >> sys_tkill and sys_rt_sigqueueinfo in

Re: [PATCH] Use pid_t instead of int

Somewhere else, pid_t is a typedef for an int. Rene On 09.05.2016 03:25, Andy Lutomirski wrote: > On Sun, May 8, 2016 at 12:38 PM, René Nyffenegger > wrote: >> Use pid_t instead of int in the declarations of sys_kill, sys_tgkill, >> sys_tkill and sys_rt_sigqueueinfo in include/linux/syscalls.h

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, May 09, 2016 at 05:52:51AM +0200, Mike Galbraith wrote: > On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > > > In addition, I would argue maybe beefing up idle balancing is a more > > productive way to spread load, as work-stealing just does what needs > > to be done. And seems it

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, May 09, 2016 at 05:52:51AM +0200, Mike Galbraith wrote: > On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > > > In addition, I would argue maybe beefing up idle balancing is a more > > productive way to spread load, as work-stealing just does what needs > > to be done. And seems it

Re: [RFC PATCH v2 07/10] efi: load SSTDs from EFI variables

Hi Octavian, Apologies for missing this earlier, just catching up on this thread... On 04/19/2016 06:39 PM, Octavian Purdila wrote: > This patch allows SSDTs to be loaded from EFI variables. It works by > specifying the EFI variable name containing the SSDT to be loaded. All > variables with

Re: [RFC PATCH v2 07/10] efi: load SSTDs from EFI variables

Hi Octavian, Apologies for missing this earlier, just catching up on this thread... On 04/19/2016 06:39 PM, Octavian Purdila wrote: > This patch allows SSDTs to be loaded from EFI variables. It works by > specifying the EFI variable name containing the SSDT to be loaded. All > variables with

[PATCH] sched/rt/deadline: Don't push if task's scheduling class was changed

We got a warning below: WARNING: CPU: 1 PID: 2468 at kernel/sched/core.c:1161 set_task_cpu+0x1af/0x1c0 CPU: 1 PID: 2468 Comm: bugon Not tainted 4.6.0-rc3+ #16 Hardware name: Intel Corporation Broadwell Client 0086 89618374 8800897a7d50 8133dc8c

[PATCH] sched/rt/deadline: Don't push if task's scheduling class was changed

We got a warning below: WARNING: CPU: 1 PID: 2468 at kernel/sched/core.c:1161 set_task_cpu+0x1af/0x1c0 CPU: 1 PID: 2468 Comm: bugon Not tainted 4.6.0-rc3+ #16 Hardware name: Intel Corporation Broadwell Client 0086 89618374 8800897a7d50 8133dc8c

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, May 09, 2016 at 05:45:40AM +0200, Mike Galbraith wrote: > On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > > On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > > > Maybe give the criteria a bit margin, not just wakees tend to equal > > > > llc_size, > > > > but the

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, May 09, 2016 at 05:45:40AM +0200, Mike Galbraith wrote: > On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > > On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > > > Maybe give the criteria a bit margin, not just wakees tend to equal > > > > llc_size, > > > > but the

Re: [PATCH V2 2/2] irqchip/gicv3-its: Implement two-level(indirect) device table support

On 05/08/2016 09:14 PM, Shanker Donthineni wrote: > Since device IDs are extremely sparse, the single, a.k.a flat table is > not sufficient for the following two reasons. > > 1) According to ARM-GIC spec, ITS hw can access maximum of 256(pages)* >64K(pageszie) bytes. In the best case, it

Re: [PATCH V2 2/2] irqchip/gicv3-its: Implement two-level(indirect) device table support

On 05/08/2016 09:14 PM, Shanker Donthineni wrote: > Since device IDs are extremely sparse, the single, a.k.a flat table is > not sufficient for the following two reasons. > > 1) According to ARM-GIC spec, ITS hw can access maximum of 256(pages)* >64K(pageszie) bytes. In the best case, it

[PATCH -tip] sched/wake_q: fix typo in wake_q_add

... the comment clearly refers to wake_up_q, and not wake_up_list. Signed-off-by: Davidlohr Bueso --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index c82ca6eccfec..c59e4df38591 100644 ---

[PATCH -tip] sched/wake_q: fix typo in wake_q_add

... the comment clearly refers to wake_up_q, and not wake_up_list. Signed-off-by: Davidlohr Bueso --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index c82ca6eccfec..c59e4df38591 100644 ---

Re: [PATCH] tools: bpf_jit_disasm: check for klogctl failure

From: Daniel Borkmann Date: Fri, 06 May 2016 00:46:56 +0200 > On 05/06/2016 12:39 AM, Colin King wrote: >> From: Colin Ian King >> >> klogctl can fail and return -ve len, so check for this and >> return NULL to avoid passing a (size_t)-1 to

Re: [PATCH] tools: bpf_jit_disasm: check for klogctl failure

From: Daniel Borkmann Date: Fri, 06 May 2016 00:46:56 +0200 > On 05/06/2016 12:39 AM, Colin King wrote: >> From: Colin Ian King >> >> klogctl can fail and return -ve len, so check for this and >> return NULL to avoid passing a (size_t)-1 to malloc. >> >> Signed-off-by: Colin Ian King > > [

Re: [PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl

From: Tyler Hicks Date: Fri, 6 May 2016 18:04:12 -0500 > This pair of patches does away with what I believe is a useless denial > audit message when a privileged process initially accesses a net sysctl. The LSM folks can apply this if they agree with you.

Re: [PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl

From: Tyler Hicks Date: Fri, 6 May 2016 18:04:12 -0500 > This pair of patches does away with what I believe is a useless denial > audit message when a privileged process initially accesses a net sysctl. The LSM folks can apply this if they agree with you.

Re: [PATCH v2] net: arc/emac: Move arc_emac_tx_clean() into arc_emac_tx() and disable tx interrut

From: Caesar Wang Date: Fri, 6 May 2016 20:19:16 +0800 > Doing tx_clean() inside poll() may scramble the tx ring buffer if > tx() is running. This will cause tx to stop working, which can be > reproduced by simultaneously downloading two large files at high speed. > >

Re: [PATCH v2] net: arc/emac: Move arc_emac_tx_clean() into arc_emac_tx() and disable tx interrut

From: Caesar Wang Date: Fri, 6 May 2016 20:19:16 +0800 > Doing tx_clean() inside poll() may scramble the tx ring buffer if > tx() is running. This will cause tx to stop working, which can be > reproduced by simultaneously downloading two large files at high speed. > > Moving tx_clean() into

Re: [PATCH v4 1/2] soc: qcom: smd: Introduce compile stubs

From: Bjorn Andersson Date: Fri, 6 May 2016 07:09:07 -0700 > Introduce compile stubs for the SMD API, allowing consumers to be > compile tested. > > Acked-by: Andy Gross > Signed-off-by: Bjorn Andersson Applied.

Re: [PATCH v4 2/2] net: Add Qualcomm IPC router

From: Bjorn Andersson Date: Fri, 6 May 2016 07:09:08 -0700 > From: Courtney Cavin > > Add an implementation of Qualcomm's IPC router protocol, used to > communicate with service providing remote processors. > > Signed-off-by:

Re: [PATCH v4 1/2] soc: qcom: smd: Introduce compile stubs

From: Bjorn Andersson Date: Fri, 6 May 2016 07:09:07 -0700 > Introduce compile stubs for the SMD API, allowing consumers to be > compile tested. > > Acked-by: Andy Gross > Signed-off-by: Bjorn Andersson Applied.

Re: [PATCH v4 2/2] net: Add Qualcomm IPC router

From: Bjorn Andersson Date: Fri, 6 May 2016 07:09:08 -0700 > From: Courtney Cavin > > Add an implementation of Qualcomm's IPC router protocol, used to > communicate with service providing remote processors. > > Signed-off-by: Courtney Cavin > Signed-off-by: Bjorn Andersson > [bjorn: Cope

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > In addition, I would argue maybe beefing up idle balancing is a more > productive way to spread load, as work-stealing just does what needs > to be done. And seems it has been (sub-unconsciously) neglected in this > case, :) P.S. Nope, I'm

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > In addition, I would argue maybe beefing up idle balancing is a more > productive way to spread load, as work-stealing just does what needs > to be done. And seems it has been (sub-unconsciously) neglected in this > case, :) P.S. Nope, I'm

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > > Maybe give the criteria a bit margin, not just wakees tend to equal > > > llc_size, > > > but the numbers are so wild to easily break the fragile condition, like: > > > >

Re: sched: tweak select_idle_sibling to look for idle threads

On Mon, 2016-05-09 at 02:57 +0800, Yuyang Du wrote: > On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > > Maybe give the criteria a bit margin, not just wakees tend to equal > > > llc_size, > > > but the numbers are so wild to easily break the fragile condition, like: > > > >

Re: [patch] qede: uninitialized variable in qede_start_xmit()

From: Dan Carpenter Date: Thu, 5 May 2016 16:21:30 +0300 > "data_split" was never set to false. It's just uninitialized. > > Fixes: 2950219d87b0 ('qede: Add basic network device support') > Signed-off-by: Dan Carpenter Applied, thanks Dan.

Re: [patch] qede: uninitialized variable in qede_start_xmit()

From: Dan Carpenter Date: Thu, 5 May 2016 16:21:30 +0300 > "data_split" was never set to false. It's just uninitialized. > > Fixes: 2950219d87b0 ('qede: Add basic network device support') > Signed-off-by: Dan Carpenter Applied, thanks Dan.

RE: [PATCH] debugobjects: insulate non-fixup logic related to static obj from fixup callbacks

> From: Thomas Gleixner [mailto:t...@linutronix.de] > On Sun, 8 May 2016, Du, Changbin wrote: > > > From: Thomas Gleixner [mailto:t...@linutronix.de] > > > > raw_spin_unlock_irqrestore(>lock, flags); > > > > /* > > > > -* Maybe the object is static.

RE: [PATCH] debugobjects: insulate non-fixup logic related to static obj from fixup callbacks

> From: Thomas Gleixner [mailto:t...@linutronix.de] > On Sun, 8 May 2016, Du, Changbin wrote: > > > From: Thomas Gleixner [mailto:t...@linutronix.de] > > > > raw_spin_unlock_irqrestore(>lock, flags); > > > > /* > > > > -* Maybe the object is static.

Re: [PATCH] mmc: mmc: do not use CMD13 to get status after speed mode switch

+ linux-rockchip I just hacked my local branch to fix the issues found on rockchip platform. The reaseon is that mmc core fail to get status after switching from hs200 to hs. So I disabled sending status for it just like what Chaotian does here. But I didn't deeply dig out the root cause but I

Re: [PATCH] mmc: mmc: do not use CMD13 to get status after speed mode switch

+ linux-rockchip I just hacked my local branch to fix the issues found on rockchip platform. The reaseon is that mmc core fail to get status after switching from hs200 to hs. So I disabled sending status for it just like what Chaotian does here. But I didn't deeply dig out the root cause but I

[PATCH 3/3] staging: dgnc: Need to check for NULL of ch

the "ch" from brd structure could be NULL, it need to check for NULL. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c

[PATCH 3/3] staging: dgnc: Need to check for NULL of ch

the "ch" from brd structure could be NULL, it need to check for NULL. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c index 9eae1a6..ba57e95

[PATCH 1/3] staging: dgnc: fix 'line over 80 characters'

fix checkpatch.pl warning about 'line over 80 characters'. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_sysfs.c | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_sysfs.c

[PATCH 1/3] staging: dgnc: fix 'line over 80 characters'

fix checkpatch.pl warning about 'line over 80 characters'. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_sysfs.c | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_sysfs.c b/drivers/staging/dgnc/dgnc_sysfs.c index

[PATCH 2/3] staging: dgnc: remove redundant condition check

dgnc_board(brd) was already checked for NULL before calling neo_parse_isr(). And also port doesn't need to check. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_neo.c

[PATCH 2/3] staging: dgnc: remove redundant condition check

dgnc_board(brd) was already checked for NULL before calling neo_parse_isr(). And also port doesn't need to check. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_neo.c

[PATCH] sched: fix the calculation of __sched_period in sched_slice()

When we get the sched_slice of a sched_entity, we use cfs_rq->nr_running to calculate the whole __sched_period. But cfs_rq->nr_running is the number of sched_entity in that cfs_rq, rq->nr_running is the number of all the tasks that are not throttled. So we should use the rq->nr_running to

[PATCH] sched: fix the calculation of __sched_period in sched_slice()

When we get the sched_slice of a sched_entity, we use cfs_rq->nr_running to calculate the whole __sched_period. But cfs_rq->nr_running is the number of sched_entity in that cfs_rq, rq->nr_running is the number of all the tasks that are not throttled. So we should use the rq->nr_running to

Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available

On Mon, May 09, 2016 at 11:45:43AM +1000, Dave Chinner wrote: > [ OT, but I'll reply anyway :P ] > > On Fri, May 06, 2016 at 02:29:23PM -0400, J. Bruce Fields wrote: > > On Thu, May 05, 2016 at 08:56:02AM +1000, Dave Chinner wrote: > > > In the latest XFS filesystem format, we randomise the

Re: [PATCH 1/6] statx: Add a system call to make enhanced file info available

On Mon, May 09, 2016 at 11:45:43AM +1000, Dave Chinner wrote: > [ OT, but I'll reply anyway :P ] > > On Fri, May 06, 2016 at 02:29:23PM -0400, J. Bruce Fields wrote: > > On Thu, May 05, 2016 at 08:56:02AM +1000, Dave Chinner wrote: > > > In the latest XFS filesystem format, we randomise the

Re: sched: tweak select_idle_sibling to look for idle threads

On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > Maybe give the criteria a bit margin, not just wakees tend to equal > > llc_size, > > but the numbers are so wild to easily break the fragile condition, like: > > Seems lockless traversal and averages just lets multiple CPUs

Re: sched: tweak select_idle_sibling to look for idle threads

On Sun, May 08, 2016 at 10:08:55AM +0200, Mike Galbraith wrote: > > Maybe give the criteria a bit margin, not just wakees tend to equal > > llc_size, > > but the numbers are so wild to easily break the fragile condition, like: > > Seems lockless traversal and averages just lets multiple CPUs

[PATCH v5 00/13] Support non-lru page migration

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be

[PATCH v5 02/12] mm: migrate: support non-lru movable page migration

We have allowed migration for only LRU pages until now and it was enough to make high-order pages. But recently, embedded system(e.g., webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory) so we have seen several reports about troubles of small high-order allocation. For fixing

[PATCH v5 00/13] Support non-lru page migration

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be

[PATCH v5 02/12] mm: migrate: support non-lru movable page migration

We have allowed migration for only LRU pages until now and it was enough to make high-order pages. But recently, embedded system(e.g., webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory) so we have seen several reports about troubles of small high-order allocation. For fixing

[PATCH v5 04/12] zsmalloc: keep max_object in size_class

Every zspage in a size_class has same number of max objects so we could move it to a size_class. Reviewed-by: Sergey Senozhatsky Signed-off-by: Minchan Kim --- mm/zsmalloc.c | 32 +++- 1 file changed, 15

[PATCH v5 05/12] zsmalloc: use bit_spin_lock

Use kernel standard bit spin-lock instead of custom mess. Even, it has a bug which doesn't disable preemption. The reason we don't have any problem is that we have used it during preemption disable section by class->lock spinlock. So no need to go to stable. Cc: Sergey Senozhatsky

[PATCH v5 03/12] mm: balloon: use general non-lru movable page feature

Now, VM has a feature to migrate non-lru movable pages so balloon doesn't need custom migration hooks in migrate.c and compaction.c. Instead, this patch implements page->mapping->a_ops->{isolate|migrate|putback} functions. With that, we could remove hooks for ballooning in general migration

[PATCH v5 06/12] zsmalloc: use accessor

Upcoming patch will change how to encode zspage meta so for easy review, this patch wraps code to access metadata as accessor. Cc: Sergey Senozhatsky Signed-off-by: Minchan Kim --- mm/zsmalloc.c | 82

  1   2   3   4   5   >