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 03:10:15 -0400	[thread overview]
Message-ID: <20010525031015.A5828@thyrsus.com> (raw)
In-Reply-To: <20010525023558.B5622@thyrsus.com> <24758.990773964@kao2.melbourne.sgi.com>
In-Reply-To: <24758.990773964@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Fri, May 25, 2001 at 04:59:24PM +1000

Keith Owens <kaos@ocs.com.au>:
> Early ones for compare-and-exchange.  AFAIK no recent (Itanium B3 or
> later) cpu has these problems.

Entry now reads:

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!  Itaniums
  from step B3 or later don't have this problem. If you're unsure,
  select N.
 
> This is software, not hardware, debugging.  It saves addresses to help
> track down spinlock problems.

Entry now reads:

IA64 IRQ bug checking
CONFIG_IA64_DEBUG_IRQ
  Selecting this option turns on bug checking for the IA64 irq_save and
  restore instructions.  It's useful for tracking down spinlock problems,
  but slow!  If you're unsure, select N.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

In recent years it has been suggested that the Second Amendment
protects the "collective" right of states to maintain militias, while
it does not protect the right of "the people" to keep and bear arms.
If anyone entertained this notion in the period during which the
Constitution and the Bill of Rights were debated and ratified, it
remains one of the most closely guarded secrets of the eighteenth
century, for no known writing surviving from the period between 1787
and 1791 states such a thesis.
        -- Stephen P. Halbrook, "That Every Man Be Armed", 1984

  reply	other threads:[~2001-05-25  7:07 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
2001-05-25  6:59     ` Keith Owens
2001-05-25  7:10       ` Eric S. Raymond [this message]
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=20010525031015.A5828@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