public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Frans Pop <elendil@planet.nl>,
	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: Sat, 19 Apr 2008 10:20:39 +0200	[thread overview]
Message-ID: <4809AB57.6050103@s5r6.in-berlin.de> (raw)
In-Reply-To: <86802c440804182017r4fe78371w3a4a714a44591223@mail.gmail.com>

> On Fri, Apr 18, 2008 at 7:15 PM, Frans Pop <elendil@planet.nl> wrote:
>>  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).

To add to this:  The help text should IMO contain
   - that a test for faulty RAM is being added if Y,
   - that this feature can be controlled by the boot parameter
     (and, per the parameter's default, is normally off),
   - how many loops with which data patterns are performed depending
     on the boot parameter value,
   - how long this might take (so that nobody who hears of this for
     the first time enables it e.g. on a server which is supposed to
     not take too long to reboot),
   - how reliable the results of this test are (I presume that some
     faults can only be found by many repeated re-runs of the memory
     tester),
   - that saying Y slightly (?) increases the size of the kernel image
     but does not influence the kernel size after boot-up is completed.

Thanks,
-- 
Stefan Richter
-=====-==--- -=-- =--==
http://arcgraph.de/sr/

      reply	other threads:[~2008-04-19  8:21 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
2008-04-19  8:20       ` Stefan Richter [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=4809AB57.6050103@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --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 \
    --cc=yhlu.kernel@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