Observing Softlockup's while running heavy IOs

Hi, Problem statement: Observing softlockups while running heavy IOs on 8 SSD drives connected behind our LSI SAS 3004 HBA. System configuration: OS & kernel version: Fedora 23, v4.2.3-300.fc23.x86_64 NUMA : disabled, CPUs : 24 logical cpus, SCSI_MQ: enabled Driver : mpt3sas, MSIx vectors: we

Observing Softlockup's while running heavy IOs

Hi, Problem statement: Observing softlockups while running heavy IOs on 8 SSD drives connected behind our LSI SAS 3004 HBA. System configuration: OS & kernel version: Fedora 23, v4.2.3-300.fc23.x86_64 NUMA : disabled, CPUs : 24 logical cpus, SCSI_MQ: enabled Driver : mpt3sas, MSIx vectors: we

[x86/uaccess] 5b710f34e1: kernel BUG at mm/usercopy.c:75!

kp-wsx03-quantal-i386-6/boot-1-quantal-core-i386.cgz-5b710f34e194c6b7710f69fdb5d798fdf35b98c1-20160817-52554-1cf9h0a-0.yaml ARCH=i386 kconfig=i386-randconfig-w0-08170631 branch=linus/master commit=5b710f34e194c6b7710f69fdb5d798fdf35b98c1 BOOT_IMAGE=/pkg/linux/i386-randconfig-w0-08170631/gcc-6/5b710f34e194c6b7710f69fdb5d798fdf

[x86/uaccess] 5b710f34e1: kernel BUG at mm/usercopy.c:75!

kp-wsx03-quantal-i386-6/boot-1-quantal-core-i386.cgz-5b710f34e194c6b7710f69fdb5d798fdf35b98c1-20160817-52554-1cf9h0a-0.yaml ARCH=i386 kconfig=i386-randconfig-w0-08170631 branch=linus/master commit=5b710f34e194c6b7710f69fdb5d798fdf35b98c1 BOOT_IMAGE=/pkg/linux/i386-randconfig-w0-08170631/gcc-6/5b710f34e194c6b7710f69fdb5d798fdf

Re: [PATCH 2/2] dt-binding: remoteproc: Introduce ADSP loader binding

On Wed 17 Aug 10:27 PDT 2016, Bjorn Andersson wrote: > This document defines the binding for a component that loads firmware > and control the life cycle of the Qualcomm ADSP core. > > Signed-off-by: Bjorn Andersson > --- >

Re: [PATCH 2/2] dt-binding: remoteproc: Introduce ADSP loader binding

On Wed 17 Aug 10:27 PDT 2016, Bjorn Andersson wrote: > This document defines the binding for a component that loads firmware > and control the life cycle of the Qualcomm ADSP core. > > Signed-off-by: Bjorn Andersson > --- > .../devicetree/bindings/remoteproc/qcom,adsp.txt | 69 >

[PATCH v2 1/2] include: trace: Display names of shrinker callbacks

This patch enables the names of callbacks in mm_shrink_slab_start and mm_shrink_slab_end to be seen by userspace tools. This should give some information regarding the identity of the shrinkers being run. Signed-off-by: Janani Ravichandran ---

[PATCH v2 1/2] include: trace: Display names of shrinker callbacks

This patch enables the names of callbacks in mm_shrink_slab_start and mm_shrink_slab_end to be seen by userspace tools. This should give some information regarding the identity of the shrinkers being run. Signed-off-by: Janani Ravichandran --- include/trace/events/vmscan.h | 18

[PATCH v2 0/2] Get callbacks/names of shrinkers from tracepoints

Currently, it is not possible to know which shrinkers are being run. Even though the callbacks are printed using %pF in tracepoints mm_shrink_slab_start and mm_shrink_slab_end, they are not visible to userspace tools like perf. To address this, this patchset 1. Enables the display of names of

[PATCH v2 0/2] Get callbacks/names of shrinkers from tracepoints

Currently, it is not possible to know which shrinkers are being run. Even though the callbacks are printed using %pF in tracepoints mm_shrink_slab_start and mm_shrink_slab_end, they are not visible to userspace tools like perf. To address this, this patchset 1. Enables the display of names of

Re: [PATCH] Add Ingenic JZ4780 hardware RNG driver

> I have just some minor comments below Appreciate your review. >> diff --git a/drivers/char/hw_random/jz4780-rng.c >> b/drivers/char/hw_random/jz4780-rng.c >> new file mode 100644 >> index 000..c9d2cde >> --- /dev/null >> +++ b/drivers/char/hw_random/jz4780-rng.c >> @@ -0,0 +1,105 @@ >>

Re: [PATCH] Add Ingenic JZ4780 hardware RNG driver

> I have just some minor comments below Appreciate your review. >> diff --git a/drivers/char/hw_random/jz4780-rng.c >> b/drivers/char/hw_random/jz4780-rng.c >> new file mode 100644 >> index 000..c9d2cde >> --- /dev/null >> +++ b/drivers/char/hw_random/jz4780-rng.c >> @@ -0,0 +1,105 @@ >>

Re: [PATCH v2 1/3] dt-bindings: thermal: Add binding document for Mediatek thermal controller

On Thursday 18 August 2016 09:20 AM, Dawei Chien wrote: This adds the device tree binding documentation for the mediatek thermal controller found on Mediatek MT2701. Reviewed-by: Keerthy Signed-off-by: Dawei Chien ---

Re: [PATCH v2 1/3] dt-bindings: thermal: Add binding document for Mediatek thermal controller

On Thursday 18 August 2016 09:20 AM, Dawei Chien wrote: This adds the device tree binding documentation for the mediatek thermal controller found on Mediatek MT2701. Reviewed-by: Keerthy Signed-off-by: Dawei Chien --- .../bindings/thermal/mediatek-thermal.txt |4 +++- 1

linux-next: Tree for Aug 18

Hi all, Changes since 20160817: New tree: vfs-miklos Removed trees: powerpc-merge-mpe, powerpc-mpe (no longer used) The netfilter-next tree gained a build failure so I used the version from next-20160817. The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit

linux-next: Tree for Aug 18

Hi all, Changes since 20160817: New tree: vfs-miklos Removed trees: powerpc-merge-mpe, powerpc-mpe (no longer used) The netfilter-next tree gained a build failure so I used the version from next-20160817. The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit

Re: perf: fuzzer: spinlock hang

On Wed, 17 Aug 2016, Peter Zijlstra wrote: > On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote: > > > > So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the > > system finally locked up permanently. > > > > It looks like some sort of spinlock error. > > The logs

Re: perf: fuzzer: spinlock hang

On Wed, 17 Aug 2016, Peter Zijlstra wrote: > On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote: > > > > So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the > > system finally locked up permanently. > > > > It looks like some sort of spinlock error. > > The logs

[PATCH] fib_trie: Fix the description of pos and bits

1) Fix one typo: s/tn/tp/ 2) Fix the description about the "u" bits. Signed-off-by: Xunlei Pang --- net/ipv4/fib_trie.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/ipv4/fib_trie.c b/net/ipv4/fib_trie.c index d07fc07..eb7c5d1 100644 ---

[PATCH] fib_trie: Fix the description of pos and bits

1) Fix one typo: s/tn/tp/ 2) Fix the description about the "u" bits. Signed-off-by: Xunlei Pang --- net/ipv4/fib_trie.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/ipv4/fib_trie.c b/net/ipv4/fib_trie.c index d07fc07..eb7c5d1 100644 --- a/net/ipv4/fib_trie.c +++

Re: perf: rdpmc and PERF_EVENT_IOC_RESET

On Wed, 17 Aug 2016, Peter Zijlstra wrote: > Hurm.. I never considered using RESET with rdpmc(). The typical usage of > rdpmc() I considered is something like: I'm finally trying to hook up PAPI to properly use rdpmc and PAPI likes to use IOC_RESET in various places. I can just special case to

Re: perf: rdpmc and PERF_EVENT_IOC_RESET

On Wed, 17 Aug 2016, Peter Zijlstra wrote: > Hurm.. I never considered using RESET with rdpmc(). The typical usage of > rdpmc() I considered is something like: I'm finally trying to hook up PAPI to properly use rdpmc and PAPI likes to use IOC_RESET in various places. I can just special case to

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Wed, Aug 17, 2016 at 08:54:11PM -0700, Huang, Ying wrote: > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology >

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Wed, Aug 17, 2016 at 08:54:11PM -0700, Huang, Ying wrote: > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology >

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On August 17, 2016 8:45:13 PM PDT, Borislav Petkov wrote: >On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: >> branch-miss-rate decreased from ~0.30% to ~0.043%. >> >> So I guess there are some code alignment change, which caused >decreased >> branch miss rate. > >Hrrm,

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On August 17, 2016 8:45:13 PM PDT, Borislav Petkov wrote: >On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: >> branch-miss-rate decreased from ~0.30% to ~0.043%. >> >> So I guess there are some code alignment change, which caused >decreased >> branch miss rate. > >Hrrm, I still can't

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

Borislav Petkov writes: > On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: >> branch-miss-rate decreased from ~0.30% to ~0.043%. >> >> So I guess there are some code alignment change, which caused decreased >> branch miss rate. > > Hrrm, I still can't imagine how that

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

Borislav Petkov writes: > On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: >> branch-miss-rate decreased from ~0.30% to ~0.043%. >> >> So I guess there are some code alignment change, which caused decreased >> branch miss rate. > > Hrrm, I still can't imagine how that would happen

[PATCH v2 0/3] Add Mediatek thermal driver for mt2701

This series support for mt2701 chip to mtk_thermal.c, and integrate both mt8173 and mt2701 on the same driver. MT8173 has four banks and five sensors, and MT2701 has only one bank and three sensors. Change since V1: 1. Restore macro name with MT8173 for nvmem calibration data since original macro

ptrace group stop signal number not reset before PTRACE_INTERRUPT is delivered?

Consider below test case (not all of it is necessary for reproducing the behavior in question, but I wanted to cover related cases as well to make sure they behave as expected). In this test case, the last group-stop (after PTRACE_INTERRUPT) is delivered with a WSTOPSIG(status) of SIGTTIN, which

[PATCH v2 1/3] dt-bindings: thermal: Add binding document for Mediatek thermal controller

This adds the device tree binding documentation for the mediatek thermal controller found on Mediatek MT2701. Signed-off-by: Dawei Chien --- .../bindings/thermal/mediatek-thermal.txt |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH v2 0/3] Add Mediatek thermal driver for mt2701

This series support for mt2701 chip to mtk_thermal.c, and integrate both mt8173 and mt2701 on the same driver. MT8173 has four banks and five sensors, and MT2701 has only one bank and three sensors. Change since V1: 1. Restore macro name with MT8173 for nvmem calibration data since original macro

ptrace group stop signal number not reset before PTRACE_INTERRUPT is delivered?

Consider below test case (not all of it is necessary for reproducing the behavior in question, but I wanted to cover related cases as well to make sure they behave as expected). In this test case, the last group-stop (after PTRACE_INTERRUPT) is delivered with a WSTOPSIG(status) of SIGTTIN, which

[PATCH v2 1/3] dt-bindings: thermal: Add binding document for Mediatek thermal controller

This adds the device tree binding documentation for the mediatek thermal controller found on Mediatek MT2701. Signed-off-by: Dawei Chien --- .../bindings/thermal/mediatek-thermal.txt |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH v2 2/3] thermal: Add Mediatek thermal driver for mt2701.

This patch adds support for mt2701 chip to mtk_thermal, and integrate both mt8173 and mt2701 on the same driver. MT8173 has four banks and five sensors, and MT2701 has only one bank and three sensors. Signed-off-by: Dawei Chien --- This patch dependents on "Add clock

[PATCH v2 3/3] arm: dts: thermal: add thermal/auxadc node.

This adds the thermal controller and auxadc nodes to the Mediatek MT2701 dtsi file. Signed-off-by: Dawei Chien --- This patch depned on: https://patchwork.kernel.org/patch/9249589/ --- arch/arm/boot/dts/mt2701.dtsi | 44 + 1

[PATCH v2 3/3] arm: dts: thermal: add thermal/auxadc node.

This adds the thermal controller and auxadc nodes to the Mediatek MT2701 dtsi file. Signed-off-by: Dawei Chien --- This patch depned on: https://patchwork.kernel.org/patch/9249589/ --- arch/arm/boot/dts/mt2701.dtsi | 44 + 1 file changed, 44

[PATCH v2 2/3] thermal: Add Mediatek thermal driver for mt2701.

This patch adds support for mt2701 chip to mtk_thermal, and integrate both mt8173 and mt2701 on the same driver. MT8173 has four banks and five sensors, and MT2701 has only one bank and three sensors. Signed-off-by: Dawei Chien --- This patch dependents on "Add clock support for Mediatek

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: > branch-miss-rate decreased from ~0.30% to ~0.043%. > > So I guess there are some code alignment change, which caused decreased > branch miss rate. Hrrm, I still can't imagine how that would happen if the machine supports POPCNT and

Re: [LKP] [lkp] [x86/hweight] 65ea11ec6a: will-it-scale.per_process_ops 9.3% improvement

On Wed, Aug 17, 2016 at 03:29:04PM -0700, Huang, Ying wrote: > branch-miss-rate decreased from ~0.30% to ~0.043%. > > So I guess there are some code alignment change, which caused decreased > branch miss rate. Hrrm, I still can't imagine how that would happen if the machine supports POPCNT and

RE: Support for configurable PCIe endpoint

> -Original Message- > From: Kishon Vijay Abraham I [mailto:kis...@ti.com] > Sent: Thursday, August 04, 2016 6:02 PM > To: Joao Pinto ; bhelg...@google.com; linux- > p...@vger.kernel.org; a...@arndb.de; Jingoo Han ; > Pratyush Anand

RE: Support for configurable PCIe endpoint

> -Original Message- > From: Kishon Vijay Abraham I [mailto:kis...@ti.com] > Sent: Thursday, August 04, 2016 6:02 PM > To: Joao Pinto ; bhelg...@google.com; linux- > p...@vger.kernel.org; a...@arndb.de; Jingoo Han ; > Pratyush Anand > Cc: Ley Foon Tan ; Rob Herring ; > Tanmay Inamdar ;

Re: [PATCH] zram: clean up valid_io_request

Hi, On (08/18/16 11:08), Shawn Lin wrote: [..] > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c > index 04365b1..1094e95 100644 > --- a/drivers/block/zram/zram_drv.c > +++ b/drivers/block/zram/zram_drv.c > @@ -120,15 +120,15 @@ static inline bool

Re: Context switch latency in tickless isolated CPU

Hi Chris, Thanks for your reply. Is the increased time fixed in each context switch? Because this increased time will be the latency of the real time application, we hope to confirm it. Thanks. Regards, - Kang On Wed, Aug 17, 2016 at 8:18 PM, Chris Metcalf wrote: >

Re: [PATCH] zram: clean up valid_io_request

Hi, On (08/18/16 11:08), Shawn Lin wrote: [..] > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c > index 04365b1..1094e95 100644 > --- a/drivers/block/zram/zram_drv.c > +++ b/drivers/block/zram/zram_drv.c > @@ -120,15 +120,15 @@ static inline bool

Re: Context switch latency in tickless isolated CPU

Hi Chris, Thanks for your reply. Is the increased time fixed in each context switch? Because this increased time will be the latency of the real time application, we hope to confirm it. Thanks. Regards, - Kang On Wed, Aug 17, 2016 at 8:18 PM, Chris Metcalf wrote: > On 8/17/2016 2:26 AM,

Re: [LKP] [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2% regression

On Thu, Aug 18, 2016 at 02:06:50AM +0800, Xin Long wrote: > > > > It doesn't seem memory is an issue. > > > > The whole dump is about the same. > > The MemFree and MemAvailable doesn't change much. > > > Hi, Aaron > > 1) > I talked with Marcelo about this one. > He said it might be related with

Re: [LKP] [lkp] [sctp] a6c2f79287: netperf.Throughput_Mbps -37.2% regression

On Thu, Aug 18, 2016 at 02:06:50AM +0800, Xin Long wrote: > > > > It doesn't seem memory is an issue. > > > > The whole dump is about the same. > > The MemFree and MemAvailable doesn't change much. > > > Hi, Aaron > > 1) > I talked with Marcelo about this one. > He said it might be related with

[PATCH v9 0/2] update the doc of kdump

v8->v9: rearrange the patch. it won't fix typo which original exists. those should be fixed in other patch, which I'll post later. v7->v8: fix "a SMP kernel" to "an SMP kernel" and replace "\" with "/" v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to

[PATCH v9 0/2] update the doc of kdump

v8->v9: rearrange the patch. it won't fix typo which original exists. those should be fixed in other patch, which I'll post later. v7->v8: fix "a SMP kernel" to "an SMP kernel" and replace "\" with "/" v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to

[PATCH] zram: clean up valid_io_request

Use IS_ALIGNED instead of opencoding to check the unaligned case. And size is aligned to ZRAM_LOGICAL_BLOCK_SIZE which will not make end <= start, so we do not need to compare the start and end. Signed-off-by: Shawn Lin --- drivers/block/zram/zram_drv.c | 6 +++--- 1

[PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH] zram: clean up valid_io_request

Use IS_ALIGNED instead of opencoding to check the unaligned case. And size is aligned to ZRAM_LOGICAL_BLOCK_SIZE which will not make end <= start, so we do not need to compare the start and end. Signed-off-by: Shawn Lin --- drivers/block/zram/zram_drv.c | 6 +++--- 1 file changed, 3

[PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt index

[PATCH v9 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang ---

[PATCH v9 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 7 +++ 1 file changed, 7

[git pull] drm fixes

Hi Linus, Pretty quiet so far, a few amdgpu/radeon fixup for pcie pm changes, and a couple of amdgpu fixes, along with some build fixes, and printk fix. Dave. The following changes since commit 4b9eaf33d83d91430b7ca45d0ebf8241da489c92: Merge branch 'akpm' (patches from Andrew) (2016-08-11

[git pull] drm fixes

Hi Linus, Pretty quiet so far, a few amdgpu/radeon fixup for pcie pm changes, and a couple of amdgpu fixes, along with some build fixes, and printk fix. Dave. The following changes since commit 4b9eaf33d83d91430b7ca45d0ebf8241da489c92: Merge branch 'akpm' (patches from Andrew) (2016-08-11

Re: [PATCH v9 4/4] arm64: dts: rockchip: configure usb2-phy support for rk3399-evb

On 2016/8/17 18:02, Heiko Stübner wrote: Am Freitag, 22. Juli 2016, 15:00:46 schrieb Frank Wang: Add vcc5v0_host regulator for usb2-phy and enable host-port support. Signed-off-by: Frank Wang applied to ny dts64 branch [0] with some changes: - the pin is named

Re: [PATCH v9 4/4] arm64: dts: rockchip: configure usb2-phy support for rk3399-evb

On 2016/8/17 18:02, Heiko Stübner wrote: Am Freitag, 22. Juli 2016, 15:00:46 schrieb Frank Wang: Add vcc5v0_host regulator for usb2-phy and enable host-port support. Signed-off-by: Frank Wang applied to ny dts64 branch [0] with some changes: - the pin is named vcc5v0_host_en not

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

On Wed, Aug 17, 2016 at 04:49:07PM +0100, Mel Gorman wrote: > On Tue, Aug 16, 2016 at 10:47:36AM -0700, Linus Torvalds wrote: > > I've always preferred to see direct reclaim as the primary model for > > reclaim, partly in order to throttle the actual "bad" process, but > > also because "kswapd

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

On Wed, Aug 17, 2016 at 04:49:07PM +0100, Mel Gorman wrote: > On Tue, Aug 16, 2016 at 10:47:36AM -0700, Linus Torvalds wrote: > > I've always preferred to see direct reclaim as the primary model for > > reclaim, partly in order to throttle the actual "bad" process, but > > also because "kswapd

Re: [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus

On Thu, 2016-08-18 at 10:31 +0800, Zhou Wenjian wrote: > nr_cpus can help to save memory. So we should remind user of it. trivia: > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt [] > @@ -390,9 +390,11 @@ Notes on loading the dump-capture kernel: >  * Boot parameter

Re: [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus

On Thu, 2016-08-18 at 10:31 +0800, Zhou Wenjian wrote: > nr_cpus can help to save memory. So we should remind user of it. trivia: > diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt [] > @@ -390,9 +390,11 @@ Notes on loading the dump-capture kernel: >  * Boot parameter

Re: [PATCH 15/15] block: Add FIXME comment to handle device_add_disk error

On (08/17/16 15:15), Fam Zheng wrote: [..] > ( > rc = device_add_disk(e1, e2, e3); > | > + /* FIXME: handle error. */ > device_add_disk(e1, e2, e3); or use __must_check for device_add_disk() function? /* which is _attribute__((warn_unused_result)) */ -ss

Re: [PATCH 15/15] block: Add FIXME comment to handle device_add_disk error

On (08/17/16 15:15), Fam Zheng wrote: [..] > ( > rc = device_add_disk(e1, e2, e3); > | > + /* FIXME: handle error. */ > device_add_disk(e1, e2, e3); or use __must_check for device_add_disk() function? /* which is _attribute__((warn_unused_result)) */ -ss

[PATCH v8 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang ---

[PATCH v8 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 7 +++ 1 file changed, 7

[PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)

[PATCH v8 0/2] update the doc of kdump

v7->v8: fix "a SMP kernel" to "an SMP kernel" and replace "\" with "/" v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to cover letter v3->v4: update the description of bring up SMP dump-capture kernel v2->v3: add description of nr_cpus. v1->v2: change nr_cpus to maxcpus

[PATCH v8 0/2] update the doc of kdump

v7->v8: fix "a SMP kernel" to "an SMP kernel" and replace "\" with "/" v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to cover letter v3->v4: update the description of bring up SMP dump-capture kernel v2->v3: add description of nr_cpus. v1->v2: change nr_cpus to maxcpus

[PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He Acked-by: Xunlei Pang --- Documentation/kdump/kdump.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/kdump/kdump.txt

Re: [PATCH v3 0/4] Amlogic: Meson: Add reset controller

On Wed, Aug 17, 2016 at 9:15 PM, Kevin Hilman wrote: > Hi Philipp, > > On Thu, Jun 2, 2016 at 2:42 AM, Philipp Zabel wrote: >> Hi Neil, >> >> Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong: >>> Patchset to add and enable the reset

Re: [PATCH v3 0/4] Amlogic: Meson: Add reset controller

On Wed, Aug 17, 2016 at 9:15 PM, Kevin Hilman wrote: > Hi Philipp, > > On Thu, Jun 2, 2016 at 2:42 AM, Philipp Zabel wrote: >> Hi Neil, >> >> Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong: >>> Patchset to add and enable the reset controller driver on Meson SoCs >>> platforms.

Re: [PATCH v10 1/2] printk: Make printk() completely async

Hello, really sorry for very long reply. On (08/12/16 11:44), Petr Mladek wrote: [..] > IMHO, this is fine. We force the synchronous mode in critical > situations anyway. yes, I think it makes sense to lower the priority (we also have briefly discussed this in private emails with Viresh). I'd

Re: [PATCH v10 1/2] printk: Make printk() completely async

Hello, really sorry for very long reply. On (08/12/16 11:44), Petr Mladek wrote: [..] > IMHO, this is fine. We force the synchronous mode in critical > situations anyway. yes, I think it makes sense to lower the priority (we also have briefly discussed this in private emails with Viresh). I'd

Fast Loans

Apply for a loan at 2% reply to this Email for more Info

Fast Loans

Apply for a loan at 2% reply to this Email for more Info

Re: [PATCH] time: alarmtimer: Add the trcepoints for alarmtimer

Hi John, On 18 August 2016 at 04:00, John Stultz wrote: > On Fri, Aug 12, 2016 at 2:16 AM, Baolin Wang wrote: >> For system debugging, we usually want to know who sets one alarm timer, the >> time of the timer, when the timer started and fired and

Re: [PATCH] time: alarmtimer: Add the trcepoints for alarmtimer

Hi John, On 18 August 2016 at 04:00, John Stultz wrote: > On Fri, Aug 12, 2016 at 2:16 AM, Baolin Wang wrote: >> For system debugging, we usually want to know who sets one alarm timer, the >> time of the timer, when the timer started and fired and so on. >> >> Thus adding tracepoints can help

Re: [PATCH v3 0/4] Amlogic: Meson: Add reset controller

Hi Philipp, On Thu, Jun 2, 2016 at 2:42 AM, Philipp Zabel wrote: > Hi Neil, > > Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong: >> Patchset to add and enable the reset controller driver on Meson SoCs >> platforms. >> >> This reset controller has up to 256

Re: [PATCH v3 0/4] Amlogic: Meson: Add reset controller

Hi Philipp, On Thu, Jun 2, 2016 at 2:42 AM, Philipp Zabel wrote: > Hi Neil, > > Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong: >> Patchset to add and enable the reset controller driver on Meson SoCs >> platforms. >> >> This reset controller has up to 256 reset lines with reset

Re: [PATCH v7 2/2] Documentation: kdump: add description of enable multi-cpus support

On 2016/08/18 at 09:50, Zhou Wenjian wrote: > multi-cpu support is useful to improve the performance of kdump in > some cases. So add the description of enable multi-cpu support in > dump-capture kernel. > > Signed-off-by: Zhou Wenjian > Acked-by: Baoquan He

Re: [PATCH v7 2/2] Documentation: kdump: add description of enable multi-cpus support

On 2016/08/18 at 09:50, Zhou Wenjian wrote: > multi-cpu support is useful to improve the performance of kdump in > some cases. So add the description of enable multi-cpu support in > dump-capture kernel. > > Signed-off-by: Zhou Wenjian > Acked-by: Baoquan He > --- >

Re: [PATCH 11/15] zram: Pass attribute group to device_add_disk

On (08/18/16 10:59), Sergey Senozhatsky wrote: [..] > I like the previous "Error creating sysfs group for device" string better, > than "Error creating disk", because the latter one is much less informative. > > do you want to do something like below? > > int device_add_disk(struct device

Re: [PATCH 11/15] zram: Pass attribute group to device_add_disk

On (08/18/16 10:59), Sergey Senozhatsky wrote: [..] > I like the previous "Error creating sysfs group for device" string better, > than "Error creating disk", because the latter one is much less informative. > > do you want to do something like below? > > int device_add_disk(struct device

Re: [PATCH 11/15] zram: Pass attribute group to device_add_disk

Hello, On (08/17/16 15:15), Fam Zheng wrote: [..] > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c > index 20920a2..2331788 100644 > --- a/drivers/block/zram/zram_drv.c > +++ b/drivers/block/zram/zram_drv.c > @@ -1298,13 +1298,10 @@ static int zram_add(void) >

Re: [PATCH 11/15] zram: Pass attribute group to device_add_disk

Hello, On (08/17/16 15:15), Fam Zheng wrote: [..] > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c > index 20920a2..2331788 100644 > --- a/drivers/block/zram/zram_drv.c > +++ b/drivers/block/zram/zram_drv.c > @@ -1298,13 +1298,10 @@ static int zram_add(void) >

linux-next: build failure after merge of the netfilter-next tree

_ipv4.ko] undefined! Caused by commit adf0516845bc ("netfilter: remove ip_conntrack* sysctl compat code") or maybe 92e47ba8839b ("netfilter: conntrack: simplify the code by using nf_conntrack_get_ht") I have used the netfilter-next tree from next-20160817 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the netfilter-next tree

_ipv4.ko] undefined! Caused by commit adf0516845bc ("netfilter: remove ip_conntrack* sysctl compat code") or maybe 92e47ba8839b ("netfilter: conntrack: simplify the code by using nf_conntrack_get_ht") I have used the netfilter-next tree from next-20160817 for today. -- Cheers, Stephen Rothwell

[PATCH v7 0/2] update the doc of kdump

v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to cover letter v3->v4: update the description of bring up SMP dump-capture kernel v2->v3: add description of nr_cpus. v1->v2: change nr_cpus to maxcpus Zhou Wenjian (2): Documentation: kdump: remind user of nr_cpus

[PATCH v7 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He --- Documentation/kdump/kdump.txt | 2 +++- 1 file changed, 2 insertions(+) diff --git a/Documentation/kdump/kdump.txt

[PATCH v7 0/2] update the doc of kdump

v6->v7: fix typo v5->v6: replace "we" with "you" v4->v5: move change log to cover letter v3->v4: update the description of bring up SMP dump-capture kernel v2->v3: add description of nr_cpus. v1->v2: change nr_cpus to maxcpus Zhou Wenjian (2): Documentation: kdump: remind user of nr_cpus

[PATCH v7 1/2] Documentation: kdump: remind user of nr_cpus

nr_cpus can help to save memory. So we should remind user of it. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He --- Documentation/kdump/kdump.txt | 2 +++- 1 file changed, 2 insertions(+) diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt index 88ff63d..96da2b7

[PATCH v7 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He --- Documentation/kdump/kdump.txt | 7 +++

[PATCH v7 2/2] Documentation: kdump: add description of enable multi-cpus support

multi-cpu support is useful to improve the performance of kdump in some cases. So add the description of enable multi-cpu support in dump-capture kernel. Signed-off-by: Zhou Wenjian Acked-by: Baoquan He --- Documentation/kdump/kdump.txt | 7 +++ 1 file changed, 7 insertions(+) diff --git

RE: [PATCH v2 6/9] mtd: spi-nor: Support R/W for S25FS-S family flash

On August 06, 2016 10:27 PM, Jagan Teki wrote: > On 22 April 2016 at 12:09, Yunhui Cui wrote: > > From: Yunhui Cui > > > > With the physical sectors combination, S25FS-S family flash requires > > some special operations for read/write functions. > > >

RE: [PATCH v2 6/9] mtd: spi-nor: Support R/W for S25FS-S family flash

On August 06, 2016 10:27 PM, Jagan Teki wrote: > On 22 April 2016 at 12:09, Yunhui Cui wrote: > > From: Yunhui Cui > > > > With the physical sectors combination, S25FS-S family flash requires > > some special operations for read/write functions. > > > > Signed-off-by: Yunhui Cui > > --- > >

Re: [PATCH 06/15] genhd: Add return code to device_add_disk

On 08/17/2016 05:14 AM, Fam Zheng wrote: ... Of course, the plan is to write patches on top. I'm not cleaning up anything here because I'm concerned callers may double free (and I didn't look hard into that). Aside from Huck's concerns, the changes looked OK from aoe's perspective. -- Ed

Re: [PATCH 06/15] genhd: Add return code to device_add_disk

On 08/17/2016 05:14 AM, Fam Zheng wrote: ... Of course, the plan is to write patches on top. I'm not cleaning up anything here because I'm concerned callers may double free (and I didn't look hard into that). Aside from Huck's concerns, the changes looked OK from aoe's perspective. -- Ed

  1   2   3   4   5   6   7   8   9   10   >