From: Robin Holt <holt@sgi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Robin Holt <holt@sgi.com>, Ingo Molnar <mingo@redhat.com>,
Russ Anderson <rja@sgi.com>, Shawn Guo <shawn.guo@linaro.org>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michel Lespinasse <walken@google.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
Tejun Heo <tj@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Patch -v4 4/4] Make reboot_cpuid a kernel parameter. other cpus.
Date: Wed, 17 Apr 2013 04:55:01 -0500 [thread overview]
Message-ID: <20130417095501.GD3658@sgi.com> (raw)
In-Reply-To: <20130416124411.GP3658@sgi.com>
On Tue, Apr 16, 2013 at 07:44:12AM -0500, Robin Holt wrote:
> On Tue, Apr 16, 2013 at 05:05:45AM -0700, H. Peter Anvin wrote:
> > Why not just support the existing syntax everywhere?
>
> I have not given it much consideration, but IIRC, the other arches that
> were using reboot= were only looking for an 'h' or something like that.
>
> I will consider making the syntax parse reboot=s#### when I get to
> the office.
Yesterday was rather disruptive and I did not get to this. I have given
it some thought this morning.
Generally speaking, I don't like the feel of this for two reasons. First,
having two different places that are parsing reboot=<reboot_mode> and
its related difficulty in documenting it. Second, we lose the /sys/ file.
Some background. First, arm. It already has a reboot=<c>. That <c>
gets passed to the reboot sub-arch function. It looks like it is ignored,
but I am very uncertain of that as it is passed into an assembly routine.
Second unicore. It parses as reboot=<c>. That <c> gets ignored.
Now the meat of my question. The Documentation/kernel-parameters.txt
file indicates reboot= is handled by the arch and are of the format
<reboot-mode>[,<reboot-mode>[,...]].
I suppose we could have both an arch and generic kernel handler for
__setup("reboot=",...) where the generic kernel one just handles the
s###, but that seems really different from how everything else is done.
I could not find one instance where a both an arch and the kernel proper
both parsed the same command-line parameter.
I did not spend the time to see if having two __setup() declarations
would work.
Additionally, the __setup("... mechanism loses the nice feature the
core_param gives us in that there is a /sys/ file now available which
allows us to easily change that setting on the running system.
Are you really sure you want me to do more than I already have. This
really feels _VERY_ wrong to me. Maybe I misunderstood your direction.
Thanks,
Robin
prev parent reply other threads:[~2013-04-17 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 9:56 [Patch -v4 0/4] Shutdown from reboot_cpuid without stopping other cpus Robin Holt
2013-04-16 9:59 ` [Patch -v4 2/4] Move shutdown/reboot related functions to kernel/reboot.c " Robin Holt
2013-04-16 10:01 ` [Patch -v4 3/4] checkpatch.pl the new kernel/reboot.c file Robin Holt
2013-04-16 10:04 ` [Patch -v4 4/4] Make reboot_cpuid a kernel parameter. other cpus Robin Holt
2013-04-16 12:05 ` H. Peter Anvin
2013-04-16 12:44 ` Robin Holt
2013-04-17 9:55 ` Robin Holt [this message]
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=20130417095501.GD3658@sgi.com \
--to=holt@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rja@sgi.com \
--cc=rusty@rustcorp.com.au \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.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