From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Frans Pop" <elendil@planet.nl>
Cc: "Yinghai Lu" <yhlu.kernel.send@gmail.com>,
mingo@elte.hu, akpm@linux-foundation.org, tglx@linutronix.de,
hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: simplify the memtest parameter setting
Date: Fri, 18 Apr 2008 20:17:37 -0700 [thread overview]
Message-ID: <86802c440804182017r4fe78371w3a4a714a44591223@mail.gmail.com> (raw)
In-Reply-To: <200804190415.47552.elendil@planet.nl>
On Fri, Apr 18, 2008 at 7:15 PM, Frans Pop <elendil@planet.nl> wrote:
> On Saturday 19 April 2008, Frans Pop wrote:
> > Yinghai Lu wrote:
> > > -config MEMTEST_BOOTPARAM
> > > - bool "Memtest boot parameter"
> > > +config MEMTEST
> > > + bool "Memtest"
> > > depends on X86_64
> > > default y
> >
> > With this patch, this default no longer makes any sense.
> >
> > > help
> > > This option adds a kernel parameter 'memtest', which allows memtest
> > > - to be disabled at boot. If this option is selected, memtest
> > > - functionality can be disabled with memtest=0 on the kernel
> > > - command line. The purpose of this option is to allow a single
> > > - kernel image to be distributed with memtest built in, but not
> > > - necessarily enabled.
> > > -
> > > + to be set.
> > > + memtest=0, mean disabled; -- default
> > > + memtest=1, mean do 1 test pattern;
> > > + ...
> > > + memtest=4, mean do 4 test patterns.
> >
> > s/mean/means/
> > s/; -- default/ (default)/
>
> These are still good (IMO).
>
>
> > Maybe some explanation of what a "test pattern" is would be useful.
> >
> > > If you are unsure how to answer this question, answer Y.
> >
> > Also makes no sense anymore.
>
> Oops. Just see I was too fast. After reading it again I see that the y/n
> value is correct after all.
>
> However, it also means that the new description is probably too short.
> The phrase "allows memtest to be set" does not really mean anything to a
> user who does not know what memtest really does. It also does not explain
> that memtest is a boot parameter.
>
> Also, it should probably be made more explicit that no memtest is actually
> performed unless the memtest boot parameter is passed at the boot prompt.
>
> Looks like 4 is the maximum possible value. This should be mentioned
> explicitly (here as well as in Documentation/kernel-parameters.txt).
current it only support 4 pattern, will try to move memtester pattern
into it later...
YH
next prev parent reply other threads:[~2008-04-19 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 0:49 [PATCH] x86_64: simplify the memtest parameter setting Yinghai Lu
2008-04-19 1:57 ` Frans Pop
2008-04-19 2:15 ` Frans Pop
2008-04-19 3:17 ` Yinghai Lu [this message]
2008-04-19 8:20 ` Stefan Richter
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=86802c440804182017r4fe78371w3a4a714a44591223@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel.send@gmail.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