From: Thomas Gleixner <tglx@linutronix.de>
To: Alex Thorlton <athorlton@sgi.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Hedi Berriche <hedi@sgi.com>,
x86@kernel.org
Subject: Re: [PATCH 1/2] Disable UV BAU by default
Date: Wed, 23 Mar 2016 12:27:44 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1603231223440.3978@nanos> (raw)
In-Reply-To: <1458579852-37580-2-git-send-email-athorlton@sgi.com>
On Mon, 21 Mar 2016, Alex Thorlton wrote:
First of all, please use proper patch prefixes.
x86/platform/uv: ....
And please fold the documentation change into the patch which changes the
parameter.
> static int timeout_us;
> -static int nobau;
> +static int nobau = 1;
> static int nobau_perm;
> static cycles_t congested_cycles;
>
> @@ -106,13 +106,22 @@ static char *stat_description[] = {
> "enable: number times use of the BAU was re-enabled"
> };
>
> -static int __init
> -setup_nobau(char *arg)
> +static int __init setup_bau(char *arg)
> {
> - nobau = 1;
> + if (!arg)
> + return -EINVAL;
> +
> + if (!strncmp(arg, "on", 2)) {
> + nobau = 0;
> + pr_info("UV BAU Enabled\n");
> + } else if (!strncmp(arg, "off", 3)) {
> + nobau = 1;
> + pr_info("UV BAU Disabled\n");
> + }
> +
> return 0;
> }
> -early_param("nobau", setup_nobau);
> +early_param("bau", setup_bau);
What's the value of having that extra argument?
The default is off, so we can do with a simple "bau" or "enable_bau" and be
done with it.
Thanks,
tglx
next prev parent reply other threads:[~2016-03-23 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 17:04 [PATCH 0/2] Re-work UV BAU enable/disable logic, add documentation Alex Thorlton
2016-03-21 17:04 ` [PATCH 1/2] Disable UV BAU by default Alex Thorlton
2016-03-23 11:27 ` Thomas Gleixner [this message]
2016-03-23 16:11 ` Alex Thorlton
2016-03-23 17:20 ` Thomas Gleixner
2016-03-23 17:25 ` Alex Thorlton
2016-03-21 17:04 ` [PATCH 2/2] Add documentation for the bau parameter Alex Thorlton
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=alpine.DEB.2.11.1603231223440.3978@nanos \
--to=tglx@linutronix.de \
--cc=athorlton@sgi.com \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.org \
/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®