linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: John Ogness <john.ogness@linutronix.de>
Cc: Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Matt Turner <mattst88@gmail.com>,
	linux-alpha@vger.kernel.org
Subject: Re: Alpha hardware for printk tests?
Date: Wed, 13 May 2020 21:25:26 +1200	[thread overview]
Message-ID: <20200513092526.GD2743@tower> (raw)
In-Reply-To: <87tv0lgqut.fsf@vostro.fn.ogness.net>

On Tue, May 12, 2020 at 04:39:06PM +0200, 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!

I run the two Alpha ES45's building for Debian-Ports.  I can run
the tests on one of them if you provide me with instructions.

Cheers,
Michael.

  reply	other threads:[~2020-05-13  9:25 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 [this message]
2020-05-13 12:17   ` John Ogness
2020-05-19 13:42     ` John Ogness
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:
  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=20200513092526.GD2743@tower \
    --to=mcree@orcon.net.nz \
    --cc=ink@jurassic.park.msu.ru \
    --cc=john.ogness@linutronix.de \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=rth@twiddle.net \
    /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).