public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: Configure.help entries wanted
Date: Fri, 25 May 2001 02:35:58 -0400	[thread overview]
Message-ID: <20010525023558.B5622@thyrsus.com> (raw)
In-Reply-To: <20010525012200.A5259@thyrsus.com> <23530.990770596@kao2.melbourne.sgi.com>
In-Reply-To: <23530.990770596@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Fri, May 25, 2001 at 04:03:16PM +1000

Keith Owens <kaos@ocs.com.au>:
> I claim my erudition prize (do I get steak knives with that?).

Results doubtful.  Consult Magic 8-Ball again :-).

I'm going to critique these individually pour encourager les autres.

> +Disable IA-64 Virtual Hash Page Table
> +CONFIG_DISABLE_VHPT
> +  The Virtual Hash Page Table (VHPT) enhances virtual address
> +  translation performance.  Normally you want the VHPT active but you
> +  can select this option to disable the VHPT for debugging.  If you're
> +  unsure, answer N.

Excellent!  Second sentence a good example of motivation.

> +McKinley A-step specific code
> +CONFIG_MCKINLEY_ASTEP_SPECIFIC
> +  Select this option to build a kernel for an IA64 McKinley system
> +  with any A-stepping CPU.
> +
> +McKinley A0/A1-step specific code
> +CONFIG_MCKINLEY_A0_SPECIFIC
> +  Select this option to build a kernel for an IA64 McKinley system
> +  with an A0 or A1 stepping CPU.

Ah, now I could have written these.  What I was hoping for was extra
information analogous to what's in these:

Enable Itanium B-step specific code
CONFIG_ITANIUM_BSTEP_SPECIFIC
  Select this option to build a kernel for an Itanium prototype system
  with a B-step CPU.  You have a B-step CPU if the "revision" field in
  /proc/cpuinfo has a value in the range from 1 to 4.

Enable Itanium B0-step specific code
CONFIG_ITANIUM_B0_SPECIFIC
  Select this option to build a kernel for an Itanium prototype system
  with a B0-step CPU.  You have a B0-step CPU if the "revision" field in
  /proc/cpuinfo is 1.

Is there a value range in /proc/cpuinfo that tells you you have an A/A0 step?

> +IA64 compare-and-exchange bug checking
> +CONFIG_IA64_DEBUG_CMPXCHG
> +  Selecting this option turns on bug checking for the IA64
> +  compare-and-exchange instructions.  This is slow!  If you're unsure,
> +  select N.
> +
> +IA64 IRQ bug checking
> +CONFIG_IA64_DEBUG_IRQ
> +  Selecting this option turns on bug checking for the IA64 irq_save and
> +  restore instructions.  This is slow!  If you're unsure, select N.

These would be much improved by some indication of what IA64 variants or mask
steppings have these problems.

> +IA64 Early printk support
> +CONFIG_IA64_EARLY_PRINTK
> +  Selecting this option uses the VGA screen for printk() output before
> +  the consoles are initialised.  It is useful for debugging problems
> +  early in the boot process, but only if you have a VGA screen
> +  attached.  If you're unsure, select N.

Good!

> +IA64 Print Hazards
> +CONFIG_IA64_PRINT_HAZARDS
> +  Selecting this option prints more information for Illegal Dependency
> +  Faults, that is, for Read after Write, Write after Write or Write
> +  after Read violations.  This option is ignored if you are compiling
> +  for an Itanium A step processor (CONFIG_ITANIUM_ASTEP_SPECIFIC).  If
> +  you're unsure, select Y.

Excellent!

This is a fine start.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

"If I must write the truth, I am disposed to avoid every assembly 
of bishops; for of no synod have I seen a profitable end, but
rather an addition to than a diminution of evils; for the love 
of strife and the thirst for superiority are beyond the power 
of words to express."
	-- Father Gregory Nazianzen, 381 AD

  reply	other threads:[~2001-05-25  6:33 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25  5:22 Configure.help entries wanted Eric S. Raymond
2001-05-25  6:03 ` Keith Owens
2001-05-25  6:35   ` Eric S. Raymond [this message]
2001-05-25  6:59     ` Keith Owens
2001-05-25  7:10       ` Eric S. Raymond
2001-05-25  7:36 ` Philip Blundell
2001-05-25  8:04   ` [kbuild-devel] " Eric S. Raymond
2001-05-25 10:30     ` Russell King
2001-05-26  4:34 ` [kbuild-devel] " Greg Banks
2001-05-26  6:06   ` Jaswinder Singh
2001-05-26 10:06     ` Greg Banks
2001-05-26 18:50       ` Jaswinder Singh
2001-05-27  1:12         ` Greg Banks
2001-05-27  1:08           ` Jaswinder Singh
2001-05-27  1:29             ` Greg Banks
2001-05-27  1:28               ` Jaswinder Singh
2001-05-27  2:03                 ` Greg Banks
2001-05-27  2:08                   ` Jaswinder Singh
2001-05-27  1:20           ` Alan Cox
2001-05-27  1:31             ` Jaswinder Singh
2001-05-27  2:10               ` Greg Banks
2001-05-27  2:13                 ` Jaswinder Singh
2001-05-27  2:52                   ` Greg Banks
2001-05-27 16:27                     ` Pavel Machek
2001-05-28  0:56                       ` Greg Banks
2001-05-28  1:05                         ` Alan Cox
2001-05-28  2:36                           ` Greg Banks
2001-05-28  2:34                             ` Jaswinder Singh
2001-05-28  2:58                         ` Jaswinder Singh
2001-05-28  3:17                           ` Greg Banks
2001-05-27  2:00             ` Greg Banks
2001-05-27  3:06             ` Greg Banks
2001-05-27  3:10               ` Jaswinder Singh
2001-05-27 15:24                 ` Greg Banks
2001-05-27  5:03         ` Bill Pringlemeir
2001-05-26 21:48       ` esr
2001-05-27  1:54         ` Jaswinder Singh
2001-05-27  2:43         ` Greg Banks

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=20010525023558.B5622@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.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