All of
 help / color / mirror / Atom feed
From: John Ogness <>
To: Michael Cree <>
Cc: Richard Henderson <>,
	Ivan Kokshaysky <>,
	Matt Turner <>,
Subject: Re: Alpha hardware for printk tests?
Date: Tue, 19 May 2020 15:42:15 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (John Ogness's message of "Wed, 13 May 2020 14:17:51 +0200")

On 2020-05-12, John Ogness <> wrote:
> I have posted[0] a new lockless printk ringbuffer implementation. The
> ringbuffer has been tested heavily on x86_64 and arm64 SMP
> systems. However, I would also like to test it on an SMP Alpha
> system. Since the main purpose of the test is to verify the memory
> barriers, the tests need to run on real hardware.
> The new ringbuffer (with test routine) can also be built as a kernel
> module and does not require any kernel patching. It should work on any
> Linux kernel 4.20 or higher.
> Is there anyone with access to SMP Alpha hardware that would be
> willing to run the tests for me? Or can someone tell me where I might
> find such a candidate? Thanks!

A problem leading to data corruption in the ringbuffer messages has been
identified and fixed. A new version of the test module is available:

The README in the tarball explains how to build/run the test and what
information to send back after the test.

This test module should build/run without any kernel patching or
rebooting. Even if it is only allowed to run on your SMP-Alpha for an
hour, that would be very helpful for me.

John Ogness

  reply	other threads:[~2020-05-19 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 14:39 Alpha hardware for printk tests? John Ogness
2020-05-13  9:25 ` Michael Cree
2020-05-13 12:17   ` John Ogness
2020-05-19 13:42     ` John Ogness [this message]
2020-05-19 20:28       ` Michael Cree
2020-05-25  9:47       ` Michael Cree

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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.