From: Jarek Poplawski <jarkao2@o2.pl>
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, 8 Nov 2006 10:32:01 +0100 [thread overview]
Message-ID: <20061108093201.GA2489@ff.dom.local> (raw)
In-Reply-To: <454CA335.609@steudten.com>
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 ?
Jarek P.
next prev parent reply other threads:[~2006-11-08 9:32 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 [this message]
2006-11-08 11:08 ` alpha @ steudten Engineering
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=20061108093201.GA2489@ff.dom.local \
--to=jarkao2@o2.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).