Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote: > On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote: >> On 1/15/2018 4:47 PM, Gabriel C wrote: >>> On 11.01.2018 19:33, Borislav Petkov wrote: On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: > This patch series

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote: > On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote: >> On 1/15/2018 4:47 PM, Gabriel C wrote: >>> On 11.01.2018 19:33, Borislav Petkov wrote: On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: > This patch series

Re: pull-request: wireless-drivers-next 2018-01-19

From: Kalle Valo Date: Fri, 19 Jan 2018 10:59:33 +0200 > a pull request to net-next tree for 4.16. This should be the last pull > request in this cycle, unless Linus releases -rc9 of course. Only few > patches so should be an easy one. Please let me know if there are any >

Re: pull-request: wireless-drivers-next 2018-01-19

From: Kalle Valo Date: Fri, 19 Jan 2018 10:59:33 +0200 > a pull request to net-next tree for 4.16. This should be the last pull > request in this cycle, unless Linus releases -rc9 of course. Only few > patches so should be an easy one. Please let me know if there are any > problems. Pulled,

Re: [PATCH 34/35] x86/kvm: Add IBPB support

On 18/01/2018 16:32, Paolo Bonzini wrote: > On 18/01/2018 14:48, Peter Zijlstra wrote: >> From: Ashok Raj >> >> Add MSR passthrough for MSR_IA32_PRED_CMD and place branch predictor >> barriers on switching between VMs to avoid inter VM specte-v2 attacks. >> >> [peterz: rebase

Re: [PATCH 34/35] x86/kvm: Add IBPB support

On 18/01/2018 16:32, Paolo Bonzini wrote: > On 18/01/2018 14:48, Peter Zijlstra wrote: >> From: Ashok Raj >> >> Add MSR passthrough for MSR_IA32_PRED_CMD and place branch predictor >> barriers on switching between VMs to avoid inter VM specte-v2 attacks. >> >> [peterz: rebase and changelog

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 8:20 AM, Bart Van Assche wrote: > On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote: >> Please see queue_delayed_work_on(), hctx->run_work is shared by all >> scheduling, once blk_mq_delay_run_hw_queue(100ms) returns, no new >> scheduling can make progress during the 100ms. > > How

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 8:20 AM, Bart Van Assche wrote: > On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote: >> Please see queue_delayed_work_on(), hctx->run_work is shared by all >> scheduling, once blk_mq_delay_run_hw_queue(100ms) returns, no new >> scheduling can make progress during the 100ms. > > How

[PATCH V3 08/10] clk: imx: implement new clk_hw based APIs

Clock providers are recommended to use the new struct clk_hw based API, so implement IMX clk_hw based provider helpers functions to the new approach. Signed-off-by: Dong Aisheng --- ChangeLog: v2->v3: * no changes v1->v2: new patches --- drivers/clk/imx/clk.c | 22

[PATCH V3 08/10] clk: imx: implement new clk_hw based APIs

Clock providers are recommended to use the new struct clk_hw based API, so implement IMX clk_hw based provider helpers functions to the new approach. Signed-off-by: Dong Aisheng --- ChangeLog: v2->v3: * no changes v1->v2: new patches --- drivers/clk/imx/clk.c | 22 ++

[PATCH V3 10/10] add imx7ulp support

Signed-off-by: Dong Aisheng --- arch/arm/boot/dts/Makefile | 2 + arch/arm/boot/dts/imx7ulp-evk.dts| 87 +++ arch/arm/boot/dts/imx7ulp.dtsi | 202 +++ arch/arm/configs/imx_v6_v7_defconfig | 16 ++-

[PATCH V3 00/10] clk: add imx7ulp clk support

This patch series intends to add imx7ulp clk support. i.MX7ULP Clock functions are under joint control of the System Clock Generation (SCG) modules, Peripheral Clock Control (PCC) modules, and Core Mode Controller (CMC)1 blocks The clocking scheme provides clear separation between M4 domain and

[PATCH V3 00/10] clk: add imx7ulp clk support

This patch series intends to add imx7ulp clk support. i.MX7ULP Clock functions are under joint control of the System Clock Generation (SCG) modules, Peripheral Clock Control (PCC) modules, and Core Mode Controller (CMC)1 blocks The clocking scheme provides clear separation between M4 domain and

[PATCH V3 10/10] add imx7ulp support

Signed-off-by: Dong Aisheng --- arch/arm/boot/dts/Makefile | 2 + arch/arm/boot/dts/imx7ulp-evk.dts| 87 +++ arch/arm/boot/dts/imx7ulp.dtsi | 202 +++ arch/arm/configs/imx_v6_v7_defconfig | 16 ++- arch/arm/mach-imx/Kconfig

[PATCH 1/1] Documentation: clk: enable lock is not held for clk_is_enabled API

The core does not need to hold enable lock for clk_is_enabled API. Update the doc to reflect it. Cc: Jonathan Corbet Cc: Stephen Boyd Suggested-by: Stephen Boyd Signed-off-by: Dong Aisheng ---

[PATCH 1/1] Documentation: clk: enable lock is not held for clk_is_enabled API

The core does not need to hold enable lock for clk_is_enabled API. Update the doc to reflect it. Cc: Jonathan Corbet Cc: Stephen Boyd Suggested-by: Stephen Boyd Signed-off-by: Dong Aisheng --- Documentation/clk.txt | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On 19 January 2018 at 08:12, Jiri Olsa wrote: > On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: >> Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: >> > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: >> > > Em

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On 19 January 2018 at 08:12, Jiri Olsa wrote: > On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: >> Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: >> > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: >> > > Em Thu, Jan 18, 2018 at

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri, Jan 19, 2018 at 7:11 AM, Michal Hocko wrote: > On Fri 19-01-18 06:49:29, Shakeel Butt wrote: >> On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: >> > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: >> >> Currently mem_cgroup_resize_limit()

Re: [BUG] do_IRQ: 7.33 No irq handler for vector

On Fri, 19 Jan 2018, jianchao.wang wrote: > When I did cpu hotplug stress test, I found this log on my machine. > > [ 267.161043] do_IRQ: 7.33 No irq handler for vector > > I add a dump_stack below the bug and get following log: Well, that's pretty uninteresting. What's interesting is which

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri, Jan 19, 2018 at 7:11 AM, Michal Hocko wrote: > On Fri 19-01-18 06:49:29, Shakeel Butt wrote: >> On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: >> > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: >> >> Currently mem_cgroup_resize_limit() retries to set limit after reclaiming >> >>

Re: [BUG] do_IRQ: 7.33 No irq handler for vector

On Fri, 19 Jan 2018, jianchao.wang wrote: > When I did cpu hotplug stress test, I found this log on my machine. > > [ 267.161043] do_IRQ: 7.33 No irq handler for vector > > I add a dump_stack below the bug and get following log: Well, that's pretty uninteresting. What's interesting is which

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 12:26 AM, Ming Lei wrote: > On Thu, Jan 18, 2018 at 09:02:45PM -0700, Jens Axboe wrote: >> On 1/18/18 7:32 PM, Ming Lei wrote: >>> On Thu, Jan 18, 2018 at 01:11:01PM -0700, Jens Axboe wrote: On 1/18/18 11:47 AM, Bart Van Assche wrote: >> This is all very tiresome. > >

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On 1/19/18 12:26 AM, Ming Lei wrote: > On Thu, Jan 18, 2018 at 09:02:45PM -0700, Jens Axboe wrote: >> On 1/18/18 7:32 PM, Ming Lei wrote: >>> On Thu, Jan 18, 2018 at 01:11:01PM -0700, Jens Axboe wrote: On 1/18/18 11:47 AM, Bart Van Assche wrote: >> This is all very tiresome. > >

Re: [PATCH] ARM: dts: nomadik: add interrupt-parent for clcd

On Tue, Jan 16, 2018 at 8:29 AM, Linus Walleij wrote: > On Mon, Jan 15, 2018 at 5:37 PM, Arnd Bergmann wrote: > >> The clcd device is lacking an interrupt-parent property, which makes >> the interrupt unusable and shows up as a warning with the latest >>

Re: [PATCH] ARM: dts: nomadik: add interrupt-parent for clcd

On Tue, Jan 16, 2018 at 8:29 AM, Linus Walleij wrote: > On Mon, Jan 15, 2018 at 5:37 PM, Arnd Bergmann wrote: > >> The clcd device is lacking an interrupt-parent property, which makes >> the interrupt unusable and shows up as a warning with the latest >> dtc version: >> >>

[PATCH net-next] net: hns3: converting spaces into tabs to avoid checkpatch.pl warning

Spaces were mistakenly used instead of tabs in some of the code related to reset functionality, which caused checkpatch.pl errors. These were missed earlier so fixing them now. Signed-off-by: Salil Mehta --- drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 4 ++-- 1

[PATCH net-next] net: hns3: converting spaces into tabs to avoid checkpatch.pl warning

Spaces were mistakenly used instead of tabs in some of the code related to reset functionality, which caused checkpatch.pl errors. These were missed earlier so fixing them now. Signed-off-by: Salil Mehta --- drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 4 ++-- 1 file changed, 2

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote: > Please see queue_delayed_work_on(), hctx->run_work is shared by all > scheduling, once blk_mq_delay_run_hw_queue(100ms) returns, no new > scheduling can make progress during the 100ms. How about addressing that as follows: diff --git

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote: > Please see queue_delayed_work_on(), hctx->run_work is shared by all > scheduling, once blk_mq_delay_run_hw_queue(100ms) returns, no new > scheduling can make progress during the 100ms. How about addressing that as follows: diff --git

Re: [PATCH] net/mlx4_en: ensure rx_desc updating reaches HW before prod db updating

Hi Tariq Very sad that the crash was reproduced again after applied the patch. --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c @@ -252,6 +252,7 @@ static inline bool mlx4_en_is_ring_empty(struct mlx4_en_rx_ring *ring) static inline void

Re: [PATCH] net/mlx4_en: ensure rx_desc updating reaches HW before prod db updating

Hi Tariq Very sad that the crash was reproduced again after applied the patch. --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c @@ -252,6 +252,7 @@ static inline bool mlx4_en_is_ring_empty(struct mlx4_en_rx_ring *ring) static inline void

[PATCH] Coccinelle: zalloc-simple: Delete duplicate specifications of the key word "expression"

From: Markus Elfring Date: Fri, 19 Jan 2018 16:00:22 +0100 Reduce the file size a bit by removing 12 specifications of the key word "expression" in this script for the semantic patch language. Signed-off-by: Markus Elfring ---

[PATCH] Coccinelle: zalloc-simple: Delete duplicate specifications of the key word "expression"

From: Markus Elfring Date: Fri, 19 Jan 2018 16:00:22 +0100 Reduce the file size a bit by removing 12 specifications of the key word "expression" in this script for the semantic patch language. Signed-off-by: Markus Elfring --- scripts/coccinelle/api/alloc/zalloc-simple.cocci | 36

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

2018-01-19 22:52 GMT+08:00 Arnd Bergmann : > On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote: >> 2018-01-18 19:02 GMT+08:00 Arnd Bergmann : >>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: From: Greentime Hu

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

2018-01-19 22:52 GMT+08:00 Arnd Bergmann : > On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote: >> 2018-01-18 19:02 GMT+08:00 Arnd Bergmann : >>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: From: Greentime Hu This patch adds nds32 CPU binding documents.

Re: [PATCH] psci: add CPU_IDLE dependency

On Mon, Jul 31, 2017 at 4:14 PM, Jean Delvare wrote: > > On Mon, 31 Jul 2017 11:19:39 +0100, Kevin Brodsky wrote: >> On 31/07/17 09:55, Arnd Bergmann wrote: >> > I ran into a build error for the psci_checker: >> > >> > Fixes: ea8b1c4a6019 ("drivers: psci: PSCI checker module")

Re: [PATCH] psci: add CPU_IDLE dependency

On Mon, Jul 31, 2017 at 4:14 PM, Jean Delvare wrote: > > On Mon, 31 Jul 2017 11:19:39 +0100, Kevin Brodsky wrote: >> On 31/07/17 09:55, Arnd Bergmann wrote: >> > I ran into a build error for the psci_checker: >> > >> > Fixes: ea8b1c4a6019 ("drivers: psci: PSCI checker module") >> > Signed-off-by:

Re: [RFC 0/4] tools lib traceevent: Install fixes

On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote: > On Fri, 19 Jan 2018 11:37:13 +0100 > Jiri Olsa wrote: > > > hi, > > I checked on this one and was surprised last email is from 2016 ;-) > > so we did not move much with this.. is there still will to do that? > >

Re: [RFC 0/4] tools lib traceevent: Install fixes

On Fri, Jan 19, 2018 at 10:07:28AM -0500, Steven Rostedt wrote: > On Fri, 19 Jan 2018 11:37:13 +0100 > Jiri Olsa wrote: > > > hi, > > I checked on this one and was surprised last email is from 2016 ;-) > > so we did not move much with this.. is there still will to do that? > > > > I think we

RE: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

> > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > In the uncore document, there is no event-code assigned to free running > counters. > > Some events need to be defined to indicate the free running counters. > > The events are encoded as event-code + umask-code. > > > > The

RE: [PATCH V5 4/8] perf/x86/intel/uncore: add new data structures for free running counters

> > On Thu, Jan 18, 2018 at 05:43:10PM +, Liang, Kan wrote: > > In the uncore document, there is no event-code assigned to free running > counters. > > Some events need to be defined to indicate the free running counters. > > The events are encoded as event-code + umask-code. > > > > The

Re: [PATCH] phy: work around 'phys' references to usb-nop-xceiv devices

On Fri, Jan 19, 2018 at 11:35 AM, Stefan Wahren wrote: > Am 12.01.2018 um 20:54 schrieb Rob Herring: >> On Fri, Jan 12, 2018 at 4:12 AM, Arnd Bergmann wrote: >>> --- >>> Hans tested the earlier version of this patch, I'd like one more >>> confirmation from

Re: [PATCH] phy: work around 'phys' references to usb-nop-xceiv devices

On Fri, Jan 19, 2018 at 11:35 AM, Stefan Wahren wrote: > Am 12.01.2018 um 20:54 schrieb Rob Herring: >> On Fri, Jan 12, 2018 at 4:12 AM, Arnd Bergmann wrote: >>> --- >>> Hans tested the earlier version of this patch, I'd like one more >>> confirmation from Hans or Stefan (or anyone else) that

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: > > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Thu, Jan 18, 2018 at 02:59:48PM +0100, Jiri Olsa escreveu: > > > > On

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: > > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Thu, Jan 18, 2018 at 02:59:48PM +0100, Jiri Olsa escreveu: > > > > On

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote: > On 1/15/2018 4:47 PM, Gabriel C wrote: > > On 11.01.2018 19:33, Borislav Petkov wrote: > >> On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: > >>> This patch series addresses an issue when SME is active and the BSP > >>>

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote: > On 1/15/2018 4:47 PM, Gabriel C wrote: > > On 11.01.2018 19:33, Borislav Petkov wrote: > >> On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: > >>> This patch series addresses an issue when SME is active and the BSP > >>>

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri 19-01-18 06:49:29, Shakeel Butt wrote: > On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: > > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: > >> Currently mem_cgroup_resize_limit() retries to set limit after reclaiming > >> 32 pages. It makes more sense to reclaim

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri 19-01-18 06:49:29, Shakeel Butt wrote: > On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: > > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: > >> Currently mem_cgroup_resize_limit() retries to set limit after reclaiming > >> 32 pages. It makes more sense to reclaim needed amount of

RE: [1/3] arm64: defconfig: enable CONFIG_ACPI_APEI_MEMORY_FAILURE

Thanks Arnd. Regards, Shiju > -Original Message- > From: arndbergm...@gmail.com [mailto:arndbergm...@gmail.com] On Behalf > Of Arnd Bergmann > Sent: 19 January 2018 15:07 > To: Timur Tabi > Cc: Shiju Jose; Linux ARM; Linux Kernel Mailing List; Catalin Marinas; > Will Deacon; Gregory

RE: [1/3] arm64: defconfig: enable CONFIG_ACPI_APEI_MEMORY_FAILURE

Thanks Arnd. Regards, Shiju > -Original Message- > From: arndbergm...@gmail.com [mailto:arndbergm...@gmail.com] On Behalf > Of Arnd Bergmann > Sent: 19 January 2018 15:07 > To: Timur Tabi > Cc: Shiju Jose; Linux ARM; Linux Kernel Mailing List; Catalin Marinas; > Will Deacon; Gregory

RE: [PATCH v3 1/2] dt-bindings: Document mti,mips-cpc binding

> On Wed, Dec 27, 2017 at 03:37:51PM +0100, Aleksandar Markovic wrote: > > From: Paul Burton > > > > Document a binding for the MIPS Cluster Power Controller (CPC) that > > allows the device tree to specify where the CPC registers are located. > > > > Signed-off-by: Paul

RE: [PATCH v3 1/2] dt-bindings: Document mti,mips-cpc binding

> On Wed, Dec 27, 2017 at 03:37:51PM +0100, Aleksandar Markovic wrote: > > From: Paul Burton > > > > Document a binding for the MIPS Cluster Power Controller (CPC) that > > allows the device tree to specify where the CPC registers are located. > > > > Signed-off-by: Paul Burton > >

Re: [RFC] Per file OOM badness

On 2018-01-19 11:02 AM, Michel Dänzer wrote: > On 2018-01-19 10:58 AM, Christian König wrote: >> Am 19.01.2018 um 10:32 schrieb Michel Dänzer: >>> On 2018-01-19 09:39 AM, Christian König wrote: Am 19.01.2018 um 09:20 schrieb Michal Hocko: > OK, in that case I would propose a different

Re: [RFC] Per file OOM badness

On 2018-01-19 11:02 AM, Michel Dänzer wrote: > On 2018-01-19 10:58 AM, Christian König wrote: >> Am 19.01.2018 um 10:32 schrieb Michel Dänzer: >>> On 2018-01-19 09:39 AM, Christian König wrote: Am 19.01.2018 um 09:20 schrieb Michal Hocko: > OK, in that case I would propose a different

Re: [RFC 0/4] tools lib traceevent: Install fixes

On Fri, 19 Jan 2018 11:37:13 +0100 Jiri Olsa wrote: > hi, > I checked on this one and was surprised last email is from 2016 ;-) > so we did not move much with this.. is there still will to do that? > > I think we were kind of waiting for the namespace changes in > traceevent

Re: [RFC 0/4] tools lib traceevent: Install fixes

On Fri, 19 Jan 2018 11:37:13 +0100 Jiri Olsa wrote: > hi, > I checked on this one and was surprised last email is from 2016 ;-) > so we did not move much with this.. is there still will to do that? > > I think we were kind of waiting for the namespace changes in > traceevent library.. like to

Re: [1/3] arm64: defconfig: enable CONFIG_ACPI_APEI_MEMORY_FAILURE

On Tue, Jan 16, 2018 at 5:10 PM, Timur Tabi wrote: > On 01/16/2018 09:45 AM, shiju.j...@huawei.com wrote: >> >> Enable ACPI APEI MEMORY FAILURE option for ARM64, >> so that memory errors will be handled. >> >> Signed-off-by: Shiju Jose > > > All three

Re: [1/3] arm64: defconfig: enable CONFIG_ACPI_APEI_MEMORY_FAILURE

On Tue, Jan 16, 2018 at 5:10 PM, Timur Tabi wrote: > On 01/16/2018 09:45 AM, shiju.j...@huawei.com wrote: >> >> Enable ACPI APEI MEMORY FAILURE option for ARM64, >> so that memory errors will be handled. >> >> Signed-off-by: Shiju Jose > > > All three patches: > > Acked-by: Timur Tabi > > QDT

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/15/2018 4:47 PM, Gabriel C wrote: > On 11.01.2018 19:33, Borislav Petkov wrote: >> On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: >>> This patch series addresses an issue when SME is active and the BSP >>> is attempting to check for and load microcode during load_ucode_bsp().

Re: [PATCH v3 0/5] x86: SME: BSP/SME microcode update fix

On 1/15/2018 4:47 PM, Gabriel C wrote: > On 11.01.2018 19:33, Borislav Petkov wrote: >> On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote: >>> This patch series addresses an issue when SME is active and the BSP >>> is attempting to check for and load microcode during load_ucode_bsp().

Re: [tip:sched/core] sched/rt: Simplify the IPI based RT balancing logic

On Fri, 19 Jan 2018 14:53:05 +0530 Pavan Kondeti wrote: > I am seeing "spinlock already unlocked" BUG for rd->rto_lock on a 4.9 > stable kernel based system. This issue is observed only after > inclusion of this patch. It appears to me that rq->rd can change > between

Re: [tip:sched/core] sched/rt: Simplify the IPI based RT balancing logic

On Fri, 19 Jan 2018 14:53:05 +0530 Pavan Kondeti wrote: > I am seeing "spinlock already unlocked" BUG for rd->rto_lock on a 4.9 > stable kernel based system. This issue is observed only after > inclusion of this patch. It appears to me that rq->rd can change > between spinlock is acquired and

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On Wed, Nov 15, 2017 at 1:31 AM, Jan Kara wrote: > On Wed 15-11-17 01:32:16, Yang Shi wrote: >> >> >> On 11/14/17 1:39 AM, Michal Hocko wrote: >> >On Tue 14-11-17 03:10:22, Yang Shi wrote: >> >> >> >> >> >>On 11/9/17 5:54 AM, Michal Hocko wrote: >> >>>[Sorry for the late reply] >>

Re: [PATCH v2] fs: fsnotify: account fsnotify metadata to kmemcg

On Wed, Nov 15, 2017 at 1:31 AM, Jan Kara wrote: > On Wed 15-11-17 01:32:16, Yang Shi wrote: >> >> >> On 11/14/17 1:39 AM, Michal Hocko wrote: >> >On Tue 14-11-17 03:10:22, Yang Shi wrote: >> >> >> >> >> >>On 11/9/17 5:54 AM, Michal Hocko wrote: >> >>>[Sorry for the late reply] >> >>> >> >>>On

Re: [PATCH v3 00/10] perf tools: Add support for CoreSight trace decoding

Em Wed, Jan 17, 2018 at 10:52:09AM -0700, Mathieu Poirier escreveu: > Hi Arnaldo, > > This patchset adds support for per-thread CoreSight trace decoding from the > "perf report" interface. It is largely modelled on what has been done for > intelPT traces and currently targets the ETMv4

Re: [PATCH v3 00/10] perf tools: Add support for CoreSight trace decoding

Em Wed, Jan 17, 2018 at 10:52:09AM -0700, Mathieu Poirier escreveu: > Hi Arnaldo, > > This patchset adds support for per-thread CoreSight trace decoding from the > "perf report" interface. It is largely modelled on what has been done for > intelPT traces and currently targets the ETMv4

[PATCH] crypto: chelsio - fix code indentation warning

gcc noticed some unusual and confusing indentation: drivers/crypto/chelsio/chcr_algo.c: In function 'create_authenc_wr': drivers/crypto/chelsio/chcr_algo.c:2113:2: error: this 'if' clause does not guard... [-Werror=misleading-indentation] if (error) ^~

[PATCH] crypto: chelsio - fix code indentation warning

gcc noticed some unusual and confusing indentation: drivers/crypto/chelsio/chcr_algo.c: In function 'create_authenc_wr': drivers/crypto/chelsio/chcr_algo.c:2113:2: error: this 'if' clause does not guard... [-Werror=misleading-indentation] if (error) ^~

[PATCH] NTB: ntb_perf: fix printing of resource_size_t

On 32-bit architectures, resource_size_t is usually 'unsigned int' or 'unsigned long' but not 'unsigned long long', so we get a warning about printing the wrong data: drivers/ntb/test/ntb_perf.c: In function 'perf_setup_peer_mw': drivers/ntb/test/ntb_perf.c:1390:35: error: format '%llx' expects

[PATCH] NTB: ntb_perf: fix printing of resource_size_t

On 32-bit architectures, resource_size_t is usually 'unsigned int' or 'unsigned long' but not 'unsigned long long', so we get a warning about printing the wrong data: drivers/ntb/test/ntb_perf.c: In function 'perf_setup_peer_mw': drivers/ntb/test/ntb_perf.c:1390:35: error: format '%llx' expects

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Jan 18, 2018 at 02:59:48PM +0100, Jiri Olsa escreveu: > > > On Thu, Jan 18, 2018 at 10:41:39AM -0300, Arnaldo Carvalho de Melo wrote: > > > >

Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library

Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu: > On Thu, Jan 18, 2018 at 11:14:23AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Jan 18, 2018 at 02:59:48PM +0100, Jiri Olsa escreveu: > > > On Thu, Jan 18, 2018 at 10:41:39AM -0300, Arnaldo Carvalho de Melo wrote: > > > >

[PATCH] mmc: tmio: hide unused tmio_mmc_clk_disable/tmio_mmc_clk_enable functions

When CONFIG_PM is disabled, we get a warning about the clock handling being unused: drivers/mmc/host/tmio_mmc_core.c:937:13: error: 'tmio_mmc_clk_disable' defined but not used [-Werror=unused-function] static void tmio_mmc_clk_disable(struct tmio_mmc_host *host)

[PATCH] mmc: tmio: hide unused tmio_mmc_clk_disable/tmio_mmc_clk_enable functions

When CONFIG_PM is disabled, we get a warning about the clock handling being unused: drivers/mmc/host/tmio_mmc_core.c:937:13: error: 'tmio_mmc_clk_disable' defined but not used [-Werror=unused-function] static void tmio_mmc_clk_disable(struct tmio_mmc_host *host)

[PATCH] kasan: don't emit builtin calls when sanitization is off

With KASAN enabled the kernel has two different memset() functions, one with KASAN checks (memset) and one without (__memset). KASAN uses some macro tricks to use the proper version where required. For example memset() calls in mm/slub.c are without KASAN checks, since they operate on poisoned

[PATCH] kasan: don't emit builtin calls when sanitization is off

With KASAN enabled the kernel has two different memset() functions, one with KASAN checks (memset) and one without (__memset). KASAN uses some macro tricks to use the proper version where required. For example memset() calls in mm/slub.c are without KASAN checks, since they operate on poisoned

[PATCH] NFSD: hide unused svcxdr_dupstr()

There is now only one caller left for svcxdr_dupstr() and this is inside of an #ifdef, so we can get a warning when the option is disabled: fs/nfsd/nfs4xdr.c:241:1: error: 'svcxdr_dupstr' defined but not used [-Werror=unused-function] This adds another #ifdef around the definition. Fixes:

[PATCH] NFSD: hide unused svcxdr_dupstr()

There is now only one caller left for svcxdr_dupstr() and this is inside of an #ifdef, so we can get a warning when the option is disabled: fs/nfsd/nfs4xdr.c:241:1: error: 'svcxdr_dupstr' defined but not used [-Werror=unused-function] This adds another #ifdef around the definition. Fixes:

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote: > 2018-01-18 19:02 GMT+08:00 Arnd Bergmann : >> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: >>> From: Greentime Hu >>> >>> This patch adds nds32 CPU

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote: > 2018-01-18 19:02 GMT+08:00 Arnd Bergmann : >> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: >>> From: Greentime Hu >>> >>> This patch adds nds32 CPU binding documents. >>> >>> Signed-off-by: Vincent Chen >>> Signed-off-by: Rick Chen

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: >> Currently mem_cgroup_resize_limit() retries to set limit after reclaiming >> 32 pages. It makes more sense to reclaim needed amount of pages right away. >> >> This works

Re: [PATCH v5 2/2] mm/memcontrol.c: Reduce reclaim retries in mem_cgroup_resize_limit()

On Fri, Jan 19, 2018 at 5:35 AM, Michal Hocko wrote: > On Fri 19-01-18 16:25:44, Andrey Ryabinin wrote: >> Currently mem_cgroup_resize_limit() retries to set limit after reclaiming >> 32 pages. It makes more sense to reclaim needed amount of pages right away. >> >> This works noticeably faster,

Re: [PATCH] phy: allwinner: sun4i-usb: poll vbus changes on A23/A33 when driving VBUS

On Fri, Jan 19, 2018 at 05:25:41PM +0800, Chen-Yu Tsai wrote: > The AXP223 PMIC, like the AXP221, does not generate VBUS change > interrupts when N_VBUSEN is used to drive VBUS for the OTG port > on the board. > > This was not noticed until recently, as most A23/A33 boards use > a GPIO pin that

Re: [PATCH] phy: allwinner: sun4i-usb: poll vbus changes on A23/A33 when driving VBUS

On Fri, Jan 19, 2018 at 05:25:41PM +0800, Chen-Yu Tsai wrote: > The AXP223 PMIC, like the AXP221, does not generate VBUS change > interrupts when N_VBUSEN is used to drive VBUS for the OTG port > on the board. > > This was not noticed until recently, as most A23/A33 boards use > a GPIO pin that

Re: [PATCH v5 02/19] fs: don't take the i_lock in inode_inc_iversion

On Fri, Jan 19, 2018 at 09:36:34AM -0500, Jeff Layton wrote: > Shrug...we have that problem with the spinlock in place too. The bottom > line is that reads of this value are not serialized with the increment > at all. OK, so this wouldn't even be a new bug. > I'm not 100% thrilled with this

Re: [PATCH v5 02/19] fs: don't take the i_lock in inode_inc_iversion

On Fri, Jan 19, 2018 at 09:36:34AM -0500, Jeff Layton wrote: > Shrug...we have that problem with the spinlock in place too. The bottom > line is that reads of this value are not serialized with the increment > at all. OK, so this wouldn't even be a new bug. > I'm not 100% thrilled with this

Re: [PATCH bpf-next] bpftool: recognize BPF_PROG_TYPE_CGROUP_DEVICE programs

2018-01-19 14:17 UTC+ ~ Roman Gushchin > On Mon, Jan 15, 2018 at 07:32:01PM +, Quentin Monnet wrote: [...] >> Looks good, thanks Roman! >> Would you mind updating the map names as well? It seems the >> BPF_MAP_TYPE_CPUMAP is missing from the list in map.c. > > Hello,

Re: [PATCH bpf-next] bpftool: recognize BPF_PROG_TYPE_CGROUP_DEVICE programs

2018-01-19 14:17 UTC+ ~ Roman Gushchin > On Mon, Jan 15, 2018 at 07:32:01PM +, Quentin Monnet wrote: [...] >> Looks good, thanks Roman! >> Would you mind updating the map names as well? It seems the >> BPF_MAP_TYPE_CPUMAP is missing from the list in map.c. > > Hello, Quentin! > > >

Re: [PATCH v5 02/19] fs: don't take the i_lock in inode_inc_iversion

On Thu, 2018-01-18 at 16:45 -0500, J. Bruce Fields wrote: > On Tue, Jan 09, 2018 at 09:10:42AM -0500, Jeff Layton wrote: > > From: Jeff Layton > > > > The rationale for taking the i_lock when incrementing this value is > > lost in antiquity. The readers of the field don't

Re: [PATCH v5 02/19] fs: don't take the i_lock in inode_inc_iversion

On Thu, 2018-01-18 at 16:45 -0500, J. Bruce Fields wrote: > On Tue, Jan 09, 2018 at 09:10:42AM -0500, Jeff Layton wrote: > > From: Jeff Layton > > > > The rationale for taking the i_lock when incrementing this value is > > lost in antiquity. The readers of the field don't take it (at least > >

[PATCH v1] x86/io: Define readq()/writeq() to use 64-bit type

Since non atomic readq() and writeq() were added some of the drivers would like to use it in a manner of: #include ... pr_debug("Debug value of some register: %016llx\n", readq(addr)); However, lo_hi_readq() always returns __u64 data, while readq() on x86_64 defines it as unsigned long. and

[PATCH v1] x86/io: Define readq()/writeq() to use 64-bit type

Since non atomic readq() and writeq() were added some of the drivers would like to use it in a manner of: #include ... pr_debug("Debug value of some register: %016llx\n", readq(addr)); However, lo_hi_readq() always returns __u64 data, while readq() on x86_64 defines it as unsigned long. and

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

2018-01-18 19:02 GMT+08:00 Arnd Bergmann : > On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: >> From: Greentime Hu >> >> This patch adds nds32 CPU binding documents. >> >> Signed-off-by: Vincent Chen >>

Re: [PATCH v6 31/36] dt-bindings: nds32 CPU Bindings

2018-01-18 19:02 GMT+08:00 Arnd Bergmann : > On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote: >> From: Greentime Hu >> >> This patch adds nds32 CPU binding documents. >> >> Signed-off-by: Vincent Chen >> Signed-off-by: Rick Chen >> Signed-off-by: Zong Li >> Signed-off-by: Greentime Hu >>

[PULL REQUEST] i2c for v4.15

Linus, here are two bugfixes for the I2C core: Lixing Wang fixed a refcounting problem with DT nodes. Jeremy Compostella fixed a buffer overflow possibility when using a 'don't use' ioctl interface directly. Please pull. Thanks, Wolfram The following changes since commit

[PULL REQUEST] i2c for v4.15

Linus, here are two bugfixes for the I2C core: Lixing Wang fixed a refcounting problem with DT nodes. Jeremy Compostella fixed a buffer overflow possibility when using a 'don't use' ioctl interface directly. Please pull. Thanks, Wolfram The following changes since commit

Re: [PATCH v2 07/11] arm64: Add skeleton to harden the branch predictor against aliasing attacks

On Fri, Jan 19, 2018 at 11:37:24AM +0800, Li Kun wrote: > 在 2018/1/17 18:07, Will Deacon 写道: > >On Wed, Jan 17, 2018 at 12:10:33PM +0800, Yisheng Xie wrote: > >>On 2018/1/5 21:12, Will Deacon wrote: > >>>diff --git a/arch/arm64/mm/context.c b/arch/arm64/mm/context.c > >>>index

Re: [PATCH v2 07/11] arm64: Add skeleton to harden the branch predictor against aliasing attacks

On Fri, Jan 19, 2018 at 11:37:24AM +0800, Li Kun wrote: > 在 2018/1/17 18:07, Will Deacon 写道: > >On Wed, Jan 17, 2018 at 12:10:33PM +0800, Yisheng Xie wrote: > >>On 2018/1/5 21:12, Will Deacon wrote: > >>>diff --git a/arch/arm64/mm/context.c b/arch/arm64/mm/context.c > >>>index

<    4   5   6   7   8   9   10   11   12   13   >