From: "alpha @ steudten Engineering" <NWQ3MzhlY2QwZDAzODVhN@steudten.com>
To: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: Re: INFO alpha CPU: Locking API testsuite: Results kernel 2.6.18.1
Date: Wed, 08 Nov 2006 12:08:46 +0100 [thread overview]
Message-ID: <4551BABE.1060307@steudten.com> (raw)
In-Reply-To: <20061108093201.GA2489@ff.dom.local>
CONFIG_PROVE_LOCKING=y ?
It't not there/set! It depends on:
config PROVE_LOCKING
bool "Lock debugging: prove locking correctness"
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
select LOCKDEP
so it looks like only DEBUG_KERNEL is set for alpha.
Maybe some dependencies are missing.. I'll check this.
Jarek Poplawski wrote:
> On 04-11-2006 15:27, alpha @ steudten Engineering wrote:
>> kernel-2.6.18.1 ALPHA SX164
>> No "failed" on x86.
>> ------------------------
>> | Locking API testsuite:
>> ----------------------------------------------------------------------------
>> | spin |wlock |rlock |mutex | wsem | rsem |
>> --------------------------------------------------------------------------
>> A-A deadlock:failed|failed| ok |failed|failed|failed|
> ...
>> --------------------------------------------------------
>> 143 out of 218 testcases failed, as expected. |
>> ----------------------------------------------------
>
> CONFIG_PROVE_LOCKING=y ?
prev parent reply other threads:[~2006-11-08 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 14:27 INFO alpha CPU: Locking API testsuite: Results kernel 2.6.18.1 alpha @ steudten Engineering
2006-11-08 9:32 ` Jarek Poplawski
2006-11-08 11:08 ` alpha @ steudten Engineering [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=4551BABE.1060307@steudten.com \
--to=nwq3mzhly2qwzdazodvhn@steudten.com \
--cc=linux-alpha@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.