Re: [PATCH] ARM: da8xx: use platform data for CFGCHIP syscon regmap

On Thursday 25 January 2018 08:57 PM, Sekhar Nori wrote: > + Arnd, Kishon and Lee for their information. > > On Wednesday 24 January 2018 05:06 AM, David Lechner wrote: >> This converts from using a platform device for the CFGCHIP syscon >> regmap to using platform data to pass the regmap to

Re: [PATCH] ARM: da8xx: use platform data for CFGCHIP syscon regmap

On Thursday 25 January 2018 08:57 PM, Sekhar Nori wrote: > + Arnd, Kishon and Lee for their information. > > On Wednesday 24 January 2018 05:06 AM, David Lechner wrote: >> This converts from using a platform device for the CFGCHIP syscon >> regmap to using platform data to pass the regmap to

Re: [PATCH 8/9] nvme-pci: break up nvme_timeout and nvme_dev_disable

Hi Sagi Just make some supplement here. On 02/12/2018 10:16 AM, jianchao.wang wrote: >> I think this is going in the wrong direction. Every state that is needed >> to handle serialization should be done in core ctrl state. Moreover, >> please try to avoid handling this locally in nvme-pci, place

Re: [PATCH 8/9] nvme-pci: break up nvme_timeout and nvme_dev_disable

Hi Sagi Just make some supplement here. On 02/12/2018 10:16 AM, jianchao.wang wrote: >> I think this is going in the wrong direction. Every state that is needed >> to handle serialization should be done in core ctrl state. Moreover, >> please try to avoid handling this locally in nvme-pci, place

Re: [PATCHv3 0/5] x86: Enumerate TME and PCONFIG, add MKTME_KEY_PROG helper

On Sun, Feb 11, 2018 at 08:02:41PM +0100, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > Multikey Total Memory Encryption (MKTME)[1] is a technology that allows > > transparent memory encryption in upcoming Intel platforms. > > > > MKTME is built on

Re: [PATCHv3 0/5] x86: Enumerate TME and PCONFIG, add MKTME_KEY_PROG helper

On Sun, Feb 11, 2018 at 08:02:41PM +0100, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > Multikey Total Memory Encryption (MKTME)[1] is a technology that allows > > transparent memory encryption in upcoming Intel platforms. > > > > MKTME is built on top of TME. TME allows encryption

Re: [PATCH 41/80] staging: lustre: lmv: separate master object with master stripe

On Fri, Feb 09, 2018 at 12:39:18PM +1100, NeilBrown wrote: > On Tue, Aug 16 2016, James Simmons wrote: > > > > > +static inline bool > > +lsm_md_eq(const struct lmv_stripe_md *lsm1, const struct lmv_stripe_md > > *lsm2) > > +{ > > + int idx; > > + > > + if (lsm1->lsm_md_magic !=

Re: [PATCH 41/80] staging: lustre: lmv: separate master object with master stripe

On Fri, Feb 09, 2018 at 12:39:18PM +1100, NeilBrown wrote: > On Tue, Aug 16 2016, James Simmons wrote: > > > > > +static inline bool > > +lsm_md_eq(const struct lmv_stripe_md *lsm1, const struct lmv_stripe_md > > *lsm2) > > +{ > > + int idx; > > + > > + if (lsm1->lsm_md_magic !=

Re: [PATCH] Fix copy and paste typo in documentation

On Wed, 31 Jan 2018 18:39:12 +0100, Matthias Lange wrote: > > It's 'optional' instead of 'optinal'. > > Signed-off-by: Matthias Lange Applied, thanks. Takashi

Re: [PATCH] Fix copy and paste typo in documentation

On Wed, 31 Jan 2018 18:39:12 +0100, Matthias Lange wrote: > > It's 'optional' instead of 'optinal'. > > Signed-off-by: Matthias Lange Applied, thanks. Takashi

Re: [PATCH] headers: untangle kmemleak.h from mm.h

* Randy Dunlap wrote: > From: Randy Dunlap > > Currently #includes for no obvious > reason. It looks like it's only a convenience, so remove kmemleak.h > from slab.h and add to any users of kmemleak_* > that don't already #include it. > Also

Re: [PATCH] headers: untangle kmemleak.h from mm.h

* Randy Dunlap wrote: > From: Randy Dunlap > > Currently #includes for no obvious > reason. It looks like it's only a convenience, so remove kmemleak.h > from slab.h and add to any users of kmemleak_* > that don't already #include it. > Also remove from source files that do not use it. >

RE: [PATCH] cpufreq: imx6q: support frequencies >528MHz for i.MX6UL/ULL

Anson Huang Best Regards! > -Original Message- > From: Stefan Agner [mailto:ste...@agner.ch] > Sent: Monday, February 12, 2018 12:18 AM > To: Anson Huang > Cc: Fabio Estevam ; r...@rjwysocki.net; viresh kumar > ;

RE: [PATCH] cpufreq: imx6q: support frequencies >528MHz for i.MX6UL/ULL

Anson Huang Best Regards! > -Original Message- > From: Stefan Agner [mailto:ste...@agner.ch] > Sent: Monday, February 12, 2018 12:18 AM > To: Anson Huang > Cc: Fabio Estevam ; r...@rjwysocki.net; viresh kumar > ; linux...@vger.kernel.org; Marcel Ziswiler > ; max.oss...@gmail.com;

Re: [PATCH] ALSA: usb-audio: add implicit fb quirk for Behringer UFX1204

On Fri, 09 Feb 2018 15:51:36 +0100, Lassi Ylikojola wrote: > > Add quirk to ensure a sync endpoint is properly configured. > This patch is a fix for same symptoms on Behringer UFX1204 as patch > from Albertto Aquirre on Dec 8 2016 for Axe-Fx II. > Resending. Seems that there is a difference

Re: [PATCH] ALSA: usb-audio: add implicit fb quirk for Behringer UFX1204

On Fri, 09 Feb 2018 15:51:36 +0100, Lassi Ylikojola wrote: > > Add quirk to ensure a sync endpoint is properly configured. > This patch is a fix for same symptoms on Behringer UFX1204 as patch > from Albertto Aquirre on Dec 8 2016 for Axe-Fx II. > Resending. Seems that there is a difference

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 10 feb 2018, alle ore 09:29, Oleksandr Natalenko > ha scritto: > > Hi. > > On pátek 9. února 2018 18:29:39 CET Mike Galbraith wrote: >> On Fri, 2018-02-09 at 14:21 +0100, Oleksandr Natalenko wrote: >>> In addition to this I think it should be worth

Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook

> Il giorno 10 feb 2018, alle ore 09:29, Oleksandr Natalenko > ha scritto: > > Hi. > > On pátek 9. února 2018 18:29:39 CET Mike Galbraith wrote: >> On Fri, 2018-02-09 at 14:21 +0100, Oleksandr Natalenko wrote: >>> In addition to this I think it should be worth considering CC'ing Greg >>> to

[PATCH] headers: untangle kmemleak.h from mm.h

From: Randy Dunlap Currently #includes for no obvious reason. It looks like it's only a convenience, so remove kmemleak.h from slab.h and add to any users of kmemleak_* that don't already #include it. Also remove from source files that do not use it. This is tested on

[PATCH] headers: untangle kmemleak.h from mm.h

From: Randy Dunlap Currently #includes for no obvious reason. It looks like it's only a convenience, so remove kmemleak.h from slab.h and add to any users of kmemleak_* that don't already #include it. Also remove from source files that do not use it. This is tested on i386 allmodconfig and

Re: linux-next: manual merge of the tip tree with Linus' tree

* Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/kvm/vmx.c > > between commit: > > c992384bde84 ("KVM: vmx: speed up MSR bitmap merge") > > from Linus' tree and commit: > > ff37dc0cd96c ("KVM/nVMX:

Re: linux-next: manual merge of the tip tree with Linus' tree

* Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/kvm/vmx.c > > between commit: > > c992384bde84 ("KVM: vmx: speed up MSR bitmap merge") > > from Linus' tree and commit: > > ff37dc0cd96c ("KVM/nVMX: Set the

Re: [PATCH] ALSA: ac97: kconfig: Remove select of undefined symbol AC97

On Fri, 09 Feb 2018 00:20:21 +0100, Ulf Magnusson wrote: > > On Fri, Feb 09, 2018 at 12:15:36AM +0100, Ulf Magnusson wrote: > > The AC97_BUS_NEW Kconfig symbol selects the globally undefined symbol > > AC97. > > > > Robert Jarzmik confirmed in https://lkml.org/lkml/2018/2/7/96 that the > >

Re: [PATCH] ALSA: ac97: kconfig: Remove select of undefined symbol AC97

On Fri, 09 Feb 2018 00:20:21 +0100, Ulf Magnusson wrote: > > On Fri, Feb 09, 2018 at 12:15:36AM +0100, Ulf Magnusson wrote: > > The AC97_BUS_NEW Kconfig symbol selects the globally undefined symbol > > AC97. > > > > Robert Jarzmik confirmed in https://lkml.org/lkml/2018/2/7/96 that the > >

Re: [PATCH V6 Resend 00/13] drivers: Boot Constraint core

On 25-01-18, 16:31, Viresh Kumar wrote: > So AFAICT the basic problem I was trying to solve still exists with simple-fb > as well. And the problem is that nothing prevents another driver to get probed > before the display driver (or simple-fb) and reconfigure the resources. Even > if > we let

Re: [PATCH V6 Resend 00/13] drivers: Boot Constraint core

On 25-01-18, 16:31, Viresh Kumar wrote: > So AFAICT the basic problem I was trying to solve still exists with simple-fb > as well. And the problem is that nothing prevents another driver to get probed > before the display driver (or simple-fb) and reconfigure the resources. Even > if > we let

[PATCH 3/3] misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles

To date this driver has relied on prevous state from out of tree hacks and vendor u-boot trees in order to have the host be able to access data over the LPC bus. Now we explicitly enable the AHB to LPC bridge and FWH cycles from when the user first configures the address to map. We chose to do

[PATCH 2/3] misc: aspeed-lpc: Request and enable LPC clock

The LPC device needs to ensure it's clock is enabled before it can do anything. In the past the clock was enabled and left running by u-boot, however Linux now has an upstream clock driver that disables unused clocks. Tested-by: Lei YU Reviewed-by: Andrew Jeffery

[PATCH 3/3] misc: aspeed-lpc-ctrl: Enable FWH and A2H bridge cycles

To date this driver has relied on prevous state from out of tree hacks and vendor u-boot trees in order to have the host be able to access data over the LPC bus. Now we explicitly enable the AHB to LPC bridge and FWH cycles from when the user first configures the address to map. We chose to do

[PATCH 2/3] misc: aspeed-lpc: Request and enable LPC clock

The LPC device needs to ensure it's clock is enabled before it can do anything. In the past the clock was enabled and left running by u-boot, however Linux now has an upstream clock driver that disables unused clocks. Tested-by: Lei YU Reviewed-by: Andrew Jeffery Signed-off-by: Joel Stanley

[PATCH 1/3] dt-bindings: aspeed-lpc: Document LPC Host Interface Controller

The LPC Host Interface Controller is part of a BMC SoC that is used for communication with the host. Signed-off-by: Joel Stanley --- .../devicetree/bindings/mfd/aspeed-lpc.txt | 40 ++ 1 file changed, 40 insertions(+) diff --git

[PATCH 1/3] dt-bindings: aspeed-lpc: Document LPC Host Interface Controller

The LPC Host Interface Controller is part of a BMC SoC that is used for communication with the host. Signed-off-by: Joel Stanley --- .../devicetree/bindings/mfd/aspeed-lpc.txt | 40 ++ 1 file changed, 40 insertions(+) diff --git

[PATCH 0/3] misc: aspeed-lpc-ctrl fixes

These patches were developed when testing upstream Linux with OpenBMC on Romulus. We need to ensure the LPC clock is enabled, now that the clock driver turns off any unused clocks. We also need to enable the LPC firmware cycles bit as we do not intend to upstream any mach-aspeed hacks. There was

[PATCH 0/3] misc: aspeed-lpc-ctrl fixes

These patches were developed when testing upstream Linux with OpenBMC on Romulus. We need to ensure the LPC clock is enabled, now that the clock driver turns off any unused clocks. We also need to enable the LPC firmware cycles bit as we do not intend to upstream any mach-aspeed hacks. There was

Re: [PATCH] staging: android: ion: Initialize dma_address of new sg list

On Fri, Feb 09, 2018 at 10:16:56PM -0800, Liam Mark wrote: > Fix the dup_sg_table function to initialize the dma_address of the new > sg list entries instead of the source dma_address entries. > > Fixes: 17fd283f3870 ("staging: android: ion: Duplicate sg_table") > Signed-off-by: Liam Mark

Re: [PATCH] staging: android: ion: Initialize dma_address of new sg list

On Fri, Feb 09, 2018 at 10:16:56PM -0800, Liam Mark wrote: > Fix the dup_sg_table function to initialize the dma_address of the new > sg list entries instead of the source dma_address entries. > > Fixes: 17fd283f3870 ("staging: android: ion: Duplicate sg_table") > Signed-off-by: Liam Mark How

Re: [PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

On Sat, Feb 10, 2018 at 09:46:18PM +0530, Dileep Sankhla wrote: > Signed-off-by: Dileep Sankhla The subject is too long and you need to have a changelog. regards, dan carpenter

Re: [PATCH] staging: vt6656: Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning

On Sat, Feb 10, 2018 at 09:46:18PM +0530, Dileep Sankhla wrote: > Signed-off-by: Dileep Sankhla The subject is too long and you need to have a changelog. regards, dan carpenter

Re: [PATCH 3.2 57/79] ALSA: usb-audio: Fix potential zero-division at parsing FU

On Sun, 11 Feb 2018 05:20:06 +0100, Ben Hutchings wrote: > > 3.2.99-rc1 review patch. If anyone has any objections, please let me know. > > -- > > From: Takashi Iwai > > commit 8428a8ebde2db1e988e41a58497a28beb7ce1705 upstream. Please drop this. This patch is

Re: [PATCH 3.2 57/79] ALSA: usb-audio: Fix potential zero-division at parsing FU

On Sun, 11 Feb 2018 05:20:06 +0100, Ben Hutchings wrote: > > 3.2.99-rc1 review patch. If anyone has any objections, please let me know. > > -- > > From: Takashi Iwai > > commit 8428a8ebde2db1e988e41a58497a28beb7ce1705 upstream. Please drop this. This patch is broken, and

Re: [PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

On 02/11/18 22:27, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Create a cache of the nodes that contain a phandle property. Use this > cache to find the node for a given phandle value instead of scanning > the devicetree to find the node. If the phandle value

Re: [PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

On 02/11/18 22:27, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Create a cache of the nodes that contain a phandle property. Use this > cache to find the node for a given phandle value instead of scanning > the devicetree to find the node. If the phandle value is not found > in the

Re: [PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

Hi Rob, On 02/11/18 22:27, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Create a cache of the nodes that contain a phandle property. Use this > cache to find the node for a given phandle value instead of scanning > the devicetree to find the node. If the

Re: [PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

Hi Rob, On 02/11/18 22:27, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Create a cache of the nodes that contain a phandle property. Use this > cache to find the node for a given phandle value instead of scanning > the devicetree to find the node. If the phandle value is not found >

atomic file replacing status?

Whatever happened to this patch? https://patchwork.kernel.org/patch/9636735/ It looks fine and addresses a legitimate issue. Please CC me on replies as I am not subscribed to the LKML. Kind regards, Andrew Kelley

atomic file replacing status?

Whatever happened to this patch? https://patchwork.kernel.org/patch/9636735/ It looks fine and addresses a legitimate issue. Please CC me on replies as I am not subscribed to the LKML. Kind regards, Andrew Kelley

[PATCH v3 2/3] arm64: dts: sdm845: Add minimal dts files for sdm845 SoC/MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 13 ++ arch/arm64/boot/dts/qcom/sdm845.dtsi| 275

[PATCH v3 2/3] arm64: dts: sdm845: Add minimal dts files for sdm845 SoC/MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 13 ++ arch/arm64/boot/dts/qcom/sdm845.dtsi| 275 3 files changed, 289

[PATCH v3 0/3] Add DTS for SDM845 SoC and MTP

These are basic device tree files needed to boot a SDM845 MTP board to a ramfs based serial console shell Bindings are based on whats proposed for pinctrl/serial/clock drivers for SDM845 SoC pinctrl: https://patchwork.kernel.org/patch/10157143/ (This is now pulled in by Linus Walleij for 4.17)

[PATCH v3 0/3] Add DTS for SDM845 SoC and MTP

These are basic device tree files needed to boot a SDM845 MTP board to a ramfs based serial console shell Bindings are based on whats proposed for pinctrl/serial/clock drivers for SDM845 SoC pinctrl: https://patchwork.kernel.org/patch/10157143/ (This is now pulled in by Linus Walleij for 4.17)

[PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

From: Frank Rowand Create a cache of the nodes that contain a phandle property. Use this cache to find the node for a given phandle value instead of scanning the devicetree to find the node. If the phandle value is not found in the cache, of_find_node_by_phandle() will

[PATCH v3 1/3] dt-bindings: arm: Document kryo385 cpu

Document the compatible string for the Kryo385 cpus found in qualcomm SoCs. Signed-off-by: Rajendra Nayak Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/cpus.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 1/3] dt-bindings: arm: Document kryo385 cpu

Document the compatible string for the Kryo385 cpus found in qualcomm SoCs. Signed-off-by: Rajendra Nayak Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/arm/cpus.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/cpus.txt

[PATCH v2] of: cache phandle nodes to reduce cost of of_find_node_by_phandle()

From: Frank Rowand Create a cache of the nodes that contain a phandle property. Use this cache to find the node for a given phandle value instead of scanning the devicetree to find the node. If the phandle value is not found in the cache, of_find_node_by_phandle() will fall back to the tree

[PATCH v3 3/3] arm64: dts: sdm845: Add serial console support

Add the qup uart node and geni se instance needed to support the serial console on the MTP. Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 34 arch/arm64/boot/dts/qcom/sdm845.dtsi| 39

[PATCH v3 3/3] arm64: dts: sdm845: Add serial console support

Add the qup uart node and geni se instance needed to support the serial console on the MTP. Signed-off-by: Rajendra Nayak --- arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 34 arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 + 2 files

Re: [PATCH v2] perf ftrace: Fix the buffer size in __write_tracing_file

On Mon, Feb 12, 2018 at 12:48:15PM +0800, Du, Changbin wrote: > Hi, > > On Mon, Feb 12, 2018 at 10:55:27AM +0900, Namhyung Kim wrote: > > Hello, > > > > On Thu, Feb 08, 2018 at 04:13:20PM +0800, changbin...@intel.com wrote: > > > From: Changbin Du > > > > > > The

Re: [PATCH v2] perf ftrace: Fix the buffer size in __write_tracing_file

On Mon, Feb 12, 2018 at 12:48:15PM +0800, Du, Changbin wrote: > Hi, > > On Mon, Feb 12, 2018 at 10:55:27AM +0900, Namhyung Kim wrote: > > Hello, > > > > On Thu, Feb 08, 2018 at 04:13:20PM +0800, changbin...@intel.com wrote: > > > From: Changbin Du > > > > > > The terminal character '\0' should

[PATCH V2 2/2] mmc: sdhci-msm: support voltage pad switching

From: Krishna Konda The PADs for SD card are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates whether the PAD works in 3v or 1.8v. SDHC core on msm platforms should have IO_PAD_PWR_SWITCH bit set/unset based

[PATCH V2 1/2] mmc: sdhci-msm: Add support to store supported vdd-io voltages

During probe check whether the vdd-io regulator of sdhc platform device can support 1.8V and 3V and store this information as a capability of platform device. Signed-off-by: Vijay Viswanath --- drivers/mmc/host/sdhci-msm.c | 38 ++ 1

[PATCH V2 2/2] mmc: sdhci-msm: support voltage pad switching

From: Krishna Konda The PADs for SD card are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates whether the PAD works in 3v or 1.8v. SDHC core on msm platforms should have IO_PAD_PWR_SWITCH bit set/unset based on actual voltage used

[PATCH V2 1/2] mmc: sdhci-msm: Add support to store supported vdd-io voltages

During probe check whether the vdd-io regulator of sdhc platform device can support 1.8V and 3V and store this information as a capability of platform device. Signed-off-by: Vijay Viswanath --- drivers/mmc/host/sdhci-msm.c | 38 ++ 1 file changed, 38

[PATCH V2 0/2] mmc: sdhci-msm: Configuring IO_PAD support for sdhci-msm

>From the HPG: In some platform, SDCC controller can be connected to either an eMMC device or an SD card. The PADs for SD card are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates whether the PAD works in 3v or 1.8v. For SD usage the

[PATCH V2 0/2] mmc: sdhci-msm: Configuring IO_PAD support for sdhci-msm

>From the HPG: In some platform, SDCC controller can be connected to either an eMMC device or an SD card. The PADs for SD card are dual-voltage that support 3v/1.8v. Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that indicates whether the PAD works in 3v or 1.8v. For SD usage the

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

Hi, On Sun, Feb 11, 2018 at 11:19:10AM -0800, tip-bot for David Woodhouse wrote: > x86/speculation: Use IBRS if available before calling into firmware > > Retpoline means the kernel is safe because it has no indirect branches. > But firmware isn't, so use IBRS for firmware calls if it's

Re: [tip:x86/pti] x86/speculation: Use IBRS if available before calling into firmware

Hi, On Sun, Feb 11, 2018 at 11:19:10AM -0800, tip-bot for David Woodhouse wrote: > x86/speculation: Use IBRS if available before calling into firmware > > Retpoline means the kernel is safe because it has no indirect branches. > But firmware isn't, so use IBRS for firmware calls if it's

Re: [kmemleak] unreferenced object 0xcd9c1a80 (size 192):

On 2/11/18 11:18 AM, Mathieu Malaterre wrote: Hi, On Sun, Feb 11, 2018 at 5:54 PM, Alexei Starovoitov wrote: On Sun, Feb 11, 2018 at 7:24 AM, Mathieu Malaterre wrote: Alexei, Could you please comment on why I am seeing those memleaks being

Re: [kmemleak] unreferenced object 0xcd9c1a80 (size 192):

On 2/11/18 11:18 AM, Mathieu Malaterre wrote: Hi, On Sun, Feb 11, 2018 at 5:54 PM, Alexei Starovoitov wrote: On Sun, Feb 11, 2018 at 7:24 AM, Mathieu Malaterre wrote: Alexei, Could you please comment on why I am seeing those memleaks being reported on my ppc32 system ? Should they be

Re: [PATCH v4 4/5] powerpc/mm/slice: Allow up to 64 low slices

Christophe Leroy writes: > While the implementation of the "slices" address space allows > a significant amount of high slices, it limits the number of > low slices to 16 due to the use of a single u64 low_slices_psize > element in struct mm_context_t > > On the 8xx, the

Re: [PATCH v4 4/5] powerpc/mm/slice: Allow up to 64 low slices

Christophe Leroy writes: > While the implementation of the "slices" address space allows > a significant amount of high slices, it limits the number of > low slices to 16 due to the use of a single u64 low_slices_psize > element in struct mm_context_t > > On the 8xx, the minimum slice size is

Re: [PATCH v4 2/5] powerpc/mm/slice: Enhance for supporting PPC32

Christophe Leroy writes: > In preparation for the following patch which will fix an issue on > the 8xx by re-using the 'slices', this patch enhances the > 'slices' implementation to support 32 bits CPUs. > > On PPC32, the address space is limited to 4Gbytes, hence only

Re: [PATCH v4 2/5] powerpc/mm/slice: Enhance for supporting PPC32

Christophe Leroy writes: > In preparation for the following patch which will fix an issue on > the 8xx by re-using the 'slices', this patch enhances the > 'slices' implementation to support 32 bits CPUs. > > On PPC32, the address space is limited to 4Gbytes, hence only the low > slices will be

Re: tg3 crashes under high load, when using 100Mbits

On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng wrote: > Hi Broadcom folks, > > We are now enabling a new platform with tg3 nic, unfortunately we observed > the bug [1] that dated back to 2015. > I tried commit 4419bb1cedcd ("tg3: Add workaround to restrict 5762 MRRS

Re: tg3 crashes under high load, when using 100Mbits

On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng wrote: > Hi Broadcom folks, > > We are now enabling a new platform with tg3 nic, unfortunately we observed > the bug [1] that dated back to 2015. > I tried commit 4419bb1cedcd ("tg3: Add workaround to restrict 5762 MRRS to > 2048”) but it does’t

[PATCH v2 03/11] watchdog/hpwdt: Update nmi_panic message.

Include the nmistat in the nmi_panic message to give support an indication why the NMI was called (e.g. a timeout or generate nmi button.) Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 27 +++ 1 file changed, 19 insertions(+), 8

[PATCH v2 03/11] watchdog/hpwdt: Update nmi_panic message.

Include the nmistat in the nmi_panic message to give support an indication why the NMI was called (e.g. a timeout or generate nmi button.) Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 27 +++ 1 file changed, 19 insertions(+), 8 deletions(-) diff --git

[PATCH v2 05/11] watchdog/hpwdt: Update Module info.

Update Module Author and permission on parameters so that the parameters show up in sysfs. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/watchdog/hpwdt.c

[PATCH v2 05/11] watchdog/hpwdt: Update Module info.

Update Module Author and permission on parameters so that the parameters show up in sysfs. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index

[PATCH v2 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

Gen8 and prior Proliant systems supported the "CRU" interface to firmware. This interfaces allows linux to "call back" into firmware to source the cause of an NMI. This feature isn't fully utilized as the actual source of the NMI isn't printed, the driver only indicates that the source couldn't

[PATCH v2 01/11] watchdog/hpwdt: Remove legacy NMI sourcing.

Gen8 and prior Proliant systems supported the "CRU" interface to firmware. This interfaces allows linux to "call back" into firmware to source the cause of an NMI. This feature isn't fully utilized as the actual source of the NMI isn't printed, the driver only indicates that the source couldn't

Re: [PATCH 2/4] powerpc/vas: Fix cleanup when VAS is not configured

Sukadev Bhattiprolu writes: > When VAS is not configured in the system, make sure to remove > the VAS debugfs directory and unregister the platform driver. > > Signed-off-by: Sukadev Bhattiprolu ... > diff --git

[PATCH v2 04/11] watchdog/hpwdt: white space changes

Minor white space changes and some name clean up. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 49 +++- 1 file changed, 23 insertions(+), 26 deletions(-) diff --git a/drivers/watchdog/hpwdt.c

[PATCH v2 00/11] watchdog/hpwdt: Update driver to use watchdog core.

== v2 == 1) Fix compiler error when CONFIG_HPWDT_NMI_DECODING is not defined. Small non-white space changes to patches: 0001, 0006, 0008, 0009. 2) Break out driver version change to its own patch. Small non-white space changes to patch 0008 and added 0011. == v1 == The primary purposes of

Re: [PATCH 2/4] powerpc/vas: Fix cleanup when VAS is not configured

Sukadev Bhattiprolu writes: > When VAS is not configured in the system, make sure to remove > the VAS debugfs directory and unregister the platform driver. > > Signed-off-by: Sukadev Bhattiprolu ... > diff --git a/arch/powerpc/platforms/powernv/vas.c > b/arch/powerpc/platforms/powernv/vas.c >

[PATCH v2 04/11] watchdog/hpwdt: white space changes

Minor white space changes and some name clean up. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 49 +++- 1 file changed, 23 insertions(+), 26 deletions(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index

[PATCH v2 00/11] watchdog/hpwdt: Update driver to use watchdog core.

== v2 == 1) Fix compiler error when CONFIG_HPWDT_NMI_DECODING is not defined. Small non-white space changes to patches: 0001, 0006, 0008, 0009. 2) Break out driver version change to its own patch. Small non-white space changes to patch 0008 and added 0011. == v1 == The primary purposes of

[PATCH v2 10/11] watchdog/hpwdt: remove allow_kdump module parameter.

The intent of this parameter is unclear and it sets up a race between the reset of the system by ASR and crashdump. The length of time between receipt of the pretimeout NMI and the ASR reset of the system is fixed by hardware. Turning the parameter off doesn't necessairly prevent a crash dump.

[PATCH v2 10/11] watchdog/hpwdt: remove allow_kdump module parameter.

The intent of this parameter is unclear and it sets up a race between the reset of the system by ASR and crashdump. The length of time between receipt of the pretimeout NMI and the ASR reset of the system is fixed by hardware. Turning the parameter off doesn't necessairly prevent a crash dump.

[PATCH v2 07/11] watchdog/hpwdt: Select WATCHDOG_CORE

Update Kconfig file to show that hpwdt now selects WATCHDOG_CORE. Signed-off-by: Jerry Hoemann --- drivers/watchdog/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig index 6a602f70aaa4..4d219c3fa8b4 100644 ---

[PATCH v2 06/11] watchdog/hpwdt: Modify to use watchdog core.

Follow Documentation/watchdog/convert_drivers_to_kernel_api.txt to convert hpwdt from legacy watchdog driver to use the watchdog core. Removed functions: hpwdt_open, hpwdt_release, hpwdt_write, hpwdt_ioctl Removed data structures: hpwdt_fops, hpwdt_miscdev, watchdog_device Modified functions:

[PATCH v2 07/11] watchdog/hpwdt: Select WATCHDOG_CORE

Update Kconfig file to show that hpwdt now selects WATCHDOG_CORE. Signed-off-by: Jerry Hoemann --- drivers/watchdog/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig index 6a602f70aaa4..4d219c3fa8b4 100644 ---

[PATCH v2 06/11] watchdog/hpwdt: Modify to use watchdog core.

Follow Documentation/watchdog/convert_drivers_to_kernel_api.txt to convert hpwdt from legacy watchdog driver to use the watchdog core. Removed functions: hpwdt_open, hpwdt_release, hpwdt_write, hpwdt_ioctl Removed data structures: hpwdt_fops, hpwdt_miscdev, watchdog_device Modified functions:

[PATCH v2 11/11] watchdog/hpwdt: Update driver version.

Update driver version number to reflect changes. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index bb0dcc8709b8..78168e2f9b4e 100644 ---

[PATCH v2 11/11] watchdog/hpwdt: Update driver version.

Update driver version number to reflect changes. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index bb0dcc8709b8..78168e2f9b4e 100644 ---

[PATCH v2 09/11] watchdog/hpwdt: condition early return of NMI handler on iLO5

Modify prior change to not claim an NMI unless originated from iLO to apply only to iLO5 and later going forward. This restores hpwdt traditional behavior of calling panic if the NMI is NMI_IO_CHECK, NMI_SERR, or NMI_UNKNOWN for legacy hardware. Signed-off-by: Jerry Hoemann

[PATCH v2 09/11] watchdog/hpwdt: condition early return of NMI handler on iLO5

Modify prior change to not claim an NMI unless originated from iLO to apply only to iLO5 and later going forward. This restores hpwdt traditional behavior of calling panic if the NMI is NMI_IO_CHECK, NMI_SERR, or NMI_UNKNOWN for legacy hardware. Signed-off-by: Jerry Hoemann ---

[PATCH v2 08/11] watchdog/hpwdt: Programable Pretimeout NMI

Make whether or not the hpwdt watchdog delivers a pretimeout NMI programable by the user. The underlying iLO hardware is programmable as to whether or not a pre-timeout NMI is delivered to the system before the iLO resets the system. However, the iLO does not allow for programming the length of

[PATCH v2 08/11] watchdog/hpwdt: Programable Pretimeout NMI

Make whether or not the hpwdt watchdog delivers a pretimeout NMI programable by the user. The underlying iLO hardware is programmable as to whether or not a pre-timeout NMI is delivered to the system before the iLO resets the system. However, the iLO does not allow for programming the length of

[PATCH v2 02/11] watchdog/hpwdt: remove include files no longer needed.

remove header files used by NMI sourcing and DMI decoding. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 9 - 1 file changed, 9 deletions(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index 113058644fc3..20a13c5d0285 100644 ---

[PATCH v2 02/11] watchdog/hpwdt: remove include files no longer needed.

remove header files used by NMI sourcing and DMI decoding. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 9 - 1 file changed, 9 deletions(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index 113058644fc3..20a13c5d0285 100644 ---

  1   2   3   4   5   6   7   8   >