Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On Tue, Nov 15, 2016 at 4:15 PM, Dave Hansen wrote: > On 11/10/2016 02:11 PM, Dan Williams wrote: >> @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int >> is_pid) >> "ShmemPmdMapped: %8lu kB\n" >> "Shared_Hugetlb:

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On Tue, Nov 15, 2016 at 4:15 PM, Dave Hansen wrote: > On 11/10/2016 02:11 PM, Dan Williams wrote: >> @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int >> is_pid) >> "ShmemPmdMapped: %8lu kB\n" >> "Shared_Hugetlb: %8lu kB\n" >>

Re: [PATCH v4 6/6] posix-timers: make it configurable

On Thu, Nov 10, 2016 at 9:10 PM, Nicolas Pitre wrote: > Some embedded systems have no use for them. This removes about > 25KB from the kernel binary size when configured out. > > Corresponding syscalls are routed to a stub logging the attempt to > use those syscalls

Re: [PATCH v4 6/6] posix-timers: make it configurable

On Thu, Nov 10, 2016 at 9:10 PM, Nicolas Pitre wrote: > Some embedded systems have no use for them. This removes about > 25KB from the kernel binary size when configured out. > > Corresponding syscalls are routed to a stub logging the attempt to > use those syscalls which should be enough of a

Re: [PATCH v2 02/10] dt-bindings: add documentation for rk1108 cru

On 2016/11/15 17:35, Heiko Stuebner wrote: Hi Andy, Am Montag, 14. November 2016, 20:03:01 CET schrieb Andy Yan: From: Shawn Lin This adds the dt-binding documentation for the clock and reset unit found on Rockchip rk1108 SoCs. Signed-off-by: Shawn Lin

Re: [PATCH v2 02/10] dt-bindings: add documentation for rk1108 cru

On 2016/11/15 17:35, Heiko Stuebner wrote: Hi Andy, Am Montag, 14. November 2016, 20:03:01 CET schrieb Andy Yan: From: Shawn Lin This adds the dt-binding documentation for the clock and reset unit found on Rockchip rk1108 SoCs. Signed-off-by: Shawn Lin Signed-off-by: Andy Yan --- Changes

Re: [PATCH v2 03/10] clk: rockchip: add dt-binding header for rk1108

On 2016/11/15 17:41, Heiko Stuebner wrote: Am Montag, 14. November 2016, 20:04:52 CET schrieb Andy Yan: From: Shawn Lin Add the dt-bindings header for the rk1108, that gets shared between the clock controller and the clock references in the dts. Signed-off-by: Shawn

Re: [PATCH v2 03/10] clk: rockchip: add dt-binding header for rk1108

On 2016/11/15 17:41, Heiko Stuebner wrote: Am Montag, 14. November 2016, 20:04:52 CET schrieb Andy Yan: From: Shawn Lin Add the dt-bindings header for the rk1108, that gets shared between the clock controller and the clock references in the dts. Signed-off-by: Shawn Lin Signed-off-by: Andy

linux-next: build warning after merge of the net-next tree

Hi all, After merging the net-next tree, today's linux-next build (x86_64 allmodconfig) produced this warning: kernel/bpf/bpf_lru_list.c: In function '__bpf_lru_list_rotate_inactive.isra.3': kernel/bpf/bpf_lru_list.c:201:28: warning: 'next' may be used uninitialized in this function

linux-next: build warning after merge of the net-next tree

Hi all, After merging the net-next tree, today's linux-next build (x86_64 allmodconfig) produced this warning: kernel/bpf/bpf_lru_list.c: In function '__bpf_lru_list_rotate_inactive.isra.3': kernel/bpf/bpf_lru_list.c:201:28: warning: 'next' may be used uninitialized in this function

Re: linux-next: build warning after merge of the pstore tree

On Tue, Nov 15, 2016 at 4:27 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the pstore tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from include/linux/rcupdate.h:38:0, > from

Re: linux-next: build warning after merge of the pstore tree

On Tue, Nov 15, 2016 at 4:27 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the pstore tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from include/linux/rcupdate.h:38:0, > from include/linux/idr.h:18, >

Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

On 15/11/16 21:57, Michael Ellerman wrote: > POISON_POINTER_DELTA is defined in poison.h, and is intended to be used > to shift poison values so that they don't alias userspace. > > We should add it to ZERO_SIZE_PTR so that attackers can't use > ZERO_SIZE_PTR as a way to get a pointer to

Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

On 15/11/16 21:57, Michael Ellerman wrote: > POISON_POINTER_DELTA is defined in poison.h, and is intended to be used > to shift poison values so that they don't alias userspace. > > We should add it to ZERO_SIZE_PTR so that attackers can't use > ZERO_SIZE_PTR as a way to get a pointer to

Re: [PATCH] ramoops: add pdata NULL check to ramoops_probe

On Thu, Sep 29, 2016 at 3:05 AM, Geliang Tang wrote: > On Wed, Sep 28, 2016 at 12:45:13PM -0700, Kees Cook wrote: >> On Wed, Sep 28, 2016 at 3:32 AM, Geliang Tang wrote: >> > When the pdata is NULL, ramoops_probe() segfaults. So this patch adds >> >

Re: [PATCH] ramoops: add pdata NULL check to ramoops_probe

On Thu, Sep 29, 2016 at 3:05 AM, Geliang Tang wrote: > On Wed, Sep 28, 2016 at 12:45:13PM -0700, Kees Cook wrote: >> On Wed, Sep 28, 2016 at 3:32 AM, Geliang Tang wrote: >> > When the pdata is NULL, ramoops_probe() segfaults. So this patch adds >> > a NULL check to it. >> >> While I don't mind

Re: [PATCH v6 4/4] PCI: designware: Add iATU Unroll feature

Hi Tim, On Tue, Nov 15, 2016 at 10:22 PM, Tim Harvey wrote: > Bjorn / Joao, > > This patch (from commit a0601a47053714eecec726aea5ebcd829f817497) is > causing a kernel regression in 4.9. I can no longer boot the kernel on > boards that have a PCIe switch downstream from

Re: [PATCH v6 4/4] PCI: designware: Add iATU Unroll feature

Hi Tim, On Tue, Nov 15, 2016 at 10:22 PM, Tim Harvey wrote: > Bjorn / Joao, > > This patch (from commit a0601a47053714eecec726aea5ebcd829f817497) is > causing a kernel regression in 4.9. I can no longer boot the kernel on > boards that have a PCIe switch downstream from the IMX6 (ie many of >

linux-next: build warning after merge of the pstore tree

Hi Kees, After merging the pstore tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/rcupdate.h:38:0, from include/linux/idr.h:18, from include/linux/kernfs.h:14, from

Re: [PATCH] vt: fix Scroll Lock LED trigger name

Maciej S. Szmigiero, on Wed 16 Nov 2016 00:55:57 +0100, wrote: > There is a disagreement between drivers/tty/vt/keyboard.c and > drivers/input/input-leds.c with regard to what is a Scroll Lock LED > trigger name: input calls it "kbd-scrolllock", but vt calls it > "kbd-scrollock" (two l's). > This

linux-next: build warning after merge of the pstore tree

Hi Kees, After merging the pstore tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/rcupdate.h:38:0, from include/linux/idr.h:18, from include/linux/kernfs.h:14, from

Re: [PATCH] vt: fix Scroll Lock LED trigger name

Maciej S. Szmigiero, on Wed 16 Nov 2016 00:55:57 +0100, wrote: > There is a disagreement between drivers/tty/vt/keyboard.c and > drivers/input/input-leds.c with regard to what is a Scroll Lock LED > trigger name: input calls it "kbd-scrolllock", but vt calls it > "kbd-scrollock" (two l's). > This

Re: [PATCH v6 4/4] PCI: designware: Add iATU Unroll feature

On Wed, Aug 17, 2016 at 1:00 PM, Bjorn Helgaas wrote: > From: Joao Pinto > > Add support for the new iATU Unroll mechanism that will be used from Core > version 4.80. The new Cores can support either iATU Unroll or the "old" > iATU method, now

Re: [PATCH v6 4/4] PCI: designware: Add iATU Unroll feature

On Wed, Aug 17, 2016 at 1:00 PM, Bjorn Helgaas wrote: > From: Joao Pinto > > Add support for the new iATU Unroll mechanism that will be used from Core > version 4.80. The new Cores can support either iATU Unroll or the "old" > iATU method, now called Legacy Mode. The driver is perfectly

[PATCH] clk: rockchip: rk3399: fix copy-paste error

Fix RK3368_* to RK3399_* for rk3399 clk_test clock. Signed-off-by: Jianqun Xu --- drivers/clk/rockchip/clk-rk3399.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c index

[PATCH] clk: rockchip: rk3399: fix copy-paste error

Fix RK3368_* to RK3399_* for rk3399 clk_test clock. Signed-off-by: Jianqun Xu --- drivers/clk/rockchip/clk-rk3399.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c index 2c7cba7..ccbf558b 100644 ---

Re: [PATHCv10 1/2] usb: USB Type-C connector class

Hi, At present I am using the uevent in the userspace to infer the Presence of a port on the remote end through the appearance of usbc*-partner. Userspace uses this info to decide on when to show a USB notification on the screen and what should be the options provided in the dialog. I was

Re: [PATHCv10 1/2] usb: USB Type-C connector class

Hi, At present I am using the uevent in the userspace to infer the Presence of a port on the remote end through the appearance of usbc*-partner. Userspace uses this info to decide on when to show a USB notification on the screen and what should be the options provided in the dialog. I was

[PATCH] vt: fix Scroll Lock LED trigger name

There is a disagreement between drivers/tty/vt/keyboard.c and drivers/input/input-leds.c with regard to what is a Scroll Lock LED trigger name: input calls it "kbd-scrolllock", but vt calls it "kbd-scrollock" (two l's). This prevents Scroll Lock LED trigger from binding to this LED by default.

[PATCH] vt: fix Scroll Lock LED trigger name

There is a disagreement between drivers/tty/vt/keyboard.c and drivers/input/input-leds.c with regard to what is a Scroll Lock LED trigger name: input calls it "kbd-scrolllock", but vt calls it "kbd-scrollock" (two l's). This prevents Scroll Lock LED trigger from binding to this LED by default.

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On 11/10/2016 02:11 PM, Dan Williams wrote: > @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int > is_pid) > "ShmemPmdMapped: %8lu kB\n" > "Shared_Hugetlb: %8lu kB\n" > "Private_Hugetlb: %7lu kB\n" > +

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On 11/10/2016 02:11 PM, Dan Williams wrote: > @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int > is_pid) > "ShmemPmdMapped: %8lu kB\n" > "Shared_Hugetlb: %8lu kB\n" > "Private_Hugetlb: %7lu kB\n" > +

Re: [RFC PATCH] ARM64: dts: Add support for Meson GXM

On Mon, Nov 14, 2016 at 10:44:11AM +0100, Neil Armstrong wrote: > Following the Amlogic Linux kernel, it seem the only differences > between the GXL and GXM SoCs are the CPU Clusters. > > Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards > dts files since the S905D and S912 SoCs

Re: [RFC PATCH] ARM64: dts: Add support for Meson GXM

On Mon, Nov 14, 2016 at 10:44:11AM +0100, Neil Armstrong wrote: > Following the Amlogic Linux kernel, it seem the only differences > between the GXL and GXM SoCs are the CPU Clusters. > > Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards > dts files since the S905D and S912 SoCs

[PATCH] drm/bridge: analogix_dp: return error if transfer none byte

Reference from drm_dp_aux description (about transfer): Upon success, the implementation should return the number of payload bytes that were transferred, or a negative error-code on failure. Helpers propagate errors from the .transfer() function, with the exception of the -EBUSY error, which

[PATCH] drm/bridge: analogix_dp: return error if transfer none byte

Reference from drm_dp_aux description (about transfer): Upon success, the implementation should return the number of payload bytes that were transferred, or a negative error-code on failure. Helpers propagate errors from the .transfer() function, with the exception of the -EBUSY error, which

[PATCH] clk: rockchip: rk3399: fix copy-paste error

Fix RK3368_CLKSEL_CON to RK3399_CLKSEL_CON for rk3399 clock driver. Signed-off-by: Jianqun Xu --- drivers/clk/rockchip/clk-rk3399.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/rockchip/clk-rk3399.c

[PATCH] clk: rockchip: rk3399: fix copy-paste error

Fix RK3368_CLKSEL_CON to RK3399_CLKSEL_CON for rk3399 clock driver. Signed-off-by: Jianqun Xu --- drivers/clk/rockchip/clk-rk3399.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c index

Re: [PATCHv2 5/6] arm64: Use __pa_symbol for _end

On 11/15/2016 10:35 AM, Catalin Marinas wrote: > On Mon, Nov 14, 2016 at 10:41:29AM -0800, Laura Abbott wrote: >> On 11/14/2016 10:19 AM, Catalin Marinas wrote: >>> On Thu, Nov 03, 2016 at 03:51:07PM +, Mark Rutland wrote: On Wed, Nov 02, 2016 at 05:56:42PM -0600, Laura Abbott wrote:

Re: [PATCHv2 5/6] arm64: Use __pa_symbol for _end

On 11/15/2016 10:35 AM, Catalin Marinas wrote: > On Mon, Nov 14, 2016 at 10:41:29AM -0800, Laura Abbott wrote: >> On 11/14/2016 10:19 AM, Catalin Marinas wrote: >>> On Thu, Nov 03, 2016 at 03:51:07PM +, Mark Rutland wrote: On Wed, Nov 02, 2016 at 05:56:42PM -0600, Laura Abbott wrote:

Re: [kernel-hardening] Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

On Tue, Nov 15, 2016 at 3:50 PM, Michael Ellerman wrote: > Kees Cook writes: > >> On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman >> wrote: >>> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used >>> to

Re: [kernel-hardening] Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

On Tue, Nov 15, 2016 at 3:50 PM, Michael Ellerman wrote: > Kees Cook writes: > >> On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman >> wrote: >>> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used >>> to shift poison values so that they don't alias userspace. >>> >>> We

Re: [PATCH 1/2] drivers: usb: phy: Add qoriq usb 3.0 phy driver support

On Mon, Nov 14, 2016 at 10:56:54AM +0530, Sriram Dash wrote: > Adds qoriq usb 3.0 phy driver support for LS1043A platform. > Describes the qoriq usb 2.0 phy driver binding, currently used > for LS1043A platform. > > Signed-off-by: Sriram Dash > --- >

Re: [PATCH 1/2] drivers: usb: phy: Add qoriq usb 3.0 phy driver support

On Mon, Nov 14, 2016 at 10:56:54AM +0530, Sriram Dash wrote: > Adds qoriq usb 3.0 phy driver support for LS1043A platform. > Describes the qoriq usb 2.0 phy driver binding, currently used > for LS1043A platform. > > Signed-off-by: Sriram Dash > --- >

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On Thu, 10 Nov 2016 14:11:57 -0800 Dan Williams wrote: > ZONE_DEVICE pages are mapped into a process via the filesystem-dax and > device-dax mechanisms. There are also proposals to use ZONE_DEVICE > pages for other usages outside of dax. Add statistics to smaps so >

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

On Thu, 10 Nov 2016 14:11:57 -0800 Dan Williams wrote: > ZONE_DEVICE pages are mapped into a process via the filesystem-dax and > device-dax mechanisms. There are also proposals to use ZONE_DEVICE > pages for other usages outside of dax. Add statistics to smaps so > applications can debug

Re: [PATCH/RESEND] recordmcount: arm: Implement make_nop

On 11/15, Ard Biesheuvel wrote: > On 15 November 2016 at 19:18, Stephen Boyd wrote: > > On 11/15, Ard Biesheuvel wrote: > >> On 19 October 2016 at 00:42, Stephen Boyd wrote: > >> > > >> > +static unsigned char ideal_nop4_arm_le[4] = { 0x00, 0x00, 0xa0,

Re: [PATCH/RESEND] recordmcount: arm: Implement make_nop

On 11/15, Ard Biesheuvel wrote: > On 15 November 2016 at 19:18, Stephen Boyd wrote: > > On 11/15, Ard Biesheuvel wrote: > >> On 19 October 2016 at 00:42, Stephen Boyd wrote: > >> > > >> > +static unsigned char ideal_nop4_arm_le[4] = { 0x00, 0x00, 0xa0, 0xe1 }; > >> > /* mov r0, r0 */ > >> >

Re: [kernel-hardening] Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

Kees Cook writes: > On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman wrote: >> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used >> to shift poison values so that they don't alias userspace. >> >> We should add it to

Re: [kernel-hardening] Re: [PATCH] slab: Add POISON_POINTER_DELTA to ZERO_SIZE_PTR

Kees Cook writes: > On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman wrote: >> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used >> to shift poison values so that they don't alias userspace. >> >> We should add it to ZERO_SIZE_PTR so that attackers can't use >>

[PATCH v3 3/8] mm/swap: Split swap cache into 64MB trunks

From: "Huang, Ying" The patch is to improve the scalability of the swap out/in via using fine grained locks for the swap cache. In current kernel, one address space will be used for each swap device. And in the common configuration, the number of the swap device is very

[PATCH v3 4/8] mm/swap: skip read ahead for unreferenced swap slots

We can avoid needlessly allocating page for swap slots that are not used by anyone. No pages have to be read in for these slots. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 6 ++ mm/swap_state.c |

[PATCH v3 3/8] mm/swap: Split swap cache into 64MB trunks

From: "Huang, Ying" The patch is to improve the scalability of the swap out/in via using fine grained locks for the swap cache. In current kernel, one address space will be used for each swap device. And in the common configuration, the number of the swap device is very small (one is typical).

[PATCH v3 4/8] mm/swap: skip read ahead for unreferenced swap slots

We can avoid needlessly allocating page for swap slots that are not used by anyone. No pages have to be read in for these slots. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 6 ++ mm/swap_state.c | 4 mm/swapfile.c| 47

[PATCH v3 8/8] mm/swap: Enable swap slots cache usage

Initialize swap slots cache and enable it on swap on. Drain all swap slots on swap off. Signed-off-by: Tim Chen --- mm/swapfile.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/swapfile.c b/mm/swapfile.c index 0bd105d..9cbdbfc 100644 ---

[PATCH v3 1/8] mm/swap: Fix kernel message in swap_info_get()

From: "Huang, Ying" swap_info_get() is used not only in swap free code path but also in page_swapcount(), etc. So the original kernel message in swap_info_get() is not correct now. Fix it via replacing "swap_free" to "swap_info_get" in the message. Signed-off-by: "Huang,

[PATCH v3 2/8] mm/swap: Add cluster lock

From: "Huang, Ying" This patch is to reduce the lock contention of swap_info_struct->lock via using a more fine grained lock in swap_cluster_info for some swap operations. swap_info_struct->lock is heavily contended if multiple processes reclaim pages simultaneously.

[PATCH v3 7/8] mm/swap: Add cache for swap slots allocation

We add per cpu caches for swap slots that can be allocated and freed quickly without the need to touch the swap info lock. Two separate caches are maintained for swap slots allocated and swap slots returned. This is to allow the swap slots to be returned to the global pool in a batch so they

[PATCH v3 8/8] mm/swap: Enable swap slots cache usage

Initialize swap slots cache and enable it on swap on. Drain all swap slots on swap off. Signed-off-by: Tim Chen --- mm/swapfile.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/swapfile.c b/mm/swapfile.c index 0bd105d..9cbdbfc 100644 --- a/mm/swapfile.c +++ b/mm/swapfile.c @@

[PATCH v3 1/8] mm/swap: Fix kernel message in swap_info_get()

From: "Huang, Ying" swap_info_get() is used not only in swap free code path but also in page_swapcount(), etc. So the original kernel message in swap_info_get() is not correct now. Fix it via replacing "swap_free" to "swap_info_get" in the message. Signed-off-by: "Huang, Ying" Signed-off-by:

[PATCH v3 2/8] mm/swap: Add cluster lock

From: "Huang, Ying" This patch is to reduce the lock contention of swap_info_struct->lock via using a more fine grained lock in swap_cluster_info for some swap operations. swap_info_struct->lock is heavily contended if multiple processes reclaim pages simultaneously. Because there is only one

[PATCH v3 7/8] mm/swap: Add cache for swap slots allocation

We add per cpu caches for swap slots that can be allocated and freed quickly without the need to touch the swap info lock. Two separate caches are maintained for swap slots allocated and swap slots returned. This is to allow the swap slots to be returned to the global pool in a batch so they

[PATCH v3 6/8] mm/swap: Free swap slots in batch

Add new functions that free unused swap slots in batches without the need to reacquire swap info lock. This improves scalability and reduce lock contention. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 1

[PATCH v3 5/8] mm/swap: Allocate swap slots in batches

Currently, the swap slots are allocated one page at a time, causing contention to the swap_info lock protecting the swap partition on every page being swapped. This patch adds new functions get_swap_pages and scan_swap_map_slots to request multiple swap slots at once. This will reduces the lock

[PATCH v3 6/8] mm/swap: Free swap slots in batch

Add new functions that free unused swap slots in batches without the need to reacquire swap info lock. This improves scalability and reduce lock contention. Signed-off-by: Tim Chen Co-developed-by: "Huang, Ying" --- include/linux/swap.h | 1 + mm/swapfile.c| 155

[PATCH v3 5/8] mm/swap: Allocate swap slots in batches

Currently, the swap slots are allocated one page at a time, causing contention to the swap_info lock protecting the swap partition on every page being swapped. This patch adds new functions get_swap_pages and scan_swap_map_slots to request multiple swap slots at once. This will reduces the lock

[PATCH v3 0/8] mm/swap: Regular page swap optimizations

Andrew, It seems like there are no objections to this patch series so far. Can you help us get this patch series to be code reviewed in more depth so it can be considered for inclusion to 4.10? Will appreciate if Mel, Johannes, Rik or others can take a look. We appreciate feedback about this

[PATCH v3 0/8] mm/swap: Regular page swap optimizations

Andrew, It seems like there are no objections to this patch series so far. Can you help us get this patch series to be code reviewed in more depth so it can be considered for inclusion to 4.10? Will appreciate if Mel, Johannes, Rik or others can take a look. We appreciate feedback about this

Re: [PATCH v2 0/3] add ION driver for STIh4xx SoC

On 11/15/2016 03:17 AM, Benjamin Gaignard wrote: > version 2: > - rebased on kernel 4.9-rc5 > - change heap bindings to use definitions of > drivers/staging/android/ion/devicetree.txt > > version 1: > - initial patch > > It is more or less a copy of Hisilicon driver but with a heap definition >

Re: [PATCH v2 0/3] add ION driver for STIh4xx SoC

On 11/15/2016 03:17 AM, Benjamin Gaignard wrote: > version 2: > - rebased on kernel 4.9-rc5 > - change heap bindings to use definitions of > drivers/staging/android/ion/devicetree.txt > > version 1: > - initial patch > > It is more or less a copy of Hisilicon driver but with a heap definition >

Re: [PATCH] mtd: nand: nandsim: fix error check

On 11/16/2016 12:09 AM, Sudip Mukherjee wrote: > debugfs_create_dir() and debugfs_create_file() returns NULL on error or > a pointer on success. They do not return the error value with ERR_PTR. > So we should not check the return with IS_ERR_OR_NULL, instead we > should just check for NULL. > >

Re: [PATCH] mtd: nand: nandsim: fix error check

On 11/16/2016 12:09 AM, Sudip Mukherjee wrote: > debugfs_create_dir() and debugfs_create_file() returns NULL on error or > a pointer on success. They do not return the error value with ERR_PTR. > So we should not check the return with IS_ERR_OR_NULL, instead we > should just check for NULL. > >

Re: [PATCH] kasan: support use-after-scope detection

On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov wrote: > Gcc revision 241896 implements use-after-scope detection. > Will be available in gcc 7. Support it in KASAN. > > Gcc emits 2 new callbacks to poison/unpoison large stack > objects when they go in/out of scope. >

Re: [PATCH] kasan: support use-after-scope detection

On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov wrote: > Gcc revision 241896 implements use-after-scope detection. > Will be available in gcc 7. Support it in KASAN. > > Gcc emits 2 new callbacks to poison/unpoison large stack > objects when they go in/out of scope. > Implement the callbacks

Re: [PATCH 1/2] procfs: use an enum for possible hidepid values

On Thu, Nov 3, 2016 at 8:49 AM, Kees Cook wrote: > On Thu, Nov 3, 2016 at 9:30 AM, Lafcadio Wluiki wrote: >> (Third, rebased submission, since first two submissions yielded no replies.) > > Hm, I didn't see this series before, for some reason. > >>

Re: [PATCH 1/2] procfs: use an enum for possible hidepid values

On Thu, Nov 3, 2016 at 8:49 AM, Kees Cook wrote: > On Thu, Nov 3, 2016 at 9:30 AM, Lafcadio Wluiki wrote: >> (Third, rebased submission, since first two submissions yielded no replies.) > > Hm, I didn't see this series before, for some reason. > >> Previously, the hidepid parameter was checked

Re: [RFC/PATCH 2/2] pstore: Convert console write to use ->write_buf

On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote: > Maybe I'm missing something, but I don't know why it needs to copy the > input buffer to psinfo->buf and then write. Instead we can write the > input buffer directly. The only implementation that supports console >

Re: [RFC/PATCH 2/2] pstore: Convert console write to use ->write_buf

On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote: > Maybe I'm missing something, but I don't know why it needs to copy the > input buffer to psinfo->buf and then write. Instead we can write the > input buffer directly. The only implementation that supports console > message (i.e. ramoops)

Re: [RFC/PATCH 1/2] pstore: Protect unlink with read_mutex

On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote: > When update_ms is set, pstore_get_records() will be called when there's > a new entry. But unlink can be called at the same time and might > contend with the open-read-close loop. Depending on the implementation > of

Re: [RFC/PATCH 1/2] pstore: Protect unlink with read_mutex

On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote: > When update_ms is set, pstore_get_records() will be called when there's > a new entry. But unlink can be called at the same time and might > contend with the open-read-close loop. Depending on the implementation > of platform driver, it may

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

On 16.11.2016 00:03, Andrew Lunn wrote: >> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG | >> > + SLIC_PCR_AUTONEG_RST; >> > + slic_write(sdev, SLIC_REG_WPHY, val); > >> Thats essentially what I meant by setting a

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

On 16.11.2016 00:03, Andrew Lunn wrote: >> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG | >> > + SLIC_PCR_AUTONEG_RST; >> > + slic_write(sdev, SLIC_REG_WPHY, val); > >> Thats essentially what I meant by setting a

linux-next: build warnings after merge of the pinctrl tree

Hi Linus, After merging the pinctrl tree, today's linux-next build (arm_multi_v7_defconfig) produced these warnings: drivers/pinctrl/sunxi/pinctrl-sunxi.c: In function 'sunxi_pinctrl_init': drivers/pinctrl/sunxi/pinctrl-sunxi.c:1191:8: warning: 'best_div' may be used uninitialized in this

linux-next: build warnings after merge of the pinctrl tree

Hi Linus, After merging the pinctrl tree, today's linux-next build (arm_multi_v7_defconfig) produced these warnings: drivers/pinctrl/sunxi/pinctrl-sunxi.c: In function 'sunxi_pinctrl_init': drivers/pinctrl/sunxi/pinctrl-sunxi.c:1191:8: warning: 'best_div' may be used uninitialized in this

[PATCH] mtd: nand: nandsim: fix error check

debugfs_create_dir() and debugfs_create_file() returns NULL on error or a pointer on success. They do not return the error value with ERR_PTR. So we should not check the return with IS_ERR_OR_NULL, instead we should just check for NULL. Signed-off-by: Sudip Mukherjee

[PATCH] mtd: nand: nandsim: fix error check

debugfs_create_dir() and debugfs_create_file() returns NULL on error or a pointer on success. They do not return the error value with ERR_PTR. So we should not check the return with IS_ERR_OR_NULL, instead we should just check for NULL. Signed-off-by: Sudip Mukherjee ---

[PATCH v3] usb: dwc2: add amcc,dwc-otg support

From: Christian Lamparter This patch adds support for the "amcc,usb-otg" device which is found in the PowerPC Canyonlands' dts. The device definition was added by: commit c89b3458d8cc ("powerpc/44x: Add USB DWC DTS entry to Canyonlands board") but without any driver

[PATCH v3] usb: dwc2: add amcc,dwc-otg support

From: Christian Lamparter This patch adds support for the "amcc,usb-otg" device which is found in the PowerPC Canyonlands' dts. The device definition was added by: commit c89b3458d8cc ("powerpc/44x: Add USB DWC DTS entry to Canyonlands board") but without any driver support as the dwc2 driver

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG | > > +SLIC_PCR_AUTONEG_RST; > > + slic_write(sdev, SLIC_REG_WPHY, val); > Thats essentially what I meant by setting a flag in the irq handler. The mdio > function

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG | > > +SLIC_PCR_AUTONEG_RST; > > + slic_write(sdev, SLIC_REG_WPHY, val); > Thats essentially what I meant by setting a flag in the irq handler. The mdio > function

[RFC][PATCH] cpufreq: Support of Energy Performance preference

This change allows user to provide hints to P-State selection algorithm to be more more performance centric or more energy centric. Even if this change only impacts intel_pstate driver, this change is submitted as RFC to check if we need a generic method in cpufreq to support such configuration.

[RFC][PATCH] cpufreq: intel_pstate: Support of energy performance hint using HWP

It is possible to provide hints to the HWP algorithms in the processor to be more performance centric to more energy centric. The scope of these settings is per logical processor, which means that each of the logical processors in the package can be programmed with a different value. One of the

[RFC][PATCH] cpufreq: Support of Energy Performance preference

This change allows user to provide hints to P-State selection algorithm to be more more performance centric or more energy centric. Even if this change only impacts intel_pstate driver, this change is submitted as RFC to check if we need a generic method in cpufreq to support such configuration.

[RFC][PATCH] cpufreq: intel_pstate: Support of energy performance hint using HWP

It is possible to provide hints to the HWP algorithms in the processor to be more performance centric to more energy centric. The scope of these settings is per logical processor, which means that each of the logical processors in the package can be programmed with a different value. One of the

Re: [PATCH v4] media: Driver for Toshiba et8ek8 5MP sensor

Hi Pavel, On Tue, Nov 15, 2016 at 11:54:25AM +0100, Pavel Machek wrote: > Hi! > > > On Tue, Nov 01, 2016 at 12:54:08AM +0200, Sakari Ailus wrote: > > > > > Thanks, this answered half of my questions already. ;-) > > > > :-). > > > > > > > > I'll have to go through the patches, et8ek8 driver is

Re: [PATCH v4] media: Driver for Toshiba et8ek8 5MP sensor

Hi Pavel, On Tue, Nov 15, 2016 at 11:54:25AM +0100, Pavel Machek wrote: > Hi! > > > On Tue, Nov 01, 2016 at 12:54:08AM +0200, Sakari Ailus wrote: > > > > > Thanks, this answered half of my questions already. ;-) > > > > :-). > > > > > > > > I'll have to go through the patches, et8ek8 driver is

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

On 15.11.2016 23:39, Florian Fainelli wrote: > On 11/15/2016 02:34 PM, Lino Sanfilippo wrote: >> On 15.11.2016 22:59, Andrew Lunn wrote: The link state is retrieved by a command to the application processor that is running on the network card. Also the register to set the phy

Re: [net-next 1/2] net: ethernet: slicoss: add slicoss gigabit ethernet driver

On 15.11.2016 23:39, Florian Fainelli wrote: > On 11/15/2016 02:34 PM, Lino Sanfilippo wrote: >> On 15.11.2016 22:59, Andrew Lunn wrote: The link state is retrieved by a command to the application processor that is running on the network card. Also the register to set the phy

Re: [PATCH] irq/affinity: fix irq_create_affinity_masks for the pre_vectors case

On Tue, 15 Nov 2016, Christoph Hellwig wrote: > Adjust the exit condition for assigning the affinity vectors to take the > pre_vectors into account. Otherwise the last vector will get a cpu mask > for all CPUs by accidentally hitting the post_vectors case. > > Signed-off-by: Christoph Hellwig

Re: [PATCH] irq/affinity: fix irq_create_affinity_masks for the pre_vectors case

On Tue, 15 Nov 2016, Christoph Hellwig wrote: > Adjust the exit condition for assigning the affinity vectors to take the > pre_vectors into account. Otherwise the last vector will get a cpu mask > for all CPUs by accidentally hitting the post_vectors case. > > Signed-off-by: Christoph Hellwig

<    1   2   3   4   5   6   7   8   9   10   >