[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87k28tklmx.fsf@concordia.ellerman.id.au>
Date: Tue, 14 Feb 2017 23:22:14 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org
Cc: benh@...nel.crashing.org, paulus@...ba.org,
aneesh.kumar@...ux.vnet.ibm.com,
Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com>
Subject: Re: [PATCH] powerpc/xmon: add turn off xmon option
Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com> writes:
> Once xmon is triggered, there is no interface to turn it off again.
> However there exists disable/enable xmon code flows. And more important,
> System reset interrupt on powerVM will fire an oops to make a dump. At
> that time, xmon should not be triggered.
>
> So add 'z' option after current 'x|X' exit commands. Turn xmon off if 'z'
> is following.
Thanks for trying to clear this up.
But I like the solution we discussed in the other thread better. ie.
entering/leaving xmon via sysrq will always leave the state unchanged,
and we'll add a debugfs to change the state.
cheers
Powered by blists - more mailing lists