Re: [PATCH v10 01/25] mm: introduce CONFIG_SPECULATIVE_PAGE_FAULT

Hi Laurent, I guess it's good timing to review. Guess LSF/MM goes so might change a lot since then. :) Anyway, I grap a time to review. On Tue, Apr 17, 2018 at 04:33:07PM +0200, Laurent Dufour wrote: > This configuration variable will be used to build the code needed to > handle speculative page

Re: [PATCH v10 01/25] mm: introduce CONFIG_SPECULATIVE_PAGE_FAULT

Hi Laurent, I guess it's good timing to review. Guess LSF/MM goes so might change a lot since then. :) Anyway, I grap a time to review. On Tue, Apr 17, 2018 at 04:33:07PM +0200, Laurent Dufour wrote: > This configuration variable will be used to build the code needed to > handle speculative page

next-20180416 - warnings from 'make tools/perf'

Seeing these warnings. 'diff' tells me that the files are in fact significantly different. Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from latest version at 'include/uapi/linux/kvm.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from

next-20180416 - warnings from 'make tools/perf'

Seeing these warnings. 'diff' tells me that the files are in fact significantly different. Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from latest version at 'include/uapi/linux/kvm.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from

Re: [PATCH 2/6] dmaengine: at_xdmac: simplify getting .drvdata

On Sun, Apr 22, 2018 at 11:14:10AM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Acked-by: Ludovic Desroches

Re: [PATCH 2/6] dmaengine: at_xdmac: simplify getting .drvdata

On Sun, Apr 22, 2018 at 11:14:10AM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Acked-by: Ludovic Desroches Thanks > --- > > Build tested only. buildbot is happy.

Re: [PATCH 1/6] dmaengine: at_hdmac: simplify getting .drvdata

On Sun, Apr 22, 2018 at 11:14:09AM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Acked-by: Ludovic Desroches

Re: [PATCH 1/6] dmaengine: at_hdmac: simplify getting .drvdata

On Sun, Apr 22, 2018 at 11:14:09AM +0200, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang Acked-by: Ludovic Desroches Thanks > --- > > Build tested only. buildbot is

Re: [REVIEW][PATCH 15/22] signal/s390: Use force_sig_fault where appropriate

On Fri, 20 Apr 2018 09:38:04 -0500 "Eric W. Biederman" wrote: > Filling in struct siginfo before calling force_sig_info a tedious and > error prone process, where once in a great while the wrong fields > are filled out, and siginfo has been inconsistently cleared. > >

Re: [REVIEW][PATCH 15/22] signal/s390: Use force_sig_fault where appropriate

On Fri, 20 Apr 2018 09:38:04 -0500 "Eric W. Biederman" wrote: > Filling in struct siginfo before calling force_sig_info a tedious and > error prone process, where once in a great while the wrong fields > are filled out, and siginfo has been inconsistently cleared. > > Simplify this process by

Re: [RFC v2] virtio: support packed ring

On 2018年04月01日 22:12, Tiwei Bie wrote: Hello everyone, This RFC implements packed ring support for virtio driver. The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html Minor changes are needed for the vhost

Re: [RFC v2] virtio: support packed ring

On 2018年04月01日 22:12, Tiwei Bie wrote: Hello everyone, This RFC implements packed ring support for virtio driver. The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html Minor changes are needed for the vhost

[RFC V3 PATCH 5/8] vhost: vhost_put_user() can accept metadata type

We assumes used ring update is the only user for vhost_put_user() in the past. This may not be the case for the incoming packed ring which may update the descriptor ring for used. So introduce a new type parameter. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 14

[RFC V3 PATCH 5/8] vhost: vhost_put_user() can accept metadata type

We assumes used ring update is the only user for vhost_put_user() in the past. This may not be the case for the incoming packed ring which may update the descriptor ring for used. So introduce a new type parameter. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 14 +++--- 1 file

[RFC V3 PATCH 2/8] vhost: hide used ring layout from device

We used to return descriptor head by vhost_get_vq_desc() to device and pass it back to vhost_add_used() and its friends. This exposes the internal used ring layout to device which makes it hard to be extended for e.g packed ring layout. So this patch tries to hide the used ring layout by -

[RFC V3 PATCH 2/8] vhost: hide used ring layout from device

We used to return descriptor head by vhost_get_vq_desc() to device and pass it back to vhost_add_used() and its friends. This exposes the internal used ring layout to device which makes it hard to be extended for e.g packed ring layout. So this patch tries to hide the used ring layout by -

[RFC V3 PATCH 4/8] vhost_net: do not explicitly manipulate vhost_used_elem

Two helpers of setting/getting used len were introduced to avoid explicitly manipulating vhost_used_elem in zerocopy code. This will be used to hide used_elem internals and simplify packed ring implementation. Signed-off-by: Jason Wang --- drivers/vhost/net.c | 11

[RFC V3 PATCH 4/8] vhost_net: do not explicitly manipulate vhost_used_elem

Two helpers of setting/getting used len were introduced to avoid explicitly manipulating vhost_used_elem in zerocopy code. This will be used to hide used_elem internals and simplify packed ring implementation. Signed-off-by: Jason Wang --- drivers/vhost/net.c | 11 +--

[RFC V3 PATCH 6/8] virtio: introduce packed ring defines

Signed-off-by: Jason Wang --- include/uapi/linux/virtio_config.h | 9 + include/uapi/linux/virtio_ring.h | 13 + 2 files changed, 22 insertions(+) diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h index

[RFC V3 PATCH 6/8] virtio: introduce packed ring defines

Signed-off-by: Jason Wang --- include/uapi/linux/virtio_config.h | 9 + include/uapi/linux/virtio_ring.h | 13 + 2 files changed, 22 insertions(+) diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h index 308e209..5903d51 100644 ---

[RFC V3 PATCH 8/8] vhost: event suppression for packed ring

This patch introduces basic support for event suppression aka driver and device area. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c| 170 --- drivers/vhost/vhost.h| 10 ++- include/uapi/linux/virtio_ring.h |

[RFC V3 PATCH 8/8] vhost: event suppression for packed ring

This patch introduces basic support for event suppression aka driver and device area. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c| 170 --- drivers/vhost/vhost.h| 10 ++- include/uapi/linux/virtio_ring.h | 19 + 3 files

[RFC V3 PATCH 7/8] vhost: packed ring support

Signed-off-by: Jason Wang --- drivers/vhost/net.c | 3 +- drivers/vhost/vhost.c | 535 ++ drivers/vhost/vhost.h | 8 +- 3 files changed, 509 insertions(+), 37 deletions(-) diff --git a/drivers/vhost/net.c

[RFC V3 PATCH 7/8] vhost: packed ring support

Signed-off-by: Jason Wang --- drivers/vhost/net.c | 3 +- drivers/vhost/vhost.c | 535 ++ drivers/vhost/vhost.h | 8 +- 3 files changed, 509 insertions(+), 37 deletions(-) diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c index

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

On (01/23/18 07:43), Tejun Heo wrote: > > > > We can have more. But if printk is causing printks, that's a major bug. > > And work queues are not going to fix it, it will just spread out the > > pain. Have it be 100 printks, it needs to be fixed if it is happening. > > And having all printks just

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

On (01/23/18 07:43), Tejun Heo wrote: > > > > We can have more. But if printk is causing printks, that's a major bug. > > And work queues are not going to fix it, it will just spread out the > > pain. Have it be 100 printks, it needs to be fixed if it is happening. > > And having all printks just

[RFC V3 PATCH 1/8] vhost: move get_rx_bufs to vhost.c

Move get_rx_bufs() to vhost.c and rename it to vhost_get_rx_bufs(). This helps to hide vring internal layout from specific device implementation. Packed ring implementation will benefit from this. Signed-off-by: Jason Wang --- drivers/vhost/net.c | 83

[RFC V3 PATCH 0/8] Packed ring for vhost

Hi all: This RFC implement packed ring layout. The code were tested with Tiwei's RFC V2 a thttps://lkml.org/lkml/2018/4/1/48. Some fixups and tweaks were needed on top of Tiwei's code to make it run. TCP stream and pktgen does not show obvious difference compared with split ring. Changes from

[RFC V3 PATCH 1/8] vhost: move get_rx_bufs to vhost.c

Move get_rx_bufs() to vhost.c and rename it to vhost_get_rx_bufs(). This helps to hide vring internal layout from specific device implementation. Packed ring implementation will benefit from this. Signed-off-by: Jason Wang --- drivers/vhost/net.c | 83

[RFC V3 PATCH 0/8] Packed ring for vhost

Hi all: This RFC implement packed ring layout. The code were tested with Tiwei's RFC V2 a thttps://lkml.org/lkml/2018/4/1/48. Some fixups and tweaks were needed on top of Tiwei's code to make it run. TCP stream and pktgen does not show obvious difference compared with split ring. Changes from

[RFC V3 PATCH 3/8] vhost: do not use vring_used_elem

Instead of depending on the exported vring_used_elem, this patch switches to use a new internal structure vhost_used_elem which embed vring_used_elem in itself. This could be used to let vhost to record extra metadata for the incoming packed ring layout. Signed-off-by: Jason Wang

[RFC V3 PATCH 3/8] vhost: do not use vring_used_elem

Instead of depending on the exported vring_used_elem, this patch switches to use a new internal structure vhost_used_elem which embed vring_used_elem in itself. This could be used to let vhost to record extra metadata for the incoming packed ring layout. Signed-off-by: Jason Wang ---

Re: [PATCH v2] fs: dax: Adding new return type vm_fault_t

Hi Souptick, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180420] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] fs: dax: Adding new return type vm_fault_t

Hi Souptick, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180420] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

linux-next: Signed-off-by missing for commit in the hwmon-staging tree

Hi Guenter, Commit bcafe0ea7e4f ("hwmon: MC13783: Add uid and die temperature sensor inputs") is missing a Signed-off-by from its committer. It was rebased since yesterday. -- Cheers, Stephen Rothwell pgplr3KQaJ9HR.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the hwmon-staging tree

Hi Guenter, Commit bcafe0ea7e4f ("hwmon: MC13783: Add uid and die temperature sensor inputs") is missing a Signed-off-by from its committer. It was rebased since yesterday. -- Cheers, Stephen Rothwell pgplr3KQaJ9HR.pgp Description: OpenPGP digital signature

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On (04/20/18 11:12), Petr Mladek wrote: [..] > Will 1000 lines within 1 hour be enough for you, please? I'm afraid it won't. > I am lost. In the mail [..] > My understanding of the older mail is that you called > console_drivers() in printk_safe() context only because it was > easier to disable

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On (04/20/18 11:12), Petr Mladek wrote: [..] > Will 1000 lines within 1 hour be enough for you, please? I'm afraid it won't. > I am lost. In the mail [..] > My understanding of the older mail is that you called > console_drivers() in printk_safe() context only because it was > easier to disable

linux-next: Tree for Apr 23

Hi all, Changes since 20180420: The usb tree gained a conflict against the usb.current tree. Non-merge commits (relative to Linus' tree): 1418 1459 files changed, 55564 insertions(+), 22829 deletions(-) I have

linux-next: Tree for Apr 23

Hi all, Changes since 20180420: The usb tree gained a conflict against the usb.current tree. Non-merge commits (relative to Linus' tree): 1418 1459 files changed, 55564 insertions(+), 22829 deletions(-) I have

Re: [RFC 4/6] dmaengine: xilinx_dma: Freeup active list based on descriptor completion bit

On Tue, Apr 17, 2018 at 12:28:52PM +, Radhey Shyam Pandey wrote: > > > + if ((seg->hw.status & XILINX_DMA_COMP_MASK) || > > > + (!chan->xdev->has_axieth_connected)) { > > > > why the second case ? That is not expalined in log? > In the current implementation, delay

Re: [RFC 4/6] dmaengine: xilinx_dma: Freeup active list based on descriptor completion bit

On Tue, Apr 17, 2018 at 12:28:52PM +, Radhey Shyam Pandey wrote: > > > + if ((seg->hw.status & XILINX_DMA_COMP_MASK) || > > > + (!chan->xdev->has_axieth_connected)) { > > > > why the second case ? That is not expalined in log? > In the current implementation, delay

Re: [PATCH 1/1] arm64: To remove initrd reserved area entry from memblock

Hi, May I know when this patch would be taken for merging? On Sat, Apr 7, 2018 at 9:58 AM, Chandan Vn wrote: > On Fri, Apr 6, 2018 at 9:47 PM, Laura Abbott wrote: >> Does this have an impact on anything besides accounting >> in memblock? > > Yes, the

Re: [PATCH 1/1] arm64: To remove initrd reserved area entry from memblock

Hi, May I know when this patch would be taken for merging? On Sat, Apr 7, 2018 at 9:58 AM, Chandan Vn wrote: > On Fri, Apr 6, 2018 at 9:47 PM, Laura Abbott wrote: >> Does this have an impact on anything besides accounting >> in memblock? > > Yes, the impact is only on accounting or debugging.

Re: BUG: KASAN: global-out-of-bounds in unmap_kernel_at_el0+0x70/0x1a0

On 2018-04-22 21:06, Mark Rutland wrote: > On Sun, Apr 22, 2018 at 12:47:57PM +0200, Jan Kiszka wrote: >> Hi, >> >> this can be triggered simply by running >> >> # echo 0 > /sys/devices/system/cpu/cpu3/online >> # echo 1 > /sys/devices/system/cpu/cpu3/online >> >> [ 455.904854] >>

Re: BUG: KASAN: global-out-of-bounds in unmap_kernel_at_el0+0x70/0x1a0

On 2018-04-22 21:06, Mark Rutland wrote: > On Sun, Apr 22, 2018 at 12:47:57PM +0200, Jan Kiszka wrote: >> Hi, >> >> this can be triggered simply by running >> >> # echo 0 > /sys/devices/system/cpu/cpu3/online >> # echo 1 > /sys/devices/system/cpu/cpu3/online >> >> [ 455.904854] >>

[RFC v3 PATCH] mm: shmem: make stat.st_blksize return huge page size if THP is on

Since tmpfs THP was supported in 4.8, hugetlbfs is not the only filesystem with huge page support anymore. tmpfs can use huge page via THP when mounting by "huge=" mount option. When applications use huge page on hugetlbfs, it just need check the filesystem magic number, but it is not enough for

[RFC v3 PATCH] mm: shmem: make stat.st_blksize return huge page size if THP is on

Since tmpfs THP was supported in 4.8, hugetlbfs is not the only filesystem with huge page support anymore. tmpfs can use huge page via THP when mounting by "huge=" mount option. When applications use huge page on hugetlbfs, it just need check the filesystem magic number, but it is not enough for

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported

On 20-04-18, 09:50, Florian Fainelli wrote: > On 04/20/2018 02:35 AM, Viresh Kumar wrote: > > On 20-04-18, 10:15, Sudeep Holla wrote: > >> It still doesn't give the flexibility to switch between the two > >> implementations boot time based on some firmware config(e.g. DT status > >> property). > >

Re: [PATCH 2/2] cpufreq: brcmstb-avs-cpufreq: prefer SCMI cpufreq if supported

On 20-04-18, 09:50, Florian Fainelli wrote: > On 04/20/2018 02:35 AM, Viresh Kumar wrote: > > On 20-04-18, 10:15, Sudeep Holla wrote: > >> It still doesn't give the flexibility to switch between the two > >> implementations boot time based on some firmware config(e.g. DT status > >> property). > >

Re: [PATCH 2/3] mm: add find_alloc_contig_pages() interface

On 04/22/2018 05:09 PM, Michal Hocko wrote: > On Mon 16-04-18 19:09:14, Mike Kravetz wrote: > [...] >> @@ -2010,9 +2011,13 @@ static __always_inline struct page >> *__rmqueue_cma_fallback(struct zone *zone, >> { >> return __rmqueue_smallest(zone, order, MIGRATE_CMA); >> } >> +#define

Re: [PATCH 2/3] mm: add find_alloc_contig_pages() interface

On 04/22/2018 05:09 PM, Michal Hocko wrote: > On Mon 16-04-18 19:09:14, Mike Kravetz wrote: > [...] >> @@ -2010,9 +2011,13 @@ static __always_inline struct page >> *__rmqueue_cma_fallback(struct zone *zone, >> { >> return __rmqueue_smallest(zone, order, MIGRATE_CMA); >> } >> +#define

Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask

On 22 April 2018 at 23:00, Dmitry Vyukov wrote: > On Sun, Apr 22, 2018 at 2:51 PM, Michal Hocko wrote: >> On Fri 20-04-18 18:50:24, Catalin Marinas wrote: >>> On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote: >>> > __GFP_NORETRY and __GFP_NOFAIL

Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask

On 22 April 2018 at 23:00, Dmitry Vyukov wrote: > On Sun, Apr 22, 2018 at 2:51 PM, Michal Hocko wrote: >> On Fri 20-04-18 18:50:24, Catalin Marinas wrote: >>> On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote: >>> > __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now.

[PATCH 2/5] ARM: dts: imx6sx-sabreauto: add max7322 IO expander support

Add MAX7322 IO expander support. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts b/arch/arm/boot/dts/imx6sx-sabreauto.dts index 2caca934..d59084f 100644

[PATCH 2/5] ARM: dts: imx6sx-sabreauto: add max7322 IO expander support

Add MAX7322 IO expander support. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts b/arch/arm/boot/dts/imx6sx-sabreauto.dts index 2caca934..d59084f 100644 ---

[PATCH 5/5] ARM: dts: imx6sx-sabreauto: add wdog external reset support

i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be MUXed as WDOG output to reset PMIC, add this function support. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 12 1 file changed, 12 insertions(+) diff --git

[PATCH 5/5] ARM: dts: imx6sx-sabreauto: add wdog external reset support

i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be MUXed as WDOG output to reset PMIC, add this function support. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 12 1 file changed, 12 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts

[PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support

Add FEC support on i.MX6SX Sabre Auto board. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 70 ++ 1 file changed, 70 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts

[PATCH 3/5] ARM: dts: imx6sx-sabreauto: add IO expander max7310 support

i.MX6SX Sabre Auto board has two max7310 IO expander on I2C3 bus, add support for them. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 28 1 file changed, 28 insertions(+) diff --git

[PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support

Add FEC support on i.MX6SX Sabre Auto board. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 70 ++ 1 file changed, 70 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts b/arch/arm/boot/dts/imx6sx-sabreauto.dts index

[PATCH 3/5] ARM: dts: imx6sx-sabreauto: add IO expander max7310 support

i.MX6SX Sabre Auto board has two max7310 IO expander on I2C3 bus, add support for them. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 28 1 file changed, 28 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts

[PATCH 1/5] ARM: dts: imx6sx-sabreauto: add PMIC support

Add pfuze100 support on i.MX6SX Sabre Auto board. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 117 + 1 file changed, 117 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts

[PATCH 1/5] ARM: dts: imx6sx-sabreauto: add PMIC support

Add pfuze100 support on i.MX6SX Sabre Auto board. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6sx-sabreauto.dts | 117 + 1 file changed, 117 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts b/arch/arm/boot/dts/imx6sx-sabreauto.dts index

Re: [PATCH 03/24] VFS: Introduce the structs and doc for a filesystem context [ver #7]

Hi David, On 04/19/18 06:31, David Howells wrote: > Introduce a filesystem context concept to be used during superblock > creation for mount and superblock reconfiguration for remount. This is > allocated at the beginning of the mount procedure and into it is placed: > > (1) Filesystem type. >

Re: [PATCH 03/24] VFS: Introduce the structs and doc for a filesystem context [ver #7]

Hi David, On 04/19/18 06:31, David Howells wrote: > Introduce a filesystem context concept to be used during superblock > creation for mount and superblock reconfiguration for remount. This is > allocated at the beginning of the mount procedure and into it is placed: > > (1) Filesystem type. >

Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask

On 21 April 2018 at 01:50, Catalin Marinas wrote: > On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote: >> __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now. >> But it's a wrong combination. As __GFP_NOFAIL is blockable, but >> __GFP_NORETY is

Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask

On 21 April 2018 at 01:50, Catalin Marinas wrote: > On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote: >> __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now. >> But it's a wrong combination. As __GFP_NOFAIL is blockable, but >> __GFP_NORETY is not blockable, make it

Re: [RFC v2 PATCH] mm: shmem: make stat.st_blksize return huge page size if THP is on

On 4/22/18 6:47 PM, Michal Hocko wrote: On Sat 21-04-18 00:33:59, Yang Shi wrote: Since tmpfs THP was supported in 4.8, hugetlbfs is not the only filesystem with huge page support anymore. tmpfs can use huge page via THP when mounting by "huge=" mount option. When applications use huge page

Re: [RFC v2 PATCH] mm: shmem: make stat.st_blksize return huge page size if THP is on

On 4/22/18 6:47 PM, Michal Hocko wrote: On Sat 21-04-18 00:33:59, Yang Shi wrote: Since tmpfs THP was supported in 4.8, hugetlbfs is not the only filesystem with huge page support anymore. tmpfs can use huge page via THP when mounting by "huge=" mount option. When applications use huge page

Re: [RFC v4 3/4] irqflags: Avoid unnecessary calls to trace_ if you can

On Sun, Apr 22, 2018 at 06:14:18PM -0700, Joel Fernandes wrote: > On Fri, Apr 20, 2018 at 12:07 AM, Joel Fernandes wrote: > > Hi, > > > > Thanks Matsami and Namhyung for the suggestions! > > > > On Wed, Apr 18, 2018 at 10:43 PM, Namhyung Kim wrote: > >> On

Re: [RFC v4 3/4] irqflags: Avoid unnecessary calls to trace_ if you can

On Sun, Apr 22, 2018 at 06:14:18PM -0700, Joel Fernandes wrote: > On Fri, Apr 20, 2018 at 12:07 AM, Joel Fernandes wrote: > > Hi, > > > > Thanks Matsami and Namhyung for the suggestions! > > > > On Wed, Apr 18, 2018 at 10:43 PM, Namhyung Kim wrote: > >> On Wed, Apr 18, 2018 at 06:02:50PM +0900,

[PATCH tip/core/rcu 5/6] rcutorture: Abbreviate kvm.sh summary lines

With the addition of the end-of-test state, it is not uncommon for the kvm.sh summary lines to overflow 80 characters. This commit therefore applies abbreviations in order to make the line fit into 80 characters with high probability. And yes, I did make heavy use of punched cards back in the

[PATCH tip/core/rcu 5/6] rcutorture: Abbreviate kvm.sh summary lines

With the addition of the end-of-test state, it is not uncommon for the kvm.sh summary lines to overflow 80 characters. This commit therefore applies abbreviations in order to make the line fit into 80 characters with high probability. And yes, I did make heavy use of punched cards back in the

[PATCH tip/core/rcu 6/6] torture: Make kvm-find-errors.sh find build warnings

Currently, kvm-find-errors.sh looks only for build errors ("error:"), so this commit makes it also locate build warnings ("warning:"). Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | 5 +++-- 1 file changed, 3

[PATCH tip/core/rcu 6/6] torture: Make kvm-find-errors.sh find build warnings

Currently, kvm-find-errors.sh looks only for build errors ("error:"), so this commit makes it also locate build warnings ("warning:"). Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff

[PATCH tip/core/rcu 1/6] torture: Add a script to edit output from failed runs

This commit adds a script that allows viewing the build and/or console output from failed rcutorture, locktorture, or rcuperf runs. This replaces a time-honored but inefficient manual procedure that uses cut and paste. Signed-off-by: Paul E. McKenney ---

[PATCH tip/core/rcu 4/6] rcutorture: Print end-of-test state in kvm.sh summary

This commit adds the end-of-test test, if present in the console output, to the kvm.sh test summary that is printed by kvm-recheck.sh. Note that this only applies to rcutorture console output. Signed-off-by: Paul E. McKenney ---

[PATCH tip/core/rcu 1/6] torture: Add a script to edit output from failed runs

This commit adds a script that allows viewing the build and/or console output from failed rcutorture, locktorture, or rcuperf runs. This replaces a time-honored but inefficient manual procedure that uses cut and paste. Signed-off-by: Paul E. McKenney ---

[PATCH tip/core/rcu 4/6] rcutorture: Print end-of-test state in kvm.sh summary

This commit adds the end-of-test test, if present in the console output, to the kvm.sh test summary that is printed by kvm-recheck.sh. Note that this only applies to rcutorture console output. Signed-off-by: Paul E. McKenney --- tools/testing/selftests/rcutorture/bin/kvm-recheck-rcu.sh | 8

[PATCH tip/core/rcu 2/6] torture: Fold parse-torture.sh into parse-console.sh

The rcutorture scripting scans the console output twice, once to look for various sorts of hangs and again to find warnings and panics. Unfortunately, only the output of the second scan gets written to the console.log.diags file, which can cause hangs to be overlooked. This commit therefore folds

[PATCH tip/core/rcu 3/6] rcutorture: Print end-of-test state

This commit adds end-of-test state printout to help check whether RCU shut down nicely. Note that this printout only helps for flavors of RCU that are not used much by the kernel. In particular, for normal RCU having a grace period in progress is expected behavior. Signed-off-by: Paul E.

[PATCH tip/core/rcu 2/6] torture: Fold parse-torture.sh into parse-console.sh

The rcutorture scripting scans the console output twice, once to look for various sorts of hangs and again to find warnings and panics. Unfortunately, only the output of the second scan gets written to the console.log.diags file, which can cause hangs to be overlooked. This commit therefore folds

[PATCH tip/core/rcu 3/6] rcutorture: Print end-of-test state

This commit adds end-of-test state printout to help check whether RCU shut down nicely. Note that this printout only helps for flavors of RCU that are not used much by the kernel. In particular, for normal RCU having a grace period in progress is expected behavior. Signed-off-by: Paul E.

[PATCH tip/core/rcu 0/6] Torture-test updates for v4.18

Hello! This series contains torture-test updates: 1. Add a script to edit output from failed runs. Running this script takes your editor through the build errors and the various problems in the console output, for each such file, first showing a summary of the

[PATCH tip/core/rcu 0/6] Torture-test updates for v4.18

Hello! This series contains torture-test updates: 1. Add a script to edit output from failed runs. Running this script takes your editor through the build errors and the various problems in the console output, for each such file, first showing a summary of the

[PATCH tip/core/rcu 11/21] rcu: Switch __rcu_process_callbacks() to rcu_accelerate_cbs()

The __rcu_process_callbacks() function currently checks to see if the current CPU needs a grace period and also if there is any other reason to kick off a new grace period. This is one of the fail-safe checks that has been rendered unnecessary by the changes that increase the accuracy of

[PATCH tip/core/rcu 11/21] rcu: Switch __rcu_process_callbacks() to rcu_accelerate_cbs()

The __rcu_process_callbacks() function currently checks to see if the current CPU needs a grace period and also if there is any other reason to kick off a new grace period. This is one of the fail-safe checks that has been rendered unnecessary by the changes that increase the accuracy of

[PATCH tip/core/rcu 02/21] rcu: Make rcu_start_future_gp()'s grace-period check more precise

The rcu_start_future_gp() function uses a sloppy check for a grace period being in progress, which works today because there are a number of code sequences that resolve the resulting races. However, some of these race-resolution code sequences must acquire the root rcu_node structure's ->lock,

linux-next: manual merge of the usb tree with the usb.current tree

Hi Greg, Today's linux-next merge of the usb tree got a conflict in: drivers/usb/core/hcd.c between commit: 63cb03f5c11e ("usb: core: split usb_phy_roothub_{init,alloc}") from the usb.current tree and commit: bc40f5341741 ("USB: core: hcd: drop support for legacy phys") from the usb

[PATCH tip/core/rcu 02/21] rcu: Make rcu_start_future_gp()'s grace-period check more precise

The rcu_start_future_gp() function uses a sloppy check for a grace period being in progress, which works today because there are a number of code sequences that resolve the resulting races. However, some of these race-resolution code sequences must acquire the root rcu_node structure's ->lock,

linux-next: manual merge of the usb tree with the usb.current tree

Hi Greg, Today's linux-next merge of the usb tree got a conflict in: drivers/usb/core/hcd.c between commit: 63cb03f5c11e ("usb: core: split usb_phy_roothub_{init,alloc}") from the usb.current tree and commit: bc40f5341741 ("USB: core: hcd: drop support for legacy phys") from the usb

[PATCH tip/core/rcu 09/21] rcu: Make rcu_migrate_callbacks wake GP kthread when needed

The rcu_migrate_callbacks() function invokes rcu_advance_cbs() twice, ignoring the return value. This is OK at pressent because of failsafe code that does the wakeup when needed. However, this failsafe code acquires the root rcu_node structure's lock frequently, while rcu_migrate_callbacks()

[PATCH tip/core/rcu 09/21] rcu: Make rcu_migrate_callbacks wake GP kthread when needed

The rcu_migrate_callbacks() function invokes rcu_advance_cbs() twice, ignoring the return value. This is OK at pressent because of failsafe code that does the wakeup when needed. However, this failsafe code acquires the root rcu_node structure's lock frequently, while rcu_migrate_callbacks()

[PATCH tip/core/rcu 08/21] rcu: Convert ->need_future_gp[] array to boolean

There is no longer any need for ->need_future_gp[] to count the number of requests for future grace periods, so this commit converts the additions to assignments to "true" and reduces the size of each element to one byte. While we are in the area, fix an obsolete comment. Signed-off-by: Paul E.

[PATCH tip/core/rcu 08/21] rcu: Convert ->need_future_gp[] array to boolean

There is no longer any need for ->need_future_gp[] to count the number of requests for future grace periods, so this commit converts the additions to assignments to "true" and reduces the size of each element to one byte. While we are in the area, fix an obsolete comment. Signed-off-by: Paul E.

[PATCH tip/core/rcu 03/21] rcu: Add accessor macros for the ->need_future_gp[] array

Accessors for the ->need_future_gp[] array are currently open-coded, which makes them difficult to change. To improve maintainability, this commit adds need_future_gp_mask() to compute the indexing mask from the array size, need_future_gp_element() to access the element corresponding to the

[PATCH tip/core/rcu 07/21] rcu: Make rcu_future_needs_gp() check all ->need_future_gps[] elements

Currently, the rcu_future_needs_gp() function checks only the current element of the ->need_future_gps[] array, which might miss elements that were offset from the expected element, for example, due to races with the start or the end of a grace period. This commit therefore makes

[PATCH tip/core/rcu 03/21] rcu: Add accessor macros for the ->need_future_gp[] array

Accessors for the ->need_future_gp[] array are currently open-coded, which makes them difficult to change. To improve maintainability, this commit adds need_future_gp_mask() to compute the indexing mask from the array size, need_future_gp_element() to access the element corresponding to the

[PATCH tip/core/rcu 07/21] rcu: Make rcu_future_needs_gp() check all ->need_future_gps[] elements

Currently, the rcu_future_needs_gp() function checks only the current element of the ->need_future_gps[] array, which might miss elements that were offset from the expected element, for example, due to races with the start or the end of a grace period. This commit therefore makes

  1   2   3   4   5   6   7   8   9   10   >