Re: [PATCH] powerpc/sequoia: fix NAND partitions not to overlap

Pavel Machek writes: > On Wed 2017-05-17 14:37:17, Andrew Morton wrote: >> On Wed, 17 May 2017 14:06:13 +0200 Pavel Machek wrote: >> >> > On Sun 2017-04-02 12:05:36, Pavel Machek wrote: >> > > Fix overlapping NAND partitions. >> > > >> > > Signed-off-by: Pavel

Re: [PATCH] powerpc/sequoia: fix NAND partitions not to overlap

Pavel Machek writes: > On Wed 2017-05-17 14:37:17, Andrew Morton wrote: >> On Wed, 17 May 2017 14:06:13 +0200 Pavel Machek wrote: >> >> > On Sun 2017-04-02 12:05:36, Pavel Machek wrote: >> > > Fix overlapping NAND partitions. >> > > >> > > Signed-off-by: Pavel Machek >> > >> > Ping? Two

Re: [REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors

On Thu, May 18, 2017 at 11:42:34PM -0400, Steven Rostedt wrote: > > One of my the configs I use to test ftrace with (configs that have > caused failures in the past), has lots of irq issues and fails to > initialize the network of my box. I bisected the problem down to a > single commit, and when

Re: [REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors

On Thu, May 18, 2017 at 11:42:34PM -0400, Steven Rostedt wrote: > > One of my the configs I use to test ftrace with (configs that have > caused failures in the past), has lots of irq issues and fails to > initialize the network of my box. I bisected the problem down to a > single commit, and when

Re: Virtually Mapped Stacks: Do not disable interrupts

On Wed, May 17, 2017 at 8:58 AM, Christoph Lameter wrote: > The reason to disable interrupts seems to be to avoid switching > to a different processor while handling per cpu data using > individual loads and stores. If we use per cpu RMV primitives > we will not have to disable

Re: Virtually Mapped Stacks: Do not disable interrupts

On Wed, May 17, 2017 at 8:58 AM, Christoph Lameter wrote: > The reason to disable interrupts seems to be to avoid switching > to a different processor while handling per cpu data using > individual loads and stores. If we use per cpu RMV primitives > we will not have to disable interrupts. I

Re: [PATCH 4.11 000/114] 4.11.2-stable review

On Thu, May 18, 2017 at 06:10:07PM -0700, Guenter Roeck wrote: > On 05/18/2017 03:45 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.11.2 release. > > There are 114 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.11 000/114] 4.11.2-stable review

On Thu, May 18, 2017 at 06:10:07PM -0700, Guenter Roeck wrote: > On 05/18/2017 03:45 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.11.2 release. > > There are 114 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 10/30] kobject.txt: standardize document format

On Thu, May 18, 2017 at 10:24:02PM -0300, Mauro Carvalho Chehab wrote: > Each text file under Documentation follows a different > format. Some doesn't even have titles! > > Change its representation to follow the adopted standard, > using ReST markups for it to be parseable by Sphinx: > > - Add

Re: [PATCH 10/30] kobject.txt: standardize document format

On Thu, May 18, 2017 at 10:24:02PM -0300, Mauro Carvalho Chehab wrote: > Each text file under Documentation follows a different > format. Some doesn't even have titles! > > Change its representation to follow the adopted standard, > using ReST markups for it to be parseable by Sphinx: > > - Add

Re: [uwb-i1480] question about value overwrite

On Thu, May 18, 2017 at 06:00:06PM -0500, Gustavo A. R. Silva wrote: > > Hello everybody, > > While looking into Coverity ID 1226913 I ran into the following piece of > code at drivers/uwb/i1480/dfu/phy.c:99: > > 99static > 100int i1480_mpi_read(struct i1480 *i1480, u8 *data, u16 srcaddr,

Re: [uwb-i1480] question about value overwrite

On Thu, May 18, 2017 at 06:00:06PM -0500, Gustavo A. R. Silva wrote: > > Hello everybody, > > While looking into Coverity ID 1226913 I ran into the following piece of > code at drivers/uwb/i1480/dfu/phy.c:99: > > 99static > 100int i1480_mpi_read(struct i1480 *i1480, u8 *data, u16 srcaddr,

Re: [PATCH v2 00/10] rt2x00: rt2x00: improve calling conventions for register accessors

Arnd Bergmann writes: > I've managed to split up my long patch into a series of reasonble > steps now. > > The first two are required to fix a regression from commit 41977e86c984 > ("rt2x00: add support for MT7620"), the rest are just cleanups to > have a consistent state across

Re: [PATCH v2 00/10] rt2x00: rt2x00: improve calling conventions for register accessors

Arnd Bergmann writes: > I've managed to split up my long patch into a series of reasonble > steps now. > > The first two are required to fix a regression from commit 41977e86c984 > ("rt2x00: add support for MT7620"), the rest are just cleanups to > have a consistent state across all the register

Re: [PATCH 2/8 v2] clocksource/drivers/fttmr010: Merge FTTMR010 DT bindings

On Fri, May 19, 2017 at 4:16 AM, Linus Walleij wrote: > This merges the Moxa and FTTMR010 device tree bindings into the > Faraday binding document to avoid confusion. > > The FTTMR010 is the IP block used by these SoCs, in vanilla > or modified variant. > > The Aspeed

Re: [PATCH 2/8 v2] clocksource/drivers/fttmr010: Merge FTTMR010 DT bindings

On Fri, May 19, 2017 at 4:16 AM, Linus Walleij wrote: > This merges the Moxa and FTTMR010 device tree bindings into the > Faraday binding document to avoid confusion. > > The FTTMR010 is the IP block used by these SoCs, in vanilla > or modified variant. > > The Aspeed variant is modified such

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

On Fri, May 19, 2017 at 4:17 AM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding a

Re: [PATCH 7/8 v2] clocksource/drivers/fttmr010: Merge Moxa into FTTMR010

On Fri, May 19, 2017 at 4:17 AM, Linus Walleij wrote: > This merges the Moxa Art timer driver into the Faraday FTTMR010 > driver and replaces all Kconfig symbols to use the Faraday > driver instead. We are now so similar that the drivers can > be merged by just adding a few lines to the Faraday

linux-next: Tree for May 19

Hi all, Changes since 20170518: The netfilter tree still had its build failure for which I applied a supplied fix patch. The drm-intel tree gained a conflict against the drm tree. Non-merge commits (relative to Linus' tree): 1926 2098 files changed, 66645 insertions(+), 43483 deletions

linux-next: Tree for May 19

Hi all, Changes since 20170518: The netfilter tree still had its build failure for which I applied a supplied fix patch. The drm-intel tree gained a conflict against the drm tree. Non-merge commits (relative to Linus' tree): 1926 2098 files changed, 66645 insertions(+), 43483 deletions

Re: [PATCH 1/2] cpufreq: Make iowait boost a policy option

On Thu, May 18, 2017 at 9:17 PM, Viresh Kumar wrote: > On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: >> Make iowait boost a cpufreq policy option and enable it for intel_pstate >> cpufreq driver. Governors like schedutil can use it to

Re: [PATCH 1/2] cpufreq: Make iowait boost a policy option

On Thu, May 18, 2017 at 9:17 PM, Viresh Kumar wrote: > On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: >> Make iowait boost a cpufreq policy option and enable it for intel_pstate >> cpufreq driver. Governors like schedutil can use it to determine if >> boosting for tasks that wake up

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Thu, May 18, 2017 at 9:39 PM, Viresh Kumar wrote: [..] >> diff --git a/kernel/sched/cpufreq_schedutil.c >> b/kernel/sched/cpufreq_schedutil.c >> index 76877a62b5fa..6915925bc947 100644 >> --- a/kernel/sched/cpufreq_schedutil.c >> +++ b/kernel/sched/cpufreq_schedutil.c

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Thu, May 18, 2017 at 9:39 PM, Viresh Kumar wrote: [..] >> diff --git a/kernel/sched/cpufreq_schedutil.c >> b/kernel/sched/cpufreq_schedutil.c >> index 76877a62b5fa..6915925bc947 100644 >> --- a/kernel/sched/cpufreq_schedutil.c >> +++ b/kernel/sched/cpufreq_schedutil.c >> @@ -24,6 +24,7 @@ >>

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Thu, May 18, 2017 at 9:39 PM, Viresh Kumar wrote: > On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: >> If cpufreq policy has iowait boost enabled, use it. Also make it a schedutil >> configuration from sysfs so it can be turned on/off if

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Thu, May 18, 2017 at 9:39 PM, Viresh Kumar wrote: > On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: >> If cpufreq policy has iowait boost enabled, use it. Also make it a schedutil >> configuration from sysfs so it can be turned on/off if needed (by default use >> the policy value). >

Re: [PATCH v6 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On 5/18/17 9:31 AM, Greg KH wrote: > On Fri, May 05, 2017 at 07:20:18PM -0400, Matt Brown wrote: >> This introduces the tiocsti_restrict sysctl, whose default is controlled via >> CONFIG_SECURITY_TIOCSTI_RESTRICT. When activated, this control restricts >> all TIOCSTI ioctl calls from non

Re: [PATCH v6 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On 5/18/17 9:31 AM, Greg KH wrote: > On Fri, May 05, 2017 at 07:20:18PM -0400, Matt Brown wrote: >> This introduces the tiocsti_restrict sysctl, whose default is controlled via >> CONFIG_SECURITY_TIOCSTI_RESTRICT. When activated, this control restricts >> all TIOCSTI ioctl calls from non

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: mm/vmstat.c: In function 'pagetypeinfo_showblockcount_print': mm/vmstat.c:1230:8: warning: 'page' may be used uninitialized in this function [-Wmaybe-uninitialized] if

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: mm/vmstat.c: In function 'pagetypeinfo_showblockcount_print': mm/vmstat.c:1230:8: warning: 'page' may be used uninitialized in this function [-Wmaybe-uninitialized] if

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: > If cpufreq policy has iowait boost enabled, use it. Also make it a schedutil > configuration from sysfs so it can be turned on/off if needed (by default use > the policy value). As I understand it, you want to make

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: > If cpufreq policy has iowait boost enabled, use it. Also make it a schedutil > configuration from sysfs so it can be turned on/off if needed (by default use > the policy value). As I understand it, you want to make iowait boost optional.

Re: [PATCH v2] printk: Use the main logbuf in NMI when logbuf_lock is available

On (05/19/17 11:58), Sergey Senozhatsky wrote: > > void printk_nmi_exit(void) > > { > > - this_cpu_and(printk_context, ~PRINTK_NMI_CONTEXT_MASK); > > + this_cpu_and(printk_context, > > +~(PRINTK_NMI_CONTEXT_MASK || > > + PRINTK_NMI_DEFERRED_CONTEXT_MASK)); >

Re: [PATCH v2] printk: Use the main logbuf in NMI when logbuf_lock is available

On (05/19/17 11:58), Sergey Senozhatsky wrote: > > void printk_nmi_exit(void) > > { > > - this_cpu_and(printk_context, ~PRINTK_NMI_CONTEXT_MASK); > > + this_cpu_and(printk_context, > > +~(PRINTK_NMI_CONTEXT_MASK || > > + PRINTK_NMI_DEFERRED_CONTEXT_MASK)); >

[PATCH v10 07/10] coresight: add support for CPU debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH v10 07/10] coresight: add support for CPU debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension" introduces several sampling registers, e.g.

[PATCH v10 05/10] coresight: of_get_coresight_platform_data: Add missing of_node_put

From: Suzuki K Poulose The of_get_coresight_platform_data iterates over the possible CPU nodes to find a given cpu phandle. However it does not drop the reference to the node pointer returned by the of_get_coresight_platform_data. This patch also introduces another minor

[PATCH] kbuild: simplify silent build (-s) detection

This allows to detect -s option without checking GNU Make version. As commit e36aaea28972 ("kbuild: Fix silent builds with make-4") pointed out, GNU Make 4.x changed the way/order it presents the command line options into MAKEFLAGS. In Make 3.8x, 's' is always be the first in a group of short

[PATCH v10 05/10] coresight: of_get_coresight_platform_data: Add missing of_node_put

From: Suzuki K Poulose The of_get_coresight_platform_data iterates over the possible CPU nodes to find a given cpu phandle. However it does not drop the reference to the node pointer returned by the of_get_coresight_platform_data. This patch also introduces another minor fix is to use

[PATCH] kbuild: simplify silent build (-s) detection

This allows to detect -s option without checking GNU Make version. As commit e36aaea28972 ("kbuild: Fix silent builds with make-4") pointed out, GNU Make 4.x changed the way/order it presents the command line options into MAKEFLAGS. In Make 3.8x, 's' is always be the first in a group of short

[PATCH v10 09/10] arm64: dts: qcom: msm8916: Add debug unit

Add debug unit on Qualcomm msm8916 based platforms, including the DragonBoard 410c board. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 32 1 file changed, 32

[PATCH v10 09/10] arm64: dts: qcom: msm8916: Add debug unit

Add debug unit on Qualcomm msm8916 based platforms, including the DragonBoard 410c board. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- arch/arm64/boot/dts/qcom/msm8916.dtsi | 32 1 file changed, 32 insertions(+) diff --git

[PATCH v10 08/10] arm64: dts: hi6220: register debug module

Bind debug module driver for Hi6220. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 +++ 1 file changed, 64 insertions(+) diff --git

[PATCH v10 10/10] arm64: dts: juno: Add Coresight CPU debug nodes

From: Suzuki K Poulose Add Coresight CPU debug nodes for Juno r0, r1 & r2. The CPU debug areas are mapped at the same address for all revisions, like the ETM, even though the CPUs have changed from r1 to r2. Cc: Sudeep Holla Cc: Leo Yan

[PATCH v10 08/10] arm64: dts: hi6220: register debug module

Bind debug module driver for Hi6220. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 +++ 1 file changed, 64 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi

[PATCH v10 10/10] arm64: dts: juno: Add Coresight CPU debug nodes

From: Suzuki K Poulose Add Coresight CPU debug nodes for Juno r0, r1 & r2. The CPU debug areas are mapped at the same address for all revisions, like the ETM, even though the CPUs have changed from r1 to r2. Cc: Sudeep Holla Cc: Leo Yan Cc: Mathieu Poirier Cc: Liviu Dudau Signed-off-by:

[PATCH v10 03/10] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt

Add coresight_cpu_debug.enable to kernel-parameters.txt, this flag is used to enable/disable the CPU sampling based debugging. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- Documentation/admin-guide/kernel-parameters.txt | 7 +++ 1

[PATCH v10 04/10] MAINTAINERS: update file entries for Coresight subsystem

Update document file entries for Coresight debug module. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f7d568b..d443258 100644 ---

[PATCH v10 04/10] MAINTAINERS: update file entries for Coresight subsystem

Update document file entries for Coresight debug module. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f7d568b..d443258 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1208,7 +1208,9 @@

[PATCH v10 03/10] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt

Add coresight_cpu_debug.enable to kernel-parameters.txt, this flag is used to enable/disable the CPU sampling based debugging. Reviewed-by: Mathieu Poirier Signed-off-by: Leo Yan --- Documentation/admin-guide/kernel-parameters.txt | 7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH v10 01/10] coresight: bindings for CPU debug module

According to ARMv8 architecture reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate debug module and it can support self-hosted debug and external debug. Especially for supporting self-hosted debug, this means the program can access the debug module from mmio

[PATCH v10 06/10] coresight: refactor with function of_coresight_get_cpu

This is refactor to add function of_coresight_get_cpu(), so it's used to retrieve CPU id for coresight component. Finally can use it as a common function for multiple places. Suggested-by: Mathieu Poirier Reviewed-by: Suzuki K Poulose

[PATCH v10 01/10] coresight: bindings for CPU debug module

According to ARMv8 architecture reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate debug module and it can support self-hosted debug and external debug. Especially for supporting self-hosted debug, this means the program can access the debug module from mmio

[PATCH v10 06/10] coresight: refactor with function of_coresight_get_cpu

This is refactor to add function of_coresight_get_cpu(), so it's used to retrieve CPU id for coresight component. Finally can use it as a common function for multiple places. Suggested-by: Mathieu Poirier Reviewed-by: Suzuki K Poulose Signed-off-by: Leo Yan ---

[PATCH v10 02/10] doc: Add documentation for Coresight CPU debug

Add detailed documentation for Coresight CPU debug driver, which contains the info for driver implementation, Mike Leach excellent summary for "clock and power domain". At the end some examples on how to enable the debugging functionality are provided. Suggested-by: Mike Leach

[PATCH v10 02/10] doc: Add documentation for Coresight CPU debug

Add detailed documentation for Coresight CPU debug driver, which contains the info for driver implementation, Mike Leach excellent summary for "clock and power domain". At the end some examples on how to enable the debugging functionality are provided. Suggested-by: Mike Leach Reviewed-by:

[PATCH v10 00/10] coresight: enable debug module

ARMv8 architecture reference manual (ARM DDI 0487A.k) Chapter H7 "The Sample-based Profiling Extension" has description for sampling registers, we can utilize these registers to check program counter value with combined CPU exception level, secure state, etc. So this is helpful for CPU lockup

[PATCH v10 00/10] coresight: enable debug module

ARMv8 architecture reference manual (ARM DDI 0487A.k) Chapter H7 "The Sample-based Profiling Extension" has description for sampling registers, we can utilize these registers to check program counter value with combined CPU exception level, secure state, etc. So this is helpful for CPU lockup

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Fri, May 19, 2017 at 3:17 AM, Joel Fernandes wrote: > Hi Rafael, > > On Thu, May 18, 2017 at 6:08 PM, Rafael J. Wysocki wrote: > [..] >>> static struct governor_attr rate_limit_us = __ATTR_RW(rate_limit_us); >>> +static struct governor_attr

Re: [PATCH 2/2] sched: Use iowait boost policy option in schedutil

On Fri, May 19, 2017 at 3:17 AM, Joel Fernandes wrote: > Hi Rafael, > > On Thu, May 18, 2017 at 6:08 PM, Rafael J. Wysocki wrote: > [..] >>> static struct governor_attr rate_limit_us = __ATTR_RW(rate_limit_us); >>> +static struct governor_attr iowait_boost_enable = >>>

Re: [PATCH 1/2] cpufreq: Make iowait boost a policy option

On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: > Make iowait boost a cpufreq policy option and enable it for intel_pstate > cpufreq driver. Governors like schedutil can use it to determine if > boosting for tasks that wake up with p->in_iowait set is needed. > >

Re: [PATCH 1/2] cpufreq: Make iowait boost a policy option

On Fri, May 19, 2017 at 12:00 AM, Joel Fernandes wrote: > Make iowait boost a cpufreq policy option and enable it for intel_pstate > cpufreq driver. Governors like schedutil can use it to determine if > boosting for tasks that wake up with p->in_iowait set is needed. > > Signed-off-by: Joel

Re: [PATCH v4 05/27] btrfs: btrfs_wait_tree_block_writeback can be void return

On Tue, May 09, 2017 at 11:49:08AM -0400, Jeff Layton wrote: > Nothing checks its return value. Reviewed-by: Liu Bo -liubo > > Signed-off-by: Jeff Layton > --- > fs/btrfs/disk-io.c | 6 +++--- > fs/btrfs/disk-io.h | 2 +- > 2 files changed, 4

Re: [PATCH v4 05/27] btrfs: btrfs_wait_tree_block_writeback can be void return

On Tue, May 09, 2017 at 11:49:08AM -0400, Jeff Layton wrote: > Nothing checks its return value. Reviewed-by: Liu Bo -liubo > > Signed-off-by: Jeff Layton > --- > fs/btrfs/disk-io.c | 6 +++--- > fs/btrfs/disk-io.h | 2 +- > 2 files changed, 4 insertions(+), 4 deletions(-) > > diff --git

Re: [PATCH] IB/IPoIB: Replace netdev_priv with ipoib_priv for ipoib_get_link_ksettings

On Fri, May 19, 2017 at 11:15:32AM +0800, Yanjun Zhu wrote: > > > On 2017/5/11 20:40, Leon Romanovsky wrote: > > On Thu, May 11, 2017 at 03:31:10PM +0300, Yuval Shaia wrote: > > > On Thu, May 11, 2017 at 08:14:28PM +0800, Honggang LI wrote: > > > > From: Honggang Li > > > > > >

Re: [PATCH] IB/IPoIB: Replace netdev_priv with ipoib_priv for ipoib_get_link_ksettings

On Fri, May 19, 2017 at 11:15:32AM +0800, Yanjun Zhu wrote: > > > On 2017/5/11 20:40, Leon Romanovsky wrote: > > On Thu, May 11, 2017 at 03:31:10PM +0300, Yuval Shaia wrote: > > > On Thu, May 11, 2017 at 08:14:28PM +0800, Honggang LI wrote: > > > > From: Honggang Li > > > > > > > > ipoib_dev_init

Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image

On Thu, May 18, 2017 at 01:59:14PM +0800, Dave Young wrote: > Add Takahiro and Pratyush, they should be able to review the arm64 part. > > On 05/18/17 at 11:03am, Bharat Bhushan wrote: > > This patch have minor updates in Documentation for arm64i as > > relocatable kernel. > > Also this patch

Re: [PATCH] kexec/kdump: Minor Documentation updates for arm64 and Image

On Thu, May 18, 2017 at 01:59:14PM +0800, Dave Young wrote: > Add Takahiro and Pratyush, they should be able to review the arm64 part. > > On 05/18/17 at 11:03am, Bharat Bhushan wrote: > > This patch have minor updates in Documentation for arm64i as > > relocatable kernel. > > Also this patch

Re: [PATCH -next] dma: bcm-sba-raid: fix build errors and dependencies

On Wed, May 17, 2017 at 09:40:47AM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix build errors when COMPILE_TEST is enabled but RAID6_PQ is not > enabled (seen on x86_64). Oops, I already applied one from Arnd and pushed that out. > > drivers/built-in.o: In

Re: [v1 1/1] usb:host:xhci support option to disable xHCI 1.0 USB2 HW LPM

On Fri, May 19, 2017 at 5:30 AM, Rob Herring wrote: > On Sat, May 13, 2017 at 07:13:14AM +0700, Thang Q. Nguyen wrote: >> XHCI specification 1.1 does not require xHCI 1.0 compliant controllers >> to always enable hardware USB2 LPM. >> However, the current xHCI driver always

Re: [PATCH -next] dma: bcm-sba-raid: fix build errors and dependencies

On Wed, May 17, 2017 at 09:40:47AM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Fix build errors when COMPILE_TEST is enabled but RAID6_PQ is not > enabled (seen on x86_64). Oops, I already applied one from Arnd and pushed that out. > > drivers/built-in.o: In function

Re: [v1 1/1] usb:host:xhci support option to disable xHCI 1.0 USB2 HW LPM

On Fri, May 19, 2017 at 5:30 AM, Rob Herring wrote: > On Sat, May 13, 2017 at 07:13:14AM +0700, Thang Q. Nguyen wrote: >> XHCI specification 1.1 does not require xHCI 1.0 compliant controllers >> to always enable hardware USB2 LPM. >> However, the current xHCI driver always enable it by setting

Re: [greybus-dev] [PATCH] staging: greybus: mark PM functions as __maybe_unused

On 18-05-17, 16:51, Arnd Bergmann wrote: > I find that a lot of users get the #ifdef wrong, either using the wrong > macro (CONFIG_PM vs CONFIG_PM_SLEEP) or not using the right > set of functions (e.g. calling a function only from the suspend handler). > > The __maybe_unused annotation avoids

Re: [greybus-dev] [PATCH] staging: greybus: mark PM functions as __maybe_unused

On 18-05-17, 16:51, Arnd Bergmann wrote: > I find that a lot of users get the #ifdef wrong, either using the wrong > macro (CONFIG_PM vs CONFIG_PM_SLEEP) or not using the right > set of functions (e.g. calling a function only from the suspend handler). > > The __maybe_unused annotation avoids

[REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors

One of my the configs I use to test ftrace with (configs that have caused failures in the past), has lots of irq issues and fails to initialize the network of my box. I bisected the problem down to a single commit, and when I revert that commit, my box boots without any network or irq issues.

[REGRESSION] Failed network caused by: xhci: switch to pci_alloc_irq_vectors

One of my the configs I use to test ftrace with (configs that have caused failures in the past), has lots of irq issues and fails to initialize the network of my box. I bisected the problem down to a single commit, and when I revert that commit, my box boots without any network or irq issues.

[PATCH v3 0/5] sysctl: few fixes

I've been working on making kmod more deterministic, and as I did that I couldn't help but notice a few issues with sysctl. My end goal was just to fix unsigned int support, which back then was completely broken. Liping Zhang has sent up small atomic fixes, however it still missed yet one more fix

[PATCH v3 0/5] sysctl: few fixes

I've been working on making kmod more deterministic, and as I did that I couldn't help but notice a few issues with sysctl. My end goal was just to fix unsigned int support, which back then was completely broken. Liping Zhang has sent up small atomic fixes, however it still missed yet one more fix

[PATCH v3 2/5] sysctl: kdoc'ify sysctl_writes_strict

Document the different sysctl_writes_strict modes in code. Signed-off-by: Luis R. Rodriguez --- kernel/sysctl.c | 29 + 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/kernel/sysctl.c b/kernel/sysctl.c index

[PATCH v3 2/5] sysctl: kdoc'ify sysctl_writes_strict

Document the different sysctl_writes_strict modes in code. Signed-off-by: Luis R. Rodriguez --- kernel/sysctl.c | 29 + 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 4dfba1a76cc3..02725178694a 100644 ---

[PATCH v3 1/5] sysctl: fix lax sysctl_check_table() sanity check

Commit 7c60c48f58a7 ("sysctl: Improve the sysctl sanity checks") improved sanity checks considerbly, however the enhancements on sysctl_check_table() meant adding a functional change so that only the last table entry's sanity error is propagated. It also changed the way errors were propagated so

[PATCH v3 5/5] sysctl: add unsigned int range support

To keep parity with regular int interfaces provide the an unsigned int proc_douintvec_minmax() which allows you to specify a range of allowed valid numbers. Adding proc_douintvec_minmax_sysadmin() is easy but we can wait for an actual user for that. Cc: Subash Abhinov Kasiviswanathan

[PATCH v3 4/5] sysctl: simplify unsigned int support

Commit e7d316a02f6838 ("sysctl: handle error writing UINT_MAX to u32 fields") added proc_douintvec() to start help adding support for unsigned int, this however was only half the work needed. Two fixes have come in since then for the following issues: o Printing the values shows a negative

[PATCH v3 3/5] sysctl: fold sysctl_writes_strict checks into helper

The mode sysctl_writes_strict positional checks keep being copy and pasted as we add new proc handlers. Just add a helper to avoid code duplication. Suggested-by: Kees Cook Signed-off-by: Luis R. Rodriguez --- kernel/sysctl.c | 56

[PATCH v3 1/5] sysctl: fix lax sysctl_check_table() sanity check

Commit 7c60c48f58a7 ("sysctl: Improve the sysctl sanity checks") improved sanity checks considerbly, however the enhancements on sysctl_check_table() meant adding a functional change so that only the last table entry's sanity error is propagated. It also changed the way errors were propagated so

[PATCH v3 5/5] sysctl: add unsigned int range support

To keep parity with regular int interfaces provide the an unsigned int proc_douintvec_minmax() which allows you to specify a range of allowed valid numbers. Adding proc_douintvec_minmax_sysadmin() is easy but we can wait for an actual user for that. Cc: Subash Abhinov Kasiviswanathan Cc:

[PATCH v3 4/5] sysctl: simplify unsigned int support

Commit e7d316a02f6838 ("sysctl: handle error writing UINT_MAX to u32 fields") added proc_douintvec() to start help adding support for unsigned int, this however was only half the work needed. Two fixes have come in since then for the following issues: o Printing the values shows a negative

[PATCH v3 3/5] sysctl: fold sysctl_writes_strict checks into helper

The mode sysctl_writes_strict positional checks keep being copy and pasted as we add new proc handlers. Just add a helper to avoid code duplication. Suggested-by: Kees Cook Signed-off-by: Luis R. Rodriguez --- kernel/sysctl.c | 56 1

Re: [PATCH] zlib: Mark get_unaligned16() as __maybe_unused

Hi Matthias, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc1 next-20170518] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/zlib-Mark

[PATCH 1/6] kmod: add dynamic max concurrent thread count

We currently statically limit the number of modprobe threads which we allow to run concurrently to 50. As per Keith Owens, this was a completely arbitrary value, and it was set in the 2.3.38 days [0] over 16 years ago in year 2000. Although we haven't yet hit our lower limits, experimentation [1]

Re: [PATCH] zlib: Mark get_unaligned16() as __maybe_unused

Hi Matthias, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc1 next-20170518] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Matthias-Kaehlcke/zlib-Mark

[PATCH 1/6] kmod: add dynamic max concurrent thread count

We currently statically limit the number of modprobe threads which we allow to run concurrently to 50. As per Keith Owens, this was a completely arbitrary value, and it was set in the 2.3.38 days [0] over 16 years ago in year 2000. Although we haven't yet hit our lower limits, experimentation [1]

[PATCH 4/6] kmod: return -EBUSY if modprobe limit is reached

Running out of our modprobe limit is not a memory limit but a system specific established limitation set to avoid a possible recursive issue with modprobe. This gives userspace a better idea of what happened if we can't load a module, it could use this to wait and try again. Signed-off-by: Luis

[PATCH 4/6] kmod: return -EBUSY if modprobe limit is reached

Running out of our modprobe limit is not a memory limit but a system specific established limitation set to avoid a possible recursive issue with modprobe. This gives userspace a better idea of what happened if we can't load a module, it could use this to wait and try again. Signed-off-by: Luis

[PATCH 5/6] kmod: preempt on kmod_umh_threads_get()

In theory it is possible multiple concurrent threads will try to kmod_umh_threads_get() and as such atomic_inc(_concurrent) at the same time, therefore enabling a small time during which we've bumped kmod_concurrent but have not really enabled work. By using preemption we mitigate this a bit.

[PATCH 3/6] kmod: provide wrappers for kmod_concurrent inc/dec

kmod_concurrent is used as an atomic counter for enabling the allowed limit of modprobe calls, provide wrappers for it to enable this to be expanded on more easily. This will be done later. Signed-off-by: Luis R. Rodriguez --- kernel/kmod.c | 25 +++-- 1

[PATCH 5/6] kmod: preempt on kmod_umh_threads_get()

In theory it is possible multiple concurrent threads will try to kmod_umh_threads_get() and as such atomic_inc(_concurrent) at the same time, therefore enabling a small time during which we've bumped kmod_concurrent but have not really enabled work. By using preemption we mitigate this a bit.

[PATCH 3/6] kmod: provide wrappers for kmod_concurrent inc/dec

kmod_concurrent is used as an atomic counter for enabling the allowed limit of modprobe calls, provide wrappers for it to enable this to be expanded on more easily. This will be done later. Signed-off-by: Luis R. Rodriguez --- kernel/kmod.c | 25 +++-- 1 file changed, 19

[PATCH 0/6] kmod: few simple enhancements

I've been working on making module loading more deterministic, these are some of the more straight forward changes I've come up with so far. The others depend on some further sysctl changes so I'll wait to introduce those, and also on a new kmod stress driver loader, which I'll also hold off on

[PATCH 0/6] kmod: few simple enhancements

I've been working on making module loading more deterministic, these are some of the more straight forward changes I've come up with so far. The others depend on some further sysctl changes so I'll wait to introduce those, and also on a new kmod stress driver loader, which I'll also hold off on

  1   2   3   4   5   6   7   8   9   10   >