[PATCH 2/3] powerpc/xmon: Disable and enable tracing command

[Breno Leitao]

On Wed, Aug 02, 2017 at 06:51:24PM +0530, Naveen N. Rao wrote:
> On 2017/08/01 11:21AM, Breno Leitao wrote:
> > Hi Naveen,
> > 
> > On Tue, Aug 01, 2017 at 12:10:24PM +0530, Naveen N. Rao wrote:
> > > On 2017/07/31 02:22PM, Breno Leitao wrote:
> > > > If tracing is enabled and you get into xmon, the tracing buffer
> > > > continues to be updated, causing possible loss of data due to buffer
> > > > overflow and unnecessary tracing information coming from xmon functions.
> > > > 
> > > > This patch adds a new option that allows the tracing to be disabled and
> > > > re-enabled from inside xmon.
> > > 
> > > How is this new option useful? In the next patch, you disable tracing by 
> > > default -- in what scenario do you expect to have to re-enable tracing 
> > > from within xmon?
> > 
> > I see it being useful on two different scenarios:
> > 
> > 1) You can reenable tracing if you want to call a function from xmon
> > (with 'p'), or even for code stepping (with 's').
> 
> Hmm... those are just debugging aids, so I don't see why enabling the 
> function tracer helps, unless you're debugging the tracer itself..
> 
> > 
> > 2) You may also want to reenable tracing once you resume from xmon with
> > 'zr'.
> 
> 'zr' is for reboot, so not sure what you meant there...

I meant 'x' in fact, which means 'exit monitor and recover'. This will
resume the kernel after getting into xmon.

> If tracing was enabled before we went into xmon, I think that we should 
> just restore it by default.

Makes sense. So, I will get ride of this 'v' feature and disable tracing
when entering the xmon, and reenabling it on recovering. That way, we
will avoid xmon functions showing up on the tracing buffer.

I will send a new patchset soon!

Thanks,
Breno