Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-29 Thread Jeffrey Merkey
On 1/29/16, Ingo Molnar wrote: > > * Jeffrey Merkey wrote: > >> On 1/28/16, Thomas Gleixner wrote: >> > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >> >> On 1/28/16, Thomas Gleixner wrote: >> >> > I'm probably missing something obvious here. >> >> >> >> It's a pain in the butt to grep around thr

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-29 Thread Jeffrey Merkey
On 1/29/16, Jeffrey Merkey wrote: > On 1/29/16, Ingo Molnar wrote: >> >> * Jeffrey Merkey wrote: >> >>> On 1/28/16, Thomas Gleixner wrote: >>> > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >>> >> On 1/28/16, Thomas Gleixner wrote: >>> >> > I'm probably missing something obvious here. >>> >> >>>

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-29 Thread Jeffrey Merkey
On 1/29/16, Ingo Molnar wrote: > > * Jeffrey Merkey wrote: > >> On 1/28/16, Thomas Gleixner wrote: >> > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >> >> On 1/28/16, Thomas Gleixner wrote: >> >> > I'm probably missing something obvious here. >> >> >> >> It's a pain in the butt to grep around thr

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-29 Thread Jeffrey Merkey
On 1/29/16, Ingo Molnar wrote: > > * Jeffrey Merkey wrote: > >> On 1/28/16, Thomas Gleixner wrote: >> > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >> >> On 1/28/16, Thomas Gleixner wrote: >> >> > I'm probably missing something obvious here. >> >> >> >> It's a pain in the butt to grep around thr

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-29 Thread Ingo Molnar
* Jeffrey Merkey wrote: > On 1/28/16, Thomas Gleixner wrote: > > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: > >> On 1/28/16, Thomas Gleixner wrote: > >> > I'm probably missing something obvious here. > >> > >> It's a pain in the butt to grep around through assembly language in a > >> function

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Jeffrey Merkey
> > You obviously completely ignored this part of my reply: > >> > If we follow your argumentation we need another gazillion of >> > conditional >> > breakpoints in the kernel Actually, I was not suggesting this at all. But now that you mention it, there is already a BUG() macro that inserts a a

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Chris Metcalf
On 01/28/2016 02:46 PM, Jeffrey Merkey wrote: This patch series adds an export which can be set by system debuggers to direct the hard lockup and soft lockup detector to trigger a breakpoint exception and enter a debugger if one is active. It is assumed that if someone sets this variable, then a

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Thomas Gleixner
On Thu, 28 Jan 2016, Jeffrey Merkey wrote: > On 1/28/16, Thomas Gleixner wrote: > If you don't get it Thomas, I don't know what else to say. Right now > the only debugger that provides disassembly on a single running live > Linux system is the one I use unless you want to use a serial > connectio

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Jeffrey Merkey
On 1/28/16, Thomas Gleixner wrote: > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >> On 1/28/16, Thomas Gleixner wrote: >> > I'm probably missing something obvious here. >> >> It's a pain in the butt to grep around through assembly language in a >> function in watchdog.c that has everything declare

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Thomas Gleixner
On Thu, 28 Jan 2016, Jeffrey Merkey wrote: > On 1/28/16, Thomas Gleixner wrote: > > I'm probably missing something obvious here. > > It's a pain in the butt to grep around through assembly language in a > function in watchdog.c that has everything declared static with no > symbols. It's a lot ea

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Jeffrey Merkey
On 1/28/16, Chris Metcalf wrote: > On 01/28/2016 02:46 PM, Jeffrey Merkey wrote: >> This patch series adds an export which can be set by system debuggers to >> direct the hard lockup and soft lockup detector to trigger a breakpoint >> exception and enter a debugger if one is active. It is assumed

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread kbuild test robot
Hi Jeffrey, [auto build test ERROR on v4.5-rc1] [also build test ERROR on next-20160128] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-hard-s

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Jeffrey Merkey
On 1/28/16, Thomas Gleixner wrote: > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: > >> This patch series adds an export which can be set by system debuggers to >> direct the hard lockup and soft lockup detector to trigger a breakpoint >> exception and enter a debugger if one is active. It is assume

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Thomas Gleixner
On Thu, 28 Jan 2016, Jeffrey Merkey wrote: > This patch series adds an export which can be set by system debuggers to > direct the hard lockup and soft lockup detector to trigger a breakpoint > exception and enter a debugger if one is active. It is assumed that if > someone sets this variable, th

[PATCH 01/31] Add hard/soft lockup debugger entry points

2016-01-28 Thread Jeffrey Merkey
This patch series adds an export which can be set by system debuggers to direct the hard lockup and soft lockup detector to trigger a breakpoint exception and enter a debugger if one is active. It is assumed that if someone sets this variable, then an breakpoint handler of some sort will be active