From: Michael Ellerman <mpe@ellerman.id.au>
To: Pan Xinhui <xinhui@linux.vnet.ibm.com>,
"Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>,
Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: benh@kernel.crashing.org, paulus@samba.org, npiggin@gmail.com
Subject: Re: [PATCH] powerpc/xmon: Fix an unexpected xmon onoff state change
Date: Fri, 17 Feb 2017 17:05:48 +1100 [thread overview]
Message-ID: <87h93tjqrn.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <8466dffc-d75c-d83a-2a4f-d567721db7d5@linux.vnet.ibm.com>
Pan Xinhui <xinhui@linux.vnet.ibm.com> writes:
> diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
> index 9c0e17c..f6e5c3d 100644
> --- a/arch/powerpc/xmon/xmon.c
> +++ b/arch/powerpc/xmon/xmon.c
> @@ -76,6 +76,7 @@ static int xmon_gate;
> #endif /* CONFIG_SMP */
>
> static unsigned long in_xmon __read_mostly = 0;
> +static int xmon_off = !IS_ENABLED(CONFIG_XMON_DEFAULT);
I think the logic would probably clearer if we invert this to become
xmon_on.
> @@ -3266,16 +3269,16 @@ static int __init setup_xmon_sysrq(void)
> __initcall(setup_xmon_sysrq);
> #endif /* CONFIG_MAGIC_SYSRQ */
>
> -static int __initdata xmon_early, xmon_off;
> +static int __initdata xmon_early;
>
> static int __init early_parse_xmon(char *p)
> {
> if (!p || strncmp(p, "early", 5) == 0) {
> /* just "xmon" is equivalent to "xmon=early" */
> - xmon_init(1);
> xmon_early = 1;
> + xmon_off = 0;
> } else if (strncmp(p, "on", 2) == 0)
> - xmon_init(1);
> + xmon_off = 0;
You've just changed the timing of when xmon gets enabled for the above
two cases, from here which is called very early, to xmon_setup() which
is called much later in boot.
That effectively disables xmon for most of the boot, which we do not
want to do.
cheers
next prev parent reply other threads:[~2017-02-17 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 7:49 Pan Xinhui
2017-02-15 21:22 ` Guilherme G. Piccoli
2017-02-16 5:09 ` Michael Ellerman
2017-02-16 10:57 ` Guilherme G. Piccoli
2017-02-16 11:51 ` Pan Xinhui
2017-02-17 6:05 ` Michael Ellerman [this message]
2017-02-17 9:30 ` Pan Xinhui
2017-02-17 12:25 ` Guilherme G. Piccoli
2017-02-20 4:46 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h93tjqrn.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=xinhui.pan@linux.vnet.ibm.com \
--cc=xinhui@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®