[PATCH] pci: Limit VPD length for megaraid_sas adapter

the issue by setting the vpd length to 0. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- drivers/pci/quirks.c| 49 +++ include/linux/pci_ids.h | 12 +++ 2 files changed, 61 insertions(+), 0 deletions(-) diff --git a/driver

[PATCH v2] pci: Limit VPD length for megaraid_sas adapter

s patch fixes the issue by setting the vpd length to 0. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- drivers/pci/quirks.c | 38 ++ 1 files changed, 38 insertions(+), 0 deletions(-) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index b033

Re: [PATCH v2] pci: Limit VPD length for megaraid_sas adapter

On 11/11/2015 1:30 PM, Myron Stowe wrote: > On Wed, Nov 11, 2015 at 8:54 AM, Babu Moger <babu.mo...@oracle.com> wrote: >> Changes since v1 -> v2 >> Removed the changes in pci_id.h. Kept all the vendor >> ids in quirks.c >> >> Reading or Writing of P

[PATCH v4] pci: Limit VPD length for megaraid_sas adapter

patchwork.ozlabs.org/patch/534843/ or https://lkml.org/lkml/2015/10/23/97 Tried to fix it this way, but problem is I dont see the proper start/end TAGs(at least for this adapter) at all. The data is mostly junk or zeros. This patch fixes the issue by setting the vpd length to 0x80. Signed-off-by:

Re: [PATCH v4] pci: Limit VPD length for megaraid_sas adapter

Hi Bjorn, My old logs were lost. So, I had to recreate the issue again. So it took sometime. On 12/7/2015 11:29 AM, Bjorn Helgaas wrote: > Hi Babu, > > On Thu, Dec 03, 2015 at 12:25:19PM -0800, Babu Moger wrote: >> Reading or Writing of PCI VPD data causes system panic. >>

[PATCH] drivers/usb: Skip auto handoff for TI and RENESAS usb controllers

I have never seen auto handoff working on TI and RENESAS cards. Eventually, we force handoff. This code forces the handoff unconditionally. It saves 5 seconds boot time for each card. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- drivers/usb/host/pci-quirks.c |7 +++ 1

Re: [PATCH v4] pci: Limit VPD length for megaraid_sas adapter

Hi Bjorn, Checking again. How about adding some messages in the logs to let user know that vpd has been disabled on this device in case if there is an attempt to access vpd. What do you think?. Thanks Babu On 12/7/2015 5:07 PM, Babu Moger wrote: > Hi Bjorn, > My old logs were lost. So,

[PATCH v3] pci: Limit VPD length for megaraid_sas adapter

patchwork.ozlabs.org/patch/534843/ or https://lkml.org/lkml/2015/10/23/97 Tried to fix it this way, but problem is I dont see the proper start/end TAGs(at least for this adapter) at all. The data is mostly junk or zeros. This patch fixes the issue by setting the vpd length to 0x80. Signed-off-by:

[PATCH] ixgbe: Fix minor typo while freeing irq

The array subscript increments after the execution of the statement. So there is no issue here. However it helps to read the code better. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |2 +- 1 files changed, 1 insertions(+), 1 del

Re: [PATCHv2 4/4] pci: Blacklist vpd access for buggy devices

4. https://patchwork.kernel.org/patch/8084221/ I will wait for Hannes's response before re-posting it. Hannes, If you want me to re-post all the series let me know. > > On Wed, Jan 13, 2016 at 12:25:35PM +0100, Hannes Reinecke wrote: >> From: Babu Moger <babu.mo...@oracle.com&g

Re: [PATCH RFC] pci: Blacklist vpd access for buggy devices

On 1/21/2016 9:47 AM, jordan_hargr...@dell.com wrote: >> From: Babu Moger [babu.mo...@oracle.com] >> Sent: Tuesday, January 19, 2016 2:39 PM >> To: Hargrave, Jordan; bhelg...@google.com >> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; >> alexander

[PATCH v4 4/4] pci: Blacklist vpd access for buggy devices

this patch implements a PCI quirk to disabling VPD acces altogether by setting the vpd length to '0'. Added all the PCI_VENDOR_ID_ATTANSIC varients. Signed-off-by: Babu Moger <babu.mo...@oracle.com> Signed-off-by: Hannes Reinecke <h...@suse.de> Signed-off-by: Jordan Hargrave <jordan_hargr.

[PATCH RFC] PCI: Fix for panic while enabling SR-IOV

ata from PF to VF. Also verified the fix. Please review. Let me know if there is a better way to fix this. Signed-off-by: Babu Moger <babu.mo...@oracle.com> Signed-off-by: Sowmini Varadhan <sowmini.varad...@oracle.com> --- arch/sparc/kernel/pci.c |7 +++ drivers/pci/iov.c |

Re: [PATCH v2] drivers/usb: Skip auto handoff for TI and RENESAS usb controllers

Its been a while since I submit this patch. Ping 1. On 1/8/2016 9:39 AM, Babu Moger wrote: > I have never seen auto handoff working on TI and RENESAS cards. > Eventually, we force handoff. This code forces the handoff > unconditionally. It saves 5 seconds boot time for each card. &g

[PATCH v2] sparc/PCI: Fix for panic while enabling SR-IOV

happens via of_create_pci_dev for sparc), some of the arch specific initialization does not happen for VF device. That causes panic when archdata is accessed. To fix this, I have used already defined weak function pcibios_setup_device to copy archdata from PF to VF. Also verified the fix. Signed-o

[PATCH v3] sparc/PCI: Fix for panic while enabling SR-IOV

happens via of_create_pci_dev for sparc), some of the arch specific initialization does not happen for VF device. That causes panic when archdata is accessed. To fix this, I have used already defined weak function pcibios_setup_device to copy archdata from PF to VF. Also verified the fix. Signed-o

[PATCH v4] sparc/PCI: Fix for panic while enabling SR-IOV

happens via of_create_pci_dev for sparc), some of the arch specific initialization does not happen for VF device. That causes panic when archdata is accessed. To fix this, I have used already defined weak function pcibios_setup_device to copy archdata from PF to VF. Also verified the fix. Signed-o

Re: [PATCH v4] sparc/PCI: Fix for panic while enabling SR-IOV

Hi David, On 3/29/2016 7:57 PM, David Miller wrote: > From: Babu Moger <babu.mo...@oracle.com> > Date: Thu, 24 Mar 2016 13:02:22 -0700 > >> We noticed this panic while enabling SR-IOV in sparc. > ... >> SR-IOV code looks for arch specific data while enabling &

[PATCH] ixgbevf: Fix relaxed order settings in VF driver

with VF interface. Fixed it by reading the registers first and setting the specific bit of interest. With this change we are able to match the bandwidth equivalent to PF interface. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c

Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver

Hi Alex, On 4/21/2016 2:22 PM, Alexander Duyck wrote: > On Thu, Apr 21, 2016 at 11:13 AM, Alexander Duyck > <alexander.du...@gmail.com> wrote: >> On Thu, Apr 21, 2016 at 10:21 AM, Babu Moger <babu.mo...@oracle.com> wrote: >>> Current code writes the tx/rx relax

[PATCH v2] ixgbevf: Change the relaxed order settings in VF driver for sparc

We noticed performance issues with VF interface on sparc compared to PF. Setting the RX to IXGBE_DCA_RXCTRL_DATA_WRO_EN brings it on far with PF. Also this matches to the default sparc setting in PF driver. Signed-off-by: Babu Moger <babu.mo...@oracle.com> Acked-by: Sowmini Va

Filesystem slow write performance

s with latest upstream kernel. Looked at the upstream patches and tried most of the upstream patches which appear to be related and nothing helped. Problem is fairly easy to reproduce. Let me know if you want me to try something. Thanks Babu Moger

Re: Filesystem slow write performance

I wasn't able to repro this with mainline. Sorry for the noise. On 8/6/2016 1:49 PM, Babu Moger wrote: Hi, Seeing some terrible write performance with ext3/4 writes. Reads are fine. I have a created loop device and mounted as ext3(tried ext4 also). Here is iostat output. await time

Re: [PATCH v3 2/2] lockdep: Limit static allocations if PROVE_LOCKING_SMALL is defined

CCing Dave. Dave, Please ack it if it looks good. Thanks. On 9/27/2016 2:33 PM, Babu Moger wrote: Reduce the size of data structure for lockdep entries by half if PROVE_LOCKING_SMALL if defined. This is used only for sparc. Signed-off-by: Babu Moger <babu.mo...@oracle.com> ---

Re: [PATCH v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

On 9/28/2016 3:39 AM, Peter Zijlstra wrote: On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote: This new config parameter limits the space used for "Lock debugging: prove locking correctness" by about 4MB. The current sparc systems have the limitation of 32MB size for k

Re: [PATCH v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

Dave, Gentle reminder to review this patch. Thanks On 9/30/2016 12:19 AM, David Miller wrote: From: Babu Moger <babu.mo...@oracle.com> Date: Thu, 29 Sep 2016 08:53:24 -0500 On 9/28/2016 3:39 AM, Peter Zijlstra wrote: On Tue, Sep 27, 2016 at 12:33:27PM -0700, Babu Moger wrote: Th

Re: [PATCH 1/2] watchdog: Introduce update_arch_nmi_watchdog

On 10/6/2016 11:34 PM, Sam Ravnborg wrote: On Thu, Oct 06, 2016 at 03:16:42PM -0700, Babu Moger wrote: Currently we do not have a way to enable/disable arch specific watchdog handlers if it was implemented by any of the architectures. This patch introduces new function

[PATCH 0/2] Introduce update_arch_nmi_watchdog for arch specific handlers

in arch specific handlers. If you think there is a better way to do this. Please advice. Tested on sparc. Compile tested on x86. Babu Moger (2): watchdog: Introduce update_arch_nmi_watchdog sparc: Implement update_arch_nmi_watchdog arch/sparc/kernel/nmi.c | 26

[PATCH 1/2] watchdog: Introduce update_arch_nmi_watchdog

watchdog_enabled variable outside so that arch specific nmi watchdogs can use it to implement enalbe/disable behavour. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- include/linux/nmi.h |1 + kernel/watchdog.c | 16 +--- 2 files changed, 14 insertions(+), 3 deletions(-) diff

[PATCH 2/2] sparc: Implement update_arch_nmi_watchdog

interface. Example commands. To enable: echo 1 > /proc/sys/kernel/nmi_watchdog To disable: echo 0 > /proc/sys/kernel/nmi_watchdog It can also achieved using the sysctl parameter kernel.nmi_watchdog Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/kernel/

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 2:12 AM, Peter Zijlstra wrote: On Thu, Sep 22, 2016 at 11:43:34AM -0700, Babu Moger wrote: These patches adjust the static allocations for lockdep data structures used for debugging locking correctness. The current code reserves about 4MB extra space for these data structures. Most

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 9:34 AM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 09:04:42AM -0500, Babu Moger wrote: On 9/23/2016 2:12 AM, Peter Zijlstra wrote: On Thu, Sep 22, 2016 at 11:43:34AM -0700, Babu Moger wrote: These patches adjust the static allocations for lockdep data structures used

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 10:04 AM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 09:50:52AM -0500, Babu Moger wrote: Why can't you boot? You have that little memories? 4MB doesn't seem like a worthwhile amount of memory. Also, you didn't say. This seems a somewhat crucial point. Correct, We can't

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 10:40 AM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 10:15:46AM -0500, Babu Moger wrote: Correct, We can't boot with lockdep. Sorry I did not make that clear. We have a limit on static size of the kernel. This stuff should be in .bss not .data. It should not affect

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 3:17 PM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 02:57:39PM -0500, Babu Moger wrote: We checked again. Yes, It goes in .bss section. But in sparc we have to fit .text, .data, .bss in 7 permanent TLBs(that is totally 28MB). It was fine so far. But the commit

[PATCH 0/2] Ajust lockdep static allocations

tic allocations"). Added new CONFIG_PROVE_LOCKING_PLUS in case someone needs more entries to debug their large configuration. Patch 1 : Adjusts the sizes based on the new config parameter patch 2 : Adds new config parameter Babu Moger (2): lockdep: Keep the default static allocations sma

[PATCH 1/2] lockdep: Keep the default static allocations small

needs to enable more static space for lockdep entries, lock chains and stack traces to debug large configurations. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/locking/lockdep_internals.h | 14 +++--- 1 files changed, 11 insertions(+), 3 deletions(-) d

[PATCH 2/2] config: Add new CONFIG_PROVE_LOCKING_PLUS

Adding the new config parameter CONFIG_PROVE_LOCKING_PLUS in case someone needs to enable more static space for lockdep entries, lock chains and stack traces to debug large configurations. The default size is kept small to cover majority of the configs. Signed-off-by: Babu Moger <babu

Re: [PATCH v2 1/2] config: Add new CONFIG_PROVE_LOCKING_SMALL

On 9/27/2016 10:43 AM, Sam Ravnborg wrote: On Tue, Sep 27, 2016 at 09:51:40AM -0500, Babu Moger wrote: On 9/27/2016 6:40 AM, Peter Zijlstra wrote: On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote: Since this is only relevant for sparc, and for sparc this is "sele

Re: [PATCH v2 1/2] config: Add new CONFIG_PROVE_LOCKING_SMALL

On 9/27/2016 6:40 AM, Peter Zijlstra wrote: On Tue, Sep 27, 2016 at 06:46:25AM +0200, Sam Ravnborg wrote: Since this is only relevant for sparc, and for sparc this is "select"ed, then there is limited/no gain having this as a visible menu config option. How about adding just a simple

[PATCH v3 0/2] Ajust lockdep static allocations for sparc

Peter Zijlstra, keeping the default as is. Introduced new config variable CONFIG_PROVE_LOCKING_SMALL to handle sparc specific case. v0: Initial revision. Babu Moger (2): config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc lockdep: Limit static alloc

[PATCH v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

row beyond this limit and causing system boot-up issues. With this option, kernel limits the size of the entries of lock_chains, stack_trace etc., so that kernel fits in required size limit. This is not visible to user and only used for sparc. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- ar

[PATCH v3 2/2] lockdep: Limit static allocations if PROVE_LOCKING_SMALL is defined

Reduce the size of data structure for lockdep entries by half if PROVE_LOCKING_SMALL if defined. This is used only for sparc. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/locking/lockdep_internals.h | 20 +--- 1 files changed, 17 insertions(+), 3 del

[PATCH v2 2/2] lockdep: Keep the static allocations small for PROVE_LOCKING_SMALL

Reduce the size of data structure for lockdep entries half if PROVE_LOCKING_SMALL if defined. This is used for sparc. This config variable is disabled by default. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/locking/lockdep_internals.h | 13 ++--- 1 files chang

[PATCH v2 0/2] Ajust lockdep static allocations for sparc

v2: As suggested by Peter Zijlstra, keeping the default as is. Introduced new config variable CONFIG_PROVE_LOCKING_SMALL to handle sparc specific case. v0: Initial revision. Babu Moger (2): config: Add new CONFIG_PROVE_LOCKING_SMALL lockdep: Keep the static allocations sm

[PATCH v2 1/2] config: Add new CONFIG_PROVE_LOCKING_SMALL

s sections. With PROVE_LOCKING feature, the kernel size could grow beyond this limit and causing system bootup issues. With this option, kernel limits the size of the entries of lock_chains, stack_trace etc. so that kernel fits in required size limit. This is only visible for sparc. Signed-off-by: Babu Moge

[RFC PATCH 2/4] watchdog: Move shared definitions to nmi.h

Move shared macros and definitions to nmi.h so that watchdog.c, watchdog_hld.c or any other architecture specific handler can use those definitions. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- include/linux/nmi.h | 19 +++ kernel/watchdog.c

[RFC PATCH 1/4] watchdog: Remove hardlockup handler references

Separate hardlockup code from watchdog.c. It is mostly straight forward. Remove everything inside CONFIG_HARDLOCKUP_DETECTORS. This code will go to file watchdog_hld.c. We also define weak handlers watchdog_nmi_enable and watchdog_nmi_disable. Signed-off-by: Babu Moger <babu.mo...@oracle.

[RFC PATCH 3/4] watchdog: Move hardlockup detector to separate file

Move hardlockup detector code to watchdog_hld.c. Also update the makefile accordigly. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/Makefile |1 + kernel/watchdog_hld.c | 238 + 2 files changed, 239 insertions

[RFC PATCH 4/4] sparc: Implement watchdog_nmi_enable and watchdog_nmi_disable

proc or sysctl interface. Example commands. To enable: echo 1 > /proc/sys/kernel/nmi_watchdog To disable: echo 0 > /proc/sys/kernel/nmi_watchdog It can also achieved using the sysctl parameter kernel.nmi_watchdog Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/

[RFC PATCH 0/4] Clean up watchdog handlers

such that architectures can override its definitions. Thanks to Don Zickus for his suggestions. Here is the previous discussion http://www.spinics.net/lists/sparclinux/msg16441.html Babu Moger (4): watchdog: Remove hardlockup handler references watchdog: Move shared definitions to nmi.h watchdog: Move

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

Don, On 10/17/2016 12:31 PM, Don Zickus wrote: On Thu, Oct 13, 2016 at 01:38:01PM -0700, Babu Moger wrote: Currently we do not have a way to enable/disable arch specific watchdog handlers if it was implemented by any of the architectures. This patch introduces new functions

[PATCH v3 2/2] sparc: Implement arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

watchdogs using proc or sysctl interface. Example commands. To enable: echo 1 > /proc/sys/kernel/nmi_watchdog To disable: echo 0 > /proc/sys/kernel/nmi_watchdog It can also achieved using the sysctl parameter kernel.nmi_watchdog Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/

[PATCH v3 0/2] Introduce arch specific nmi enable, disable handlers

: Initial version. Discussion thread here http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1245427.html Babu Moger (2): watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable sparc: Implement arch_watchdog_nmi_enable and arch_watchdog_nmi_disable arch/sparc

[PATCH v3 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

handlers. These functions are defined as weak as architectures can override their definitions to enable/disable nmi watchdog behaviour. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/watchdog.c | 69 +++- 1 files changed, 46 inse

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

On 10/24/2016 10:19 AM, Don Zickus wrote: On Fri, Oct 21, 2016 at 04:50:21PM -0500, Babu Moger wrote: Don, On 10/21/2016 2:19 PM, Andrew Morton wrote: On Fri, 21 Oct 2016 11:11:14 -0400 Don Zickus <dzic...@redhat.com> wrote: On Thu, Oct 20, 2016 at 08:25:27PM -0700, Andrew Morton

Re: [PATCH v2 RESEND] drivers/usb: Skip auto handoff for TI and RENESAS usb controllers

On 10/25/2016 1:51 AM, Mathias Nyman wrote: On 24.10.2016 17:52, Babu Moger wrote: On 10/24/2016 5:54 AM, Yoshihiro Shimoda wrote: Hi, From: Mathias Nyman Sent: Monday, October 24, 2016 6:58 PM On 22.10.2016 01:25, Babu Moger wrote: Never seen XHCI auto handoff working on TI and RENESAS

[PATCH v2 RESEND] drivers/usb: Skip auto handoff for TI and RENESAS usb controllers

Never seen XHCI auto handoff working on TI and RENESAS cards. Eventually, we force handoff. This code forces the handoff unconditionally. It saves 5 seconds boot time for each card. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- v2: Made changes per comments from Greg KH. Extra

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

Don, On 10/21/2016 2:19 PM, Andrew Morton wrote: On Fri, 21 Oct 2016 11:11:14 -0400 Don Zickus wrote: On Thu, Oct 20, 2016 at 08:25:27PM -0700, Andrew Morton wrote: On Thu, 20 Oct 2016 12:14:14 -0400 Don Zickus wrote: -static int

Re: [PATCH v2 RESEND] drivers/usb: Skip auto handoff for TI and RENESAS usb controllers

On 10/24/2016 5:54 AM, Yoshihiro Shimoda wrote: Hi, From: Mathias Nyman Sent: Monday, October 24, 2016 6:58 PM On 22.10.2016 01:25, Babu Moger wrote: Never seen XHCI auto handoff working on TI and RENESAS cards. Eventually, we force handoff. This code forces the handoff unconditionally

Re: [RFC PATCH 0/4] Clean up watchdog handlers

On 10/31/2016 4:00 PM, Don Zickus wrote: On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements both softlockup and hardlockup detectors. Softlockup code is generic. Hardlockup code is arch specific

Re: [RFC PATCH 0/4] Clean up watchdog handlers

On 10/31/2016 4:00 PM, Don Zickus wrote: On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements both softlockup and hardlockup detectors. Softlockup code is generic. Hardlockup code is arch specific

Re: [RFC PATCH 0/4] Clean up watchdog handlers

On 11/1/2016 8:20 AM, Don Zickus wrote: On Mon, Oct 31, 2016 at 04:30:59PM -0500, Babu Moger wrote: On 10/31/2016 4:00 PM, Don Zickus wrote: On Wed, Oct 26, 2016 at 09:02:19AM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements

Re: [PATCH v2 0/3] Clean up watchdog handlers

On 11/4/2016 11:25 AM, Don Zickus wrote: On Tue, Nov 01, 2016 at 02:13:43PM -0700, Babu Moger wrote: This is an attempt to cleanup watchdog handlers. Right now, kernel/watchdog.c implements both softlockup and hardlockup detectors. Softlockup code is generic. Hardlockup code is arch specific

[PATCH v2 0/3] Clean up watchdog handlers

. is_hardlockup kind of generic most part. kernel/built-in.o: In function `watchdog_overflow_callback': watchdog_hld.c:(.text+0x56940): undefined reference to `sysctl_hardlockup_all_cpu_backtrace' Moved this definition to nmi.h. v1: Initial version Babu Moger (3): watchdog: Move shared

[PATCH v2 1/3] watchdog: Move shared definitions to nmi.h

Move shared macros and definitions to nmi.h so that watchdog.c, new file watchdog_hld.c or any other architecture specific handler can use those definitions. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- include/linux/nmi.h | 24 kernel/watchdog.c

[PATCH v2 3/3] sparc: Implement watchdog_nmi_enable and watchdog_nmi_disable

proc or sysctl interface. Example commands. To enable: echo 1 > /proc/sys/kernel/nmi_watchdog To disable: echo 0 > /proc/sys/kernel/nmi_watchdog It can also achieved using the sysctl parameter kernel.nmi_watchdog Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/

[PATCH RESEND v3 1/2] config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc

row beyond this limit and causing system boot-up issues. With this option, kernel limits the size of the entries of lock_chains, stack_trace etc., so that kernel fits in required size limit. This is not visible to user and only used for sparc. Signed-off-by: Babu Moger <babu.mo...@oracle.com> Acked-by:

[PATCH RESEND v3 2/2] lockdep: Limit static allocations if PROVE_LOCKING_SMALL is defined

Reduce the size of data structure for lockdep entries by half if PROVE_LOCKING_SMALL if defined. This is used only for sparc. Signed-off-by: Babu Moger <babu.mo...@oracle.com> Acked-by: Sam Ravnborg <s...@ravnborg.org> --- kernel/locking/lockdep_internals.h | 20 +

[PATCH RESEND v3 0/2] Adjust lockdep static allocations for sparc

ed new config variable CONFIG_PROVE_LOCKING_SMALL to handle sparc specific case. v0: Initial revision. Babu Moger (2): config: Adding the new config parameter CONFIG_PROVE_LOCKING_SMALL for sparc lockdep: Limit static allocations if PROVE_LOCKING_SMALL is defined arch/sparc/K

[PATCH v2 2/3] watchdog: Move hardlockup detector to separate file

Separate hardlockup code from watchdog.c and move it to watchdog_hld.c. It is mostly straight forward. Remove everything inside CONFIG_HARDLOCKUP_DETECTORS. This code will go to file watchdog_hld.c. Also update the makefile accordigly. Signed-off-by: Babu Moger <babu.mo...@oracle.com> ---

[PATCH v2 2/2] sparc: Implement arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

watchdogs using proc or sysctl interface. Example commands. To enable: echo 1 > /proc/sys/kernel/nmi_watchdog To disable: echo 0 > /proc/sys/kernel/nmi_watchdog It can also achieved using the sysctl parameter kernel.nmi_watchdog Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/

[PATCH v2 0/2] Introduce arch specific nmi enable, disable handlers

to introduce new variable nmi_init_done to synchronize watchdog thread and kernel init thread. v1: Initial version. Discussion thread here http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1245427.html Babu Moger (2): watchdog: Introduce arch_watchdog_nmi_enable

Re: [PATCH 0/2] Introduce update_arch_nmi_watchdog for arch specific handlers

On 10/7/2016 10:51 AM, Don Zickus wrote: On Thu, Oct 06, 2016 at 03:16:41PM -0700, Babu Moger wrote: During our testing we noticed that nmi watchdogs in sparc could not be disabled or enabled dynamically using sysctl/proc interface. Sparc uses its own arch specific nmi watchdogs

[PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

handlers. These functions are defined as weak as architectures can override their definitions to enable/disable nmi watchdog behaviour. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- kernel/watchdog.c | 65 +++- 1 files changed, 44 inse

[PATCH v2] arch/sparc: Avoid DCTI Couples

, since not all implementations make that distinction, for optimal performance, a DCTI should not be placed in the instruction word immediately following an annulled branch-always instruction (BA,A or BPA,A)." Signed-off-by: Babu Moger <babu.mo...@oracle.com> Reviewed-by: Rob Gardn

[PATCH] arch/sparc: Avoid DCTI Couples

sumes it will." Signed-off-by: Babu Moger <babu.mo...@oracle.com> Reviewed-by: Rob Gardner <rob.gard...@oracle.com> --- arch/sparc/kernel/head_64.S|4 arch/sparc/kernel/misctrap.S |1 + arch/sparc/kernel/rtrap_64.S |1 + arch/sparc/kernel/spiterrs.

Re: [PATCH RFC 3/4] arch/sparc: Optimized memcpy, memset, copy_to_user, copy_from_user for M7

David, Thanks for the comments. I am working on addressing your feedback. Comments inline below. On 7/29/2017 4:36 PM, David Miller wrote: From: Babu Moger <babu.mo...@oracle.com> Date: Thu, 27 Jul 2017 15:57:29 -0600 @@ -600,7 +600,7 @@ niagara_tlb_fixup: be,pt

Re: [PATCH v2 0/4] Update memcpy, memset etc. for M7/M8 architectures

David, Thanks for applying. On 8/10/2017 4:38 PM, David Miller wrote: From: Babu Moger <babu.mo...@oracle.com> Date: Mon, 7 Aug 2017 17:52:48 -0600 This series of patches updates the memcpy, memset, copy_to_user, copy_from_user etc for SPARC M7/M8 architecture. This doesn't buil

Re: [GIT PULL] USB/PHY patches for 4.13-rc1

On 7/4/2017 4:09 AM, Geert Uytterhoeven wrote: Hi Greg, On Tue, Jul 4, 2017 at 10:04 AM, Greg KH wrote: On Tue, Jul 04, 2017 at 09:15:55AM +0200, Geert Uytterhoeven wrote: On Mon, Jul 3, 2017 at 4:58 PM, Greg KH wrote: USB/PHY

Re: [GIT PULL] USB/PHY patches for 4.13-rc1

On 7/6/2017 3:24 AM, Max Filippov wrote: Hi Babu, On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger <babu.mo...@oracle.com> wrote: Max, Do you have any concerns about xtensa? no, not ATM. I still haven't got a chance to look closer at moving endianness macros back to Kconfig for xtensa.

Re: [GIT PULL] USB/PHY patches for 4.13-rc1

On 7/6/2017 9:33 AM, Greg KH wrote: On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote: On 7/6/2017 3:24 AM, Max Filippov wrote: Hi Babu, On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger <babu.mo...@oracle.com> wrote: Max, Do you have any concerns about xtensa? no, not ATM. I

Re: [GIT PULL] USB/PHY patches for 4.13-rc1

On 7/6/2017 10:51 AM, Greg KH wrote: On Thu, Jul 06, 2017 at 10:28:03AM -0500, Babu Moger wrote: On 7/6/2017 9:33 AM, Greg KH wrote: On Thu, Jul 06, 2017 at 09:28:06AM -0500, Babu Moger wrote: On 7/6/2017 3:24 AM, Max Filippov wrote: Hi Babu, On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger

[PATCH v3 1/3] arch: Define CPU_BIG_ENDIAN for all fixed big endian archs

/earlycon.c drivers/tty/serial/serial_core.c Be aware that this may cause regressions if someone has worked-around problems in the above code already. Remove the work-around. Here is our original discussion https://lkml.org/lkml/2017/5/24/620 Signed-off-by: Babu Moger <babu.mo...@oracle.com> Sug

[PATCH v3 3/3] include: warn for inconsistent endian config definition

is not defined on big endian architecture and also warn if it defined on little endian architectures. Here is our original discussion https://lkml.org/lkml/2017/5/24/620 Signed-off-by: Babu Moger <babu.mo...@oracle.com> Suggested-by: Arnd Bergmann <a...@arndb.de> Acked-by: Geert Uytterhoeven

[PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for inconsistencies

ded the choice statement for endianness selection for microblaze. Updated the Makefile for microblaze(Suggested by Arnd Bergmann) to properly compile for the correct format. Updated acks. v1 -> v2: Updated the commit messages and acks. Babu Moger (3): arch: Define CPU_BIG_ENDIAN for all fixed big

[PATCH v3 2/3] arch/microblaze: Add choice for endianness and update Makefile

microblaze architectures can be configured for either little or big endian formats. Add a choice option for the user to select the correct endian format(default to big endian). Also update the Makefile so toolchain can compile for the format it is configured for. Signed-off-by: Babu Moger

[PATCH v2 1/4] arch/sparc: Separate the exception handlers from NG4memcpy

Separate the exception handlers from NG4memcpy so that it can be used with new memcpy routines. Make a separate file for all these handlers. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/Makefile |2 + arch/sparc/lib/Memcpy_utils.S

[PATCH v2 0/4] Update memcpy, memset etc. for M7/M8 architectures

/patch/792662/ However, I did not see these patches in sparc-next tree. It may be in queue now. It is possible these patches might cause some build problems. It will resolve once all M8 patches are in sparc-next tree. v0: Initial version Babu Moger (4): arch/sparc: Separate

[PATCH v2 2/4] arch/sparc: Rename exception handlers

Rename exception handlers to memcpy_xxx as these are going to be used by new memcpy routines and these handlers are not exclusive to NG4memcpy anymore. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/Memcpy_utils.S | 120 +++--- arch

[PATCH v2 3/4] arch/sparc: Optimized memcpy, memset, copy_to_user, copy_from_user for M7/M8

New algorithm that takes advantage of the M7/M8 block init store ASI, ie, overlapping pipelines and miss buffer filling. Full details in code comments. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/kernel/head_64.S | 16 +- arch/sparc/lib/M7copy_from_user.S

[PATCH v2 4/4] arch/sparc: Add accurate exception reporting in M7memcpy

Add accurate exception reporting in M7memcpy Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/M7copy_from_user.S | 11 +- arch/sparc/lib/M7copy_to_user.S | 10 +- arch/sparc/lib/M7memcpy.S | 396 ++-- arch/spa

[PATCH RFC 2/4] arch/sparc: Rename exception handlers

Rename exception handlers to memcpy_xxx as these are going to be used by new memcpy routines and these handlers are not exclusive to NG4memcpy anymore. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/Memcpy_utils.S | 120 +++--- arch

[PATCH RFC 3/4] arch/sparc: Optimized memcpy, memset, copy_to_user, copy_from_user for M7

New algorithm that takes advantage of the M7 block init store ASI, ie, overlapping pipelines and miss buffer filling. Full details in code comments. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/kernel/head_64.S | 12 +- arch/sparc/lib/M7copy_from_user.S

[PATCH RFC 4/4] arch/sparc: Add accurate exception reporting in M7memcpy

Add accurate exception reporting in M7memcpy Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/M7copy_from_user.S | 11 +- arch/sparc/lib/M7copy_to_user.S | 10 +- arch/sparc/lib/M7memcpy.S | 396 ++-- arch/spa

[PATCH RFC 1/4] arch/sparc: Separate the exception handlers from NG4memcpy

Separate the exception handlers from NG4memcpy so that it can be used with new memcpy routines. Make a separate file for all these handlers. Signed-off-by: Babu Moger <babu.mo...@oracle.com> --- arch/sparc/lib/Makefile |2 + arch/sparc/lib/Memcpy_utils.S

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On 6/12/2017 3:51 PM, Arnd Bergmann wrote: On Mon, Jun 12, 2017 at 10:30 PM, Babu Moger <babu.mo...@oracle.com> wrote: Looks like microblaze can be configured to either little or big endian formats. How about adding a choice statement to address this. Here is my proposed patch. H

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

On 6/12/2017 3:58 PM, Max Filippov wrote: On Mon, Jun 12, 2017 at 1:51 PM, Arnd Bergmann wrote: That way, we don't have to guess what the toolchain does, but rather tell it to do whatever is configured, like we do for most other architectures. Unfortunately we can't do the

Re: [PATCH 2/2] include: warn for inconsistent endian config definition

-ci/linux/commits/Babu-Moger/Define-CPU_BIG_ENDIAN-or-warn-for-inconsistencies/20170610-200424 config: microblaze-mmu_defconfig (attached as .config) compiler: microblaze-linux-gcc (GCC) 6.2.0 reproduce: wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin

[PATCH v3 1/3] arch: Define CPU_BIG_ENDIAN for all fixed big endian archs

/earlycon.c drivers/tty/serial/serial_core.c Be aware that this may cause regressions if someone has worked-around problems in the above code already. Remove the work-around. Here is our original discussion https://lkml.org/lkml/2017/5/24/620 Signed-off-by: Babu Moger <babu.mo...@oracle.com> Sug

  1   2   3   4   5   6   >