Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore

On 12/19/17 at 06:58pm, Jiri Bohac wrote: Sorry for late response. Please see the inline comments. > > On Tue, Dec 19, 2017 at 09:58:04AM +0800, Baoquan He wrote: > > Hmm, as I have said in the first replying mail, the v2 will introduce > > issues: > > > > 1) If 'iommu=off' is specified in 1st

Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore

On 12/19/17 at 06:58pm, Jiri Bohac wrote: Sorry for late response. Please see the inline comments. > > On Tue, Dec 19, 2017 at 09:58:04AM +0800, Baoquan He wrote: > > Hmm, as I have said in the first replying mail, the v2 will introduce > > issues: > > > > 1) If 'iommu=off' is specified in 1st

Re: [PATCH v2] zram: better utilization of zram swap space

On (12/27/17 15:29), Minchan Kim wrote: > On Fri, Dec 22, 2017 at 04:00:06PM +0530, Gopi Sai Teja wrote: > > 75% of the PAGE_SIZE is not a correct threshold to store uncompressed > > Please describe it in detail that why current threshold is bad in that > memory efficiency point of view. > > >

Re: [PATCH v2] zram: better utilization of zram swap space

On (12/27/17 15:29), Minchan Kim wrote: > On Fri, Dec 22, 2017 at 04:00:06PM +0530, Gopi Sai Teja wrote: > > 75% of the PAGE_SIZE is not a correct threshold to store uncompressed > > Please describe it in detail that why current threshold is bad in that > memory efficiency point of view. > > >

Re: [PATCH v2 2/3] dt-bindings: PCI: dra7xx: Add properties to enable x2 lane in dra7

Hi, On Tuesday 26 December 2017 11:40 PM, Tony Lindgren wrote: > * Rob Herring [171226 17:49]: >> On Fri, Dec 22, 2017 at 12:24 PM, Tony Lindgren wrote: >>> * Kishon Vijay Abraham I [171222 06:06]: Hi Rob, On Thursday 21 December

Re: [PATCH v2 2/3] dt-bindings: PCI: dra7xx: Add properties to enable x2 lane in dra7

Hi, On Tuesday 26 December 2017 11:40 PM, Tony Lindgren wrote: > * Rob Herring [171226 17:49]: >> On Fri, Dec 22, 2017 at 12:24 PM, Tony Lindgren wrote: >>> * Kishon Vijay Abraham I [171222 06:06]: Hi Rob, On Thursday 21 December 2017 12:27 AM, Rob Herring wrote: > On Tue,

Re: [PATCH v2] zram: better utilization of zram swap space

Hello, On Fri, Dec 22, 2017 at 04:00:06PM +0530, Gopi Sai Teja wrote: > 75% of the PAGE_SIZE is not a correct threshold to store uncompressed Please describe it in detail that why current threshold is bad in that memory efficiency point of view. > pages in zs_page as this must be changed if the

Re: [PATCH v2] zram: better utilization of zram swap space

Hello, On Fri, Dec 22, 2017 at 04:00:06PM +0530, Gopi Sai Teja wrote: > 75% of the PAGE_SIZE is not a correct threshold to store uncompressed Please describe it in detail that why current threshold is bad in that memory efficiency point of view. > pages in zs_page as this must be changed if the

Re: [PATCH -next v3 1/2] mtd: nand: toshiba: Retrieve ECC requirements from extended ID

On 2017/12/19 20:56, Boris Brezillon wrote: > On Tue, 19 Dec 2017 20:42:36 +0900 > KOBAYASHI Yoshitake wrote: > >> On 2017/12/07 0:08, Boris Brezillon wrote: >>> On Wed, 6 Dec 2017 23:04:57 +0900 >>> KOBAYASHI Yoshitake

Re: [PATCH -next v3 1/2] mtd: nand: toshiba: Retrieve ECC requirements from extended ID

On 2017/12/19 20:56, Boris Brezillon wrote: > On Tue, 19 Dec 2017 20:42:36 +0900 > KOBAYASHI Yoshitake wrote: > >> On 2017/12/07 0:08, Boris Brezillon wrote: >>> On Wed, 6 Dec 2017 23:04:57 +0900 >>> KOBAYASHI Yoshitake wrote: >>> This patch enables support to read the ECC strength and

Re: [RFC 2/2] pci: dwc: pci-exynos: add the codes to support the exynos5433

On 12/27/2017 06:11 AM, Rob Herring wrote: > On Thu, Dec 21, 2017 at 09:14:07PM +0900, Jaehoon Chung wrote: >> Exynos5433 has the PCIe for WiFi. >> Added the codes relevant to PCIe for supporting the exynos5433. >> Also changed the binding documentation name to >> 'samsung,exynos-pcie.txt'. >>

Re: [RFC 2/2] pci: dwc: pci-exynos: add the codes to support the exynos5433

On 12/27/2017 06:11 AM, Rob Herring wrote: > On Thu, Dec 21, 2017 at 09:14:07PM +0900, Jaehoon Chung wrote: >> Exynos5433 has the PCIe for WiFi. >> Added the codes relevant to PCIe for supporting the exynos5433. >> Also changed the binding documentation name to >> 'samsung,exynos-pcie.txt'. >>

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: > On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote: > > Check whether error injectable event is on function entry or not. > > Currently it checks the event is ftrace-based kprobes or not, >

Re: [RFC PATCH bpf-next v2 1/4] tracing/kprobe: bpf: Check error injectable event is on function entry

On Tue, 26 Dec 2017 17:57:32 -0800 Alexei Starovoitov wrote: > On Tue, Dec 26, 2017 at 04:46:59PM +0900, Masami Hiramatsu wrote: > > Check whether error injectable event is on function entry or not. > > Currently it checks the event is ftrace-based kprobes or not, > > but that is wrong. It

[PATCH 3/3] staging: irda: separate multiple assignments

Clean up checkpatch warning: CHECK: multiple assignments should be avoided Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c

[PATCH 3/3] staging: irda: separate multiple assignments

Clean up checkpatch warning: CHECK: multiple assignments should be avoided Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c b/drivers/staging/irda/drivers/esi-sir.c

[PATCH 2/3] staging: irda: add spaces around '|' operator

Clean up checkpatch warning: CHECK: spaces preferred around that '|' (ctx:VxV) Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c

[PATCH 2/3] staging: irda: add spaces around '|' operator

Clean up checkpatch warning: CHECK: spaces preferred around that '|' (ctx:VxV) Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c

[PATCH 1/3] staging: irda: fix type from "unsigned" to "unsigned int"

Clean up checkpatch warning: WARNING: Prefer 'unsigned int' to bare use of 'unsigned' Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c

[PATCH 1/3] staging: irda: fix type from "unsigned" to "unsigned int"

Clean up checkpatch warning: WARNING: Prefer 'unsigned int' to bare use of 'unsigned' Signed-off-by: JI-HUN KIM --- drivers/staging/irda/drivers/esi-sir.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/irda/drivers/esi-sir.c

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Dong Aisheng [mailto:donga...@gmail.com] > Sent: Wednesday, December 27, 2017 10:51 AM > To: A.s. Dong > Cc: Shawn Guo ; Peng Fan ; > linux-kernel@vger.kernel.org; Russell King

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Dong Aisheng [mailto:donga...@gmail.com] > Sent: Wednesday, December 27, 2017 10:51 AM > To: A.s. Dong > Cc: Shawn Guo ; Peng Fan ; > linux-kernel@vger.kernel.org; Russell King ; Fabio > Estevam ; Sascha Hauer ; > van.free...@gmail.com;

Re: [PATCH net-next v5 1/6] net: tcp: Add trace events for TCP congestion window tracing

On Tue, 26 Dec 2017 18:51:55 -0500 (EST) David Miller wrote: > From: Masami Hiramatsu > Date: Fri, 22 Dec 2017 11:05:33 +0900 > > > This adds an event to trace TCP stat variables with > > slightly intrusive trace-event. This uses ftrace/perf > > event

[PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors

AMD processors are not subject to the types of attacks that the kernel page table isolation feature protects against. The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that

Re: [PATCH net-next v5 1/6] net: tcp: Add trace events for TCP congestion window tracing

On Tue, 26 Dec 2017 18:51:55 -0500 (EST) David Miller wrote: > From: Masami Hiramatsu > Date: Fri, 22 Dec 2017 11:05:33 +0900 > > > This adds an event to trace TCP stat variables with > > slightly intrusive trace-event. This uses ftrace/perf > > event log buffer to trace those state, no needs

[PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors

AMD processors are not subject to the types of attacks that the kernel page table isolation feature protects against. The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that

Re: [PATCH v4] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

When all the patch issues are ironed out consider this Acked-by: Tony Luck I was planning to hunt down the erratum when I got back from vacation in the new year. Sent from my iPhone > On Dec 26, 2017, at 04:42, Jia Zhang wrote: > > Instead

Re: [PATCH v4] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

When all the patch issues are ironed out consider this Acked-by: Tony Luck I was planning to hunt down the erratum when I got back from vacation in the new year. Sent from my iPhone > On Dec 26, 2017, at 04:42, Jia Zhang wrote: > > Instead of blacklisting all types of Broadwell processor

[PATCH] rpmsg: virtio_rpmsg_bus: fix rpmsg_probe() for virtio-mmio transport

When virtio-rpmsg device is provided via virtio-mmio transport, the dma_alloc_coherent() (called by rpmsg_probe()) fails on ARM/ARM64 systems because "vdev->dev.parent->parent" device is used as parameter to dma_alloc_coherent(). The "vdev->dev.parent->parent" device represents underlying

[PATCH] rpmsg: virtio_rpmsg_bus: fix rpmsg_probe() for virtio-mmio transport

When virtio-rpmsg device is provided via virtio-mmio transport, the dma_alloc_coherent() (called by rpmsg_probe()) fails on ARM/ARM64 systems because "vdev->dev.parent->parent" device is used as parameter to dma_alloc_coherent(). The "vdev->dev.parent->parent" device represents underlying

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 26-12-17, 14:23, Rob Herring wrote: > > cpu_opp_table: cpu_opp_table { > > compatible = "operating-points-v2"; > > opp-shared; > > > > opp00 { > > opp-hz = /bits/ 64 <20800>; > >

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 26-12-17, 14:23, Rob Herring wrote: > > cpu_opp_table: cpu_opp_table { > > compatible = "operating-points-v2"; > > opp-shared; > > > > opp00 { > > opp-hz = /bits/ 64 <20800>; > >

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

Sounds like it's been pinned down then. Just confirming this: On Tue, Dec 26, 2017 at 06:16:37PM -0800, Linus Torvalds wrote: > On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu > wrote: > > > > I went back to the initial problematic commit e802a51 and modified it as >

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

Sounds like it's been pinned down then. Just confirming this: On Tue, Dec 26, 2017 at 06:16:37PM -0800, Linus Torvalds wrote: > On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu > wrote: > > > > I went back to the initial problematic commit e802a51 and modified it as > > you suggest: > >

Re: BUG warnings in 4.14.9

On Tue, Dec 26, 2017 at 10:54:37PM +0200, Ido Schimmel wrote: >On Tue, Dec 26, 2017 at 07:59:55PM +0100, Willy Tarreau wrote: >> Guys, >> >> Chris reported the bug below and confirmed that reverting commit >> 9704f81 (ipv6: grab rt->rt6i_ref before allocating pcpu rt) seems to >> have fixed the

Re: BUG warnings in 4.14.9

On Tue, Dec 26, 2017 at 10:54:37PM +0200, Ido Schimmel wrote: >On Tue, Dec 26, 2017 at 07:59:55PM +0100, Willy Tarreau wrote: >> Guys, >> >> Chris reported the bug below and confirmed that reverting commit >> 9704f81 (ipv6: grab rt->rt6i_ref before allocating pcpu rt) seems to >> have fixed the

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

On Wed, Dec 27, 2017 at 12:10 PM, Icenowy Zheng wrote: > 在 2017年12月27日星期三 CST 下午12:09:41，Chen-Yu Tsai 写道： >> On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: >> > This patchset adds support for the SimpleFB on Allwinner SoCs with >> > "Display Engine 2.0".

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

On Wed, Dec 27, 2017 at 12:10 PM, Icenowy Zheng wrote: > 在 2017年12月27日星期三 CST 下午12:09:41，Chen-Yu Tsai 写道： >> On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: >> > This patchset adds support for the SimpleFB on Allwinner SoCs with >> > "Display Engine 2.0". >> > >> > PATCH 1 to PATCH 3 are

Re: [PATCH] ARM: dts: ls1021a: fix incorrect clock references

On Thu, Dec 21, 2017 at 10:44:20PM +0100, Arnd Bergmann wrote: > dtc warns about two 'clocks' properties that have an extraneous '1' > at the end: > > arch/arm/boot/dts/ls1021a-qds.dtb: Warning (clocks_property): > arch/arm/boot/dts/ls1021a-twr.dtb: Warning (clocks_property): Property >

Re: [PATCH] ARM: dts: ls1021a: fix incorrect clock references

On Thu, Dec 21, 2017 at 10:44:20PM +0100, Arnd Bergmann wrote: > dtc warns about two 'clocks' properties that have an extraneous '1' > at the end: > > arch/arm/boot/dts/ls1021a-qds.dtb: Warning (clocks_property): > arch/arm/boot/dts/ls1021a-twr.dtb: Warning (clocks_property): Property >

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

在 2017年12月27日星期三 CST 下午12:09:41，Chen-Yu Tsai 写道： > On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: > > This patchset adds support for the SimpleFB on Allwinner SoCs with > > "Display Engine 2.0". > > > > PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs. > > > > PATCH 4

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

在 2017年12月27日星期三 CST 下午12:09:41，Chen-Yu Tsai 写道： > On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: > > This patchset adds support for the SimpleFB on Allwinner SoCs with > > "Display Engine 2.0". > > > > PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs. > > > > PATCH 4 adds the

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: > This patchset adds support for the SimpleFB on Allwinner SoCs with > "Display Engine 2.0". > > PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs. > > PATCH 4 adds the pipeline strings for DE2 SimpleFB. > > PATCH 5 to 7

Re: [PATCH v3 00/11] Allwinner H3/H5/A64(DE2) SimpleFB support

On Fri, Dec 22, 2017 at 8:22 PM, Icenowy Zheng wrote: > This patchset adds support for the SimpleFB on Allwinner SoCs with > "Display Engine 2.0". > > PATCH 1 to PATCH 3 are DE2 CCU fixes for H3/H5 SoCs. > > PATCH 4 adds the pipeline strings for DE2 SimpleFB. > > PATCH 5 to 7 adds necessary

Re: [PATCH] clk: mediatek: remove superfluous line including linux/clk-provider.h

On Tue, 2017-12-26 at 17:15 -0800, Stephen Boyd wrote: > On 12/25, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > clk-mtk.h has already included linux/clk-provider.h inside, so remove > > the superfluous line including linux/clk-provider.h from these files

Re: [PATCH] clk: mediatek: remove superfluous line including linux/clk-provider.h

On Tue, 2017-12-26 at 17:15 -0800, Stephen Boyd wrote: > On 12/25, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > clk-mtk.h has already included linux/clk-provider.h inside, so remove > > the superfluous line including linux/clk-provider.h from these files which > > also included

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:43:40PM -0800, Matthew Wilcox wrote: > Also add the xa_lock() and xa_unlock() family of wrappers to make it > easier to use the lock. If we could rely on -fplan9-extensions in > the compiler, we could avoid all of this syntactic sugar, but that > wasn't

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:43:40PM -0800, Matthew Wilcox wrote: > Also add the xa_lock() and xa_unlock() family of wrappers to make it > easier to use the lock. If we could rely on -fplan9-extensions in > the compiler, we could avoid all of this syntactic sugar, but that > wasn't

[PATCH 1/2] ARM: dts: imx6: RDU2: disable internal watchdog

The system has an external watchdog in the environment processor so the internal watchdog is of no use. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland Cc:

[PATCH 1/2] ARM: dts: imx6: RDU2: disable internal watchdog

The system has an external watchdog in the environment processor so the internal watchdog is of no use. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland Cc: linux-arm-ker...@lists.infradead.org Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 2/2] ARM: dts: imx6: RDU2: correct RTC compatible

The RTC is manufactured by Maxim. This is a cosmetic fix, as Linux doesn't match the vendor string for i2c devices. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland Cc:

[PATCH 2/2] ARM: dts: imx6: RDU2: correct RTC compatible

The RTC is manufactured by Maxim. This is a cosmetic fix, as Linux doesn't match the vendor string for i2c devices. Cc: Sascha Hauer Cc: Fabio Estevam Cc: Rob Herring Cc: Mark Rutland Cc: linux-arm-ker...@lists.infradead.org Cc: devicet...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Cc:

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:54:40PM +0300, Kirill A. Shutemov wrote: > On Fri, Dec 15, 2017 at 02:03:35PM -0800, Matthew Wilcox wrote: > > From: Matthew Wilcox > > > > This results in no change in structure size on 64-bit x86 as it fits in > > the padding between the gfp_t

Re: [PATCH v5 03/78] xarray: Add the xa_lock to the radix_tree_root

On Tue, Dec 26, 2017 at 07:54:40PM +0300, Kirill A. Shutemov wrote: > On Fri, Dec 15, 2017 at 02:03:35PM -0800, Matthew Wilcox wrote: > > From: Matthew Wilcox > > > > This results in no change in structure size on 64-bit x86 as it fits in > > the padding between the gfp_t and the void *. > >

Re: [PATCH] clk: mediatek: remove unnecessary include header from reset.c

On Tue, 2017-12-26 at 17:10 -0800, Stephen Boyd wrote: > On 12/25, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > In fact, the clk-mtk.h header is indeed not needed for reset.c and thus > > it's safe and good change to remove it from the file. > > > >

Re: [PATCH] clk: mediatek: remove unnecessary include header from reset.c

On Tue, 2017-12-26 at 17:10 -0800, Stephen Boyd wrote: > On 12/25, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > In fact, the clk-mtk.h header is indeed not needed for reset.c and thus > > it's safe and good change to remove it from the file. > > > > Signed-off-by: Sean Wang > >

Re: [PATCH v5 06/78] xarray: Change definition of sibling entries

On Tue, Dec 26, 2017 at 08:21:53PM +0300, Kirill A. Shutemov wrote: > > +/** > > + * xa_is_internal() - Is the entry an internal entry? > > + * @entry: Entry retrieved from the XArray > > + * > > + * Return: %true if the entry is an internal entry. > > + */ > > What does it mean "internal entry"?

Re: [PATCH v5 06/78] xarray: Change definition of sibling entries

On Tue, Dec 26, 2017 at 08:21:53PM +0300, Kirill A. Shutemov wrote: > > +/** > > + * xa_is_internal() - Is the entry an internal entry? > > + * @entry: Entry retrieved from the XArray > > + * > > + * Return: %true if the entry is an internal entry. > > + */ > > What does it mean "internal entry"?

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On December 26, 2017 6:54:55 PM PST, Linus Torvalds wrote: >On Tue, Dec 26, 2017 at 6:25 PM, wrote: >> >> This is why I personally prefer to see these kinds of terminal stubs >written in assembly explicitly: the C compiler simply doesn't have all

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On December 26, 2017 6:54:55 PM PST, Linus Torvalds wrote: >On Tue, Dec 26, 2017 at 6:25 PM, wrote: >> >> This is why I personally prefer to see these kinds of terminal stubs >written in assembly explicitly: the C compiler simply doesn't have all >the information needed to do the right thing.

Re: [PATCH] mmc: sdhci: disable irq in sdhci host suspend ranther than free this irq

Hi All, Sorry for bring back this old topic again. On Thu, Jan 28, 2016 at 05:27:46PM +0100, Thomas Gleixner wrote: >On Thu, 28 Jan 2016, Thomas Gleixner wrote: >> On Thu, 28 Jan 2016, Ulf Hansson wrote: >> > Therefore, the only way we currently can make sure to don't get the >> > IRQ is to free

Re: [PATCH] mmc: sdhci: disable irq in sdhci host suspend ranther than free this irq

Hi All, Sorry for bring back this old topic again. On Thu, Jan 28, 2016 at 05:27:46PM +0100, Thomas Gleixner wrote: >On Thu, 28 Jan 2016, Thomas Gleixner wrote: >> On Thu, 28 Jan 2016, Ulf Hansson wrote: >> > Therefore, the only way we currently can make sure to don't get the >> > IRQ is to free

[PATCH 09/11 v3] ARM: orion5x: constify gpio_led

gpio_led are not supposed to change at runtime. struct gpio_led_platform_data working with const gpio_led provided by . So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- changes in v2: The GPIO LED driver can be built as a module, it

[PATCH 09/11 v3] ARM: orion5x: constify gpio_led

gpio_led are not supposed to change at runtime. struct gpio_led_platform_data working with const gpio_led provided by . So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- changes in v2: The GPIO LED driver can be built as a module, it can be

Re: [GIT PULL] hwmon fixes for v4.15-rc6

On 12/26/2017 06:25 PM, Linus Torvalds wrote: On Tue, Dec 26, 2017 at 5:41 PM, Guenter Roeck wrote: Please pull hwmon fixes for Linux v4.15-rc6 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.15-rc6 Hmm.

Re: [GIT PULL] hwmon fixes for v4.15-rc6

On 12/26/2017 06:25 PM, Linus Torvalds wrote: On Tue, Dec 26, 2017 at 5:41 PM, Guenter Roeck wrote: Please pull hwmon fixes for Linux v4.15-rc6 from signed tag: git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.15-rc6 Hmm. That was a tag, but

Re: [lkp-robot] [bpf] 82abbf8d2f: kernel_selftests.bpf.test_align.fail

On Wed, Dec 27, 2017 at 11:00:30AM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): > > commit: 82abbf8d2fc46d79611ab58daa7c608df14bb3ee ("bpf: do not allow root to > mangle valid pointers") >

Re: [lkp-robot] [bpf] 82abbf8d2f: kernel_selftests.bpf.test_align.fail

On Wed, Dec 27, 2017 at 11:00:30AM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-7): > > commit: 82abbf8d2fc46d79611ab58daa7c608df14bb3ee ("bpf: do not allow root to > mangle valid pointers") >

Re: [PATCH v5 05/78] xarray: Replace exceptional entries

On Tue, Dec 26, 2017 at 08:15:42PM +0300, Kirill A. Shutemov wrote: > > 28 files changed, 249 insertions(+), 240 deletions(-) > > Everything looks fine to me after quick scan, but hat's a lot of changes for > one patch... Yeah. It's pretty mechanical though. > > - if

Re: [PATCH v5 05/78] xarray: Replace exceptional entries

On Tue, Dec 26, 2017 at 08:15:42PM +0300, Kirill A. Shutemov wrote: > > 28 files changed, 249 insertions(+), 240 deletions(-) > > Everything looks fine to me after quick scan, but hat's a lot of changes for > one patch... Yeah. It's pretty mechanical though. > > - if

[RFC PATCH v2] workqueue: Introduce a way to set percpu worker_pool's scheduler

From: Liu Wei When pinning RT threads to specific cores using CPU affinity, the kworkers on the same CPU would starve, which may lead to some kind of priority inversion. In that case, the RT threads would also suffer high performance impact. The priority inversion looks

[RFC PATCH v2] workqueue: Introduce a way to set percpu worker_pool's scheduler

From: Liu Wei When pinning RT threads to specific cores using CPU affinity, the kworkers on the same CPU would starve, which may lead to some kind of priority inversion. In that case, the RT threads would also suffer high performance impact. The priority inversion looks like, CPU 0: libvirtd

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On Tue, Dec 26, 2017 at 6:25 PM, wrote: > > This is why I personally prefer to see these kinds of terminal stubs written > in assembly explicitly: the C compiler simply doesn't have all the > information needed to do the right thing. > > I'm personally very sceptical to nuking

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On Tue, Dec 26, 2017 at 6:25 PM, wrote: > > This is why I personally prefer to see these kinds of terminal stubs written > in assembly explicitly: the C compiler simply doesn't have all the > information needed to do the right thing. > > I'm personally very sceptical to nuking the GDT unless

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Dong Aisheng [mailto:donga...@gmail.com] > Sent: Wednesday, December 27, 2017 10:51 AM > To: A.s. Dong > Cc: Shawn Guo ; Peng Fan ; > linux-kernel@vger.kernel.org; Russell King

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Dong Aisheng [mailto:donga...@gmail.com] > Sent: Wednesday, December 27, 2017 10:51 AM > To: A.s. Dong > Cc: Shawn Guo ; Peng Fan ; > linux-kernel@vger.kernel.org; Russell King ; Fabio > Estevam ; Sascha Hauer ; > van.free...@gmail.com;

Re: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

On Wed, Dec 27, 2017 at 02:33:57AM +, A.s. Dong wrote: > > -Original Message- > > From: Shawn Guo [mailto:shawn...@kernel.org] > > Sent: Wednesday, December 27, 2017 10:32 AM > > To: Peng Fan > > Cc: A.s. Dong ; linux-kernel@vger.kernel.org;

Re: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

On Wed, Dec 27, 2017 at 02:33:57AM +, A.s. Dong wrote: > > -Original Message- > > From: Shawn Guo [mailto:shawn...@kernel.org] > > Sent: Wednesday, December 27, 2017 10:32 AM > > To: Peng Fan > > Cc: A.s. Dong ; linux-kernel@vger.kernel.org; Russell > > King ; Fabio Estevam ; > >

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On December 26, 2017 6:16:37 PM PST, Linus Torvalds wrote: >On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu > wrote: >> >> I went back to the initial problematic commit e802a51 and modified it >as you suggest: > >Thank you. > >> This did

Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot

On December 26, 2017 6:16:37 PM PST, Linus Torvalds wrote: >On Tue, Dec 26, 2017 at 3:19 PM, Alexandru Chirvasitu > wrote: >> >> I went back to the initial problematic commit e802a51 and modified it >as you suggest: > >Thank you. > >> This did not work out for me, but now it fails differently.

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Wednesday, December 27, 2017 10:32 AM > To: Peng Fan > Cc: A.s. Dong ; linux-kernel@vger.kernel.org; Russell > King ; Fabio Estevam

RE: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

> -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Wednesday, December 27, 2017 10:32 AM > To: Peng Fan > Cc: A.s. Dong ; linux-kernel@vger.kernel.org; Russell > King ; Fabio Estevam ; > Sascha Hauer ; van.free...@gmail.com; linux-arm- > ker...@lists.infradead.org

Re: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

On Wed, Dec 27, 2017 at 09:57:47AM +0800, Peng Fan wrote: > Use outer_disable/resume for suspend/resume. > With the two APIs used, code could be simplified and easy to extend > to introduce l2c_write_sec for i.MX platforms when moving Linux Kernel > runs in non-secure world. > > Signed-off-by:

Re: [PATCH V2] ARM: imx: suspend/resume: use outer_disable/resume

On Wed, Dec 27, 2017 at 09:57:47AM +0800, Peng Fan wrote: > Use outer_disable/resume for suspend/resume. > With the two APIs used, code could be simplified and easy to extend > to introduce l2c_write_sec for i.MX platforms when moving Linux Kernel > runs in non-secure world. > > Signed-off-by:

Re: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

On 12/22/2017 4:42 AM, Xiongwei Song wrote: > The functions vfio_mdev_probe, vfio_mdev_remove and the structure > vfio_mdev_driver are only used in this file, so make them static. > > Clean up sparse warnings: > drivers/vfio/mdev/vfio_mdev.c:114:5: warning: no previous prototype > for

Re: [PATCH v2 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.8

On Fri, Dec 22, 2017 at 06:50:01PM +, Quentin Monnet wrote: > Hi Roman, > > 2017-12-22 16:11 UTC+ ~ Roman Gushchin > > Bpftool build is broken with binutils version 2.28 and later. > > Could you check the binutils version? I believe it changed in 2.29 > instead of 2.28.

Re: [PATCH v2 bpf-next 2/2] tools/bpftool: fix bpftool build with bintutils >= 2.8

On Fri, Dec 22, 2017 at 06:50:01PM +, Quentin Monnet wrote: > Hi Roman, > > 2017-12-22 16:11 UTC+ ~ Roman Gushchin > > Bpftool build is broken with binutils version 2.28 and later. > > Could you check the binutils version? I believe it changed in 2.29 > instead of 2.28. Could you update

Re: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

On 12/22/2017 4:42 AM, Xiongwei Song wrote: > The functions vfio_mdev_probe, vfio_mdev_remove and the structure > vfio_mdev_driver are only used in this file, so make them static. > > Clean up sparse warnings: > drivers/vfio/mdev/vfio_mdev.c:114:5: warning: no previous prototype > for

rename arcs_cmdline to mips_cmdline

This patch should based on "Add YeeLoong support v6"

rename arcs_cmdline to mips_cmdline

This patch should based on "Add YeeLoong support v6"

[PATCH] MIPS: rename arcs_cmdline to mips_cmdline

arcs_cmdline refers to boot cmdline for all machs, not only arc systems. This patch renamed all arcs_cmdline to mips_cmdline. Signed-off-by: Jiaxun Yang --- arch/mips/alchemy/common/prom.c | 6 +++--- arch/mips/ar7/prom.c | 8

[PATCH] MIPS: rename arcs_cmdline to mips_cmdline

arcs_cmdline refers to boot cmdline for all machs, not only arc systems. This patch renamed all arcs_cmdline to mips_cmdline. Signed-off-by: Jiaxun Yang --- arch/mips/alchemy/common/prom.c | 6 +++--- arch/mips/ar7/prom.c | 8

Re: [PATCH]cpuidle: preventive check in cpuidle_select against crash

On Wed, Dec 27, 2017 at 2:57 AM, gaurav jindal wrote: > On Wed, Dec 27, 2017 at 01:42:58AM +0100, Rafael J. Wysocki wrote: >> On Tue, Dec 26, 2017 at 8:26 AM, gaurav jindal >> wrote: >> > When selecting the idle state using cpuidle_select,

Re: [PATCH]cpuidle: preventive check in cpuidle_select against crash

On Wed, Dec 27, 2017 at 2:57 AM, gaurav jindal wrote: > On Wed, Dec 27, 2017 at 01:42:58AM +0100, Rafael J. Wysocki wrote: >> On Tue, Dec 26, 2017 at 8:26 AM, gaurav jindal >> wrote: >> > When selecting the idle state using cpuidle_select, there is no >> > check on cpuidle_curr_governor. In

Re: [PATCH bpf-next 2/3] libbpf: add error reporting in XDP

On Mon, Dec 25, 2017 at 11:13:24PM +0100, Eric Leblond wrote: > Parse netlink ext attribute to get the error message returned by > the card. > > Signed-off-by: Eric Leblond ... > diff --git a/tools/lib/bpf/nlattr.c b/tools/lib/bpf/nlattr.c > new file mode 100644 > index

Re: [PATCH bpf-next 2/3] libbpf: add error reporting in XDP

On Mon, Dec 25, 2017 at 11:13:24PM +0100, Eric Leblond wrote: > Parse netlink ext attribute to get the error message returned by > the card. > > Signed-off-by: Eric Leblond ... > diff --git a/tools/lib/bpf/nlattr.c b/tools/lib/bpf/nlattr.c > new file mode 100644 > index

Re: [GIT PULL] hwmon fixes for v4.15-rc6

On Tue, Dec 26, 2017 at 5:41 PM, Guenter Roeck wrote: > > Please pull hwmon fixes for Linux v4.15-rc6 from signed tag: > > git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git > hwmon-for-linus-v4.15-rc6 Hmm. That was a tag, but not a signed one. It's

Re: [GIT PULL] hwmon fixes for v4.15-rc6

On Tue, Dec 26, 2017 at 5:41 PM, Guenter Roeck wrote: > > Please pull hwmon fixes for Linux v4.15-rc6 from signed tag: > > git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git > hwmon-for-linus-v4.15-rc6 Hmm. That was a tag, but not a signed one. It's just a naked tag that

Re: [PATCH] clk: fix reentrancy of clk_enable() on UP systems

On 12/26, David Lechner wrote: > Reentrant calls to clk_enable() are not working on UP systems. This is > caused by the fact spin_trylock_irqsave() always returns true when > CONFIG_SMP=n (and CONFIG_DEBUG_SPINLOCK=n) which causes the reference > counting to not work correctly when

Re: [PATCH] clk: fix reentrancy of clk_enable() on UP systems

On 12/26, David Lechner wrote: > Reentrant calls to clk_enable() are not working on UP systems. This is > caused by the fact spin_trylock_irqsave() always returns true when > CONFIG_SMP=n (and CONFIG_DEBUG_SPINLOCK=n) which causes the reference > counting to not work correctly when

  1   2   3   4   5   6   >