[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 store

[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 of

[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 a/kerne

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 sugg

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 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 + > > dr

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 the

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 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 performance

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. > --- > lib/test

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 wh

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 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 whi

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 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 > > --- > > critic

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

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

[PATCH] ACPI: Execute the _PTS method when system reboot

The _PTS control method is defined in the section 7.4.1 of acpi 6.0 spec. The _PTS control method is executed by the OS during the sleep transition process for S1, S2, S3, S4, and for orderly S5 shutdown. The sleeping state value (For example, 1, 2, 3, 4 or 5 for the S5 soft-off state) is passed to

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

> >> Thank you for the review! > >> > >> > > + switch (alloc_data.state) { > >> > > + case KASAN_STATE_QUARANTINE: > >> > > + case KASAN_STATE_FREE: > >> > > + kasan_report((unsigned long)object, 0, false, > >> > > + (unsigned long)__builtin_return_address(1)); > >>

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

>>> Heinrich Schuchardt 05/08/16 8:13 AM >>> >--- a/drivers/xen/gntdev.c >+++ b/drivers/xen/gntdev.c >@@ -915,36 +915,43 @@ static int gntdev_grant_copy_seg(struct >gntdev_copy_batch *batch, >static long gntdev_ioctl_grant_copy(struct gntdev_priv *priv, void __user *u) >{ >struct ioctl_gntdev_gra

[PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

Include the CPU thermal nodes directly in Odroid XU3-family common DTS because it is the only user of it. Keeping it in separate DTSI node does not bring benefits because: 1. It is not re-usable on other non-fan boards (fan is referenced), 2. It won't be re-used on future Odroid XU board because di

[PATCH] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

Add ion cached pool in system heap. Signed-off-by: Chen Feng Signed-off-by: Xia Qing --- drivers/staging/android/ion/ion_system_heap.c | 120 +- 1 file changed, 79 insertions(+), 41 deletions(-) diff --git a/drivers/staging/android/ion/ion_system_heap.c b/drivers/stag

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

On Mon, 9 May 2016, Jarkko Sakkinen wrote: > 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

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

* 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 > userspace writes to (or rea

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

Hi all, On Mon, 9 May 2016 10:59:27 +1000 Stephen Rothwell wrote: > > 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

Re: [PATCH] Use pid_t instead of int

From: René Nyffenegger In include/linux/syscalls.h, the four functions sys_kill, sys_tgkill, sys_tkill and sys_rt_sigqueueinfo are declared with "int pid" and "int tgid". However, in kernel/signal.c, the corresponding definitions use the more appropriate "pid_t" (which is a typedef'd int). This

Re: [PATCH v7 4/9] clk: mediatek: Add MT2701 clock support

Hi Stephen, On Fri, 2016-05-06 at 16:11 -0700, Stephen Boyd wrote: > On 04/14, James Liao wrote: > > diff --git a/drivers/clk/mediatek/clk-mt2701.c > > b/drivers/clk/mediatek/clk-mt2701.c > > new file mode 100644 > > index 000..b4db141 > > --- /dev/null > > +++ b/drivers/clk/mediatek/clk-mt27

[tip:sched/core] sched/core: Remove unused variable

Commit-ID: 8c5e95548d41a48b1eb2be741107a259251ebd86 Gitweb: http://git.kernel.org/tip/8c5e95548d41a48b1eb2be741107a259251ebd86 Author: Muhammad Falak R Wani AuthorDate: Thu, 5 May 2016 15:21:19 +0530 Committer: Ingo Molnar CommitDate: Mon, 9 May 2016 08:39:52 +0200 sched/core: Remove u

[tip:sched/core] sched/core: Fix comment typo in wake_q_add()

Commit-ID: 58fe9c4621b7219e724c0b7af053112f974a08c3 Gitweb: http://git.kernel.org/tip/58fe9c4621b7219e724c0b7af053112f974a08c3 Author: Davidlohr Bueso AuthorDate: Sun, 8 May 2016 20:58:10 -0700 Committer: Ingo Molnar CommitDate: Mon, 9 May 2016 08:39:52 +0200 sched/core: Fix comment ty

qemu m68k/mcf5208: problem with signal handler

Dear kernel hackers, I have a problem with the signal handling under qemu-system-m68k emulating coldfire mcf5208 evalboard. Following example code provided by Busybox maintainer Denys Vlasenko shows the problem when running on qemu: #include

Re: [PATCH] ION: Sys_heap: Add cached pool to spead up cached buffer alloc

Sorry,the order here is not right, please ignore this patch. I will RESEND it. On 2016/5/9 14:24, Chen Feng wrote: > Add ion cached pool in system heap. > > Signed-off-by: Chen Feng > Signed-off-by: Xia Qing > --- > drivers/staging/android/ion/ion_system_heap.c | 120 > +

[PATCH v4 08/11] arm64: tegra: set hot trips for Tegra132

Enable throttle function for SOC_THERM. Set "hot" trips for cpu and gpu thermal zones, which can trigger the SOC_THERM hardware throttle. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra132.dtsi | 41 +--- 1 file changed, 32 insertions(+), 9 deletions(-) di

[PATCH v4 03/11] thermal: tegra: add hw-throttle for Tegra132

Tegra132 use CCROC throttle registers to configure pulse skiper, set these registers to enable throttle function for Tegra132. Signed-off-by: Wei Ni --- drivers/thermal/tegra/soctherm.c| 234 +--- drivers/thermal/tegra/tegra132-soctherm.c | 17 ++ inclu

[PATCH v4 09/11] arm64: tegra: add soctherm node for Tegra210

Adds soctherm node for Tegra210, and add cpu, gpu, mem, pllx as thermal-zones. Set critical trip temperatures for them. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra210.dtsi | 44 1 file changed, 44 insertions(+) diff --git a/arch/arm64/boot/dts/nvi

[PATCH v4 01/11] of: Add bindings of hw throttle for Tegra soctherm

Add HW throttle configuration sub-node for soctherm, which is used to describe the throttle event, and worked as a cooling device. The "hot" type trip in thermal zone can be bound to this cooling device, and trigger the throttle function. Signed-off-by: Wei Ni --- .../bindings/thermal/nvidia,teg

[PATCH v4 02/11] thermal: tegra: add hw-throttle function

Tegra soctherm support HW throttle, when the soctherm snesors' temperature is above the throttle trip point, it will trigger pulse skiper to tune clocks accroding to the throttle depth. Add this function for Tegra124 and Tegra210. Since Tegra132 use different registers to configure pulse skiper, wi

[PATCH v4 11/11] arm64: tegra: set hot trips for Tegra210

Enable throttle function for SOC_THERM. Set "hot" trips for cpu and gpu thermal zones, which can trigger the SOC_THERM hardware throttle. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra210.dtsi | 41 +--- 1 file changed, 32 insertions(+), 9 deletions(-) di

[PATCH v4 10/11] arm64: tegra: set critical trips for Tegra210

Set general "critical" trip temperatures for cpu, gpu, mem and pllx thermal zones on Tegra210, these trips can trigger shut down or reset. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra210.dtsi | 60 1 file changed, 60 insertions(+) diff --git a/arch

[PATCH -resend] MAINTAINERS: remove Koichi Yasutake

The MTA says: : unknown user: "yasutake.koi...@jp.panasonic.com" Signed-off-by: Jiri Slaby Cc: David Howells Cc: linux-am33-l...@redhat.com --- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 0607ad9f6b29..2f17e7c2ab5c 100644 --- a/MAINTAINERS

[PATCH v4 07/11] arm64: tegra: set critical trips for Tegra132

Set general "critical" trip temperatures for cpu, gpu, mem and pllx thermal zones on Tegra132, these trips can trigger shut down or reset. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra132.dtsi | 60 1 file changed, 60 insertions(+) diff --git a/arch

[PATCH v4 00/11] Add HW throttle for Tegra soctherm

This series add following functions for Tegra soctherm: 1. add HW throttle function. 2. enable soctherm node for Tegra124, Tegra132, Tegra210, and set "critical", "hot" trips for them. Main changes from v3: 1. change some properties'name and descriptions, per Rob's comments. 2. change the correspo

[PATCH v4 06/11] arm64: tegra: use tegra132-soctherm for Tegra132

The Tegra132 has the specific settings for soctherm, so change to use campatible "nvidia,tegra132-soctherm" for it. And adds cpu, gpu, mem and pllx thermal zones. Signed-off-by: Wei Ni --- arch/arm64/boot/dts/nvidia/tegra132.dtsi | 36 ++-- 1 file changed, 34 insertio

[PATCH v4 04/11] arm: tegra: set critical trips for Tegra124

Set general "critical" trip temperatures for cpu, gpu, mem and pllx thermal zones for all Tegra124 platform, these trips can trigger shut down or reset. Tegra124 Jetson TK1 was already set "critical" trips before, so it can overwrite the general values. Signed-off-by: Wei Ni --- arch/arm/boot/dt

[PATCH v4 05/11] arm: tegra: set hot trips for Tegra124

Enable throttle function for SOC_THERM. Set "hot" trips for cpu and gpu thermal zones, which can trigger the SOC_THERM hardware throttle. Signed-off-by: Wei Ni --- arch/arm/boot/dts/tegra124.dtsi | 39 ++- 1 file changed, 30 insertions(+), 9 deletions(-) diff

[PATCH 0/2] mtd: atmel_nand: remove compatible "atmel,sama5d4-nfc"

It is a datasheet bug, for current SoCs, the RB_EDGE3(i.e. bit 27) of HSMC_SR register does not exist, the RB_EDGE0 (i.e. bit 24) is the ready/busy line edge status bit. So the compatible "atmel,sama5d4-nfc" is unneeded. Wenyou Yang (2): Revert "mtd: atmel_nand: Support variable RB_EDGE interru

[PATCH 1/2] Revert "mtd: atmel_nand: Support variable RB_EDGE interrupts"

This reverts commit 5ddc7bd43ccc ("mtd: atmel_nand: Support variable RB_EDGE interrupts") Because for current SoCs, the RB_EDGE3(i.e. bit 27) of HSMC_SR register does not exist, the RB_EDGE0 (i.e. bit 24) is the ready/busy line edge status bit. It is a datasheet bug. Signed-off-by: Wenyou Yang -

<    1   2   3