public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH 0/4] nolibc: add support for the s390 platform
Date: Tue, 10 Jan 2023 10:25:17 +0100	[thread overview]
Message-ID: <20230110092517.GA4626@1wt.eu> (raw)
In-Reply-To: <20230110073242.GB3229@1wt.eu>

On Tue, Jan 10, 2023 at 08:32:42AM +0100, Willy Tarreau wrote:
> On Mon, Jan 09, 2023 at 11:15:34AM -0800, Paul E. McKenney wrote:
> > On Mon, Jan 09, 2023 at 09:09:06AM +0100, Willy Tarreau wrote:
> > > Hello Paul,
> > > 
> > > this series adds support for the s390x platform to nolibc and rcutorture,
> > > reducing the init size from ~600kB to ~1kB. The work was contributed by
> > > Sven Schnelle. It depends on the fixes series I sent previously:
> > > 
> > >   https://lore.kernel.org/lkml/20230109075442.25963-1-w@1wt.eu/
> > > 
> > > It passes the self-tests correctly and the patches are clean, please
> > > consider queuing it.
> > 
> > "80 test(s) passed" and successful exit code.  I will assume that the
> > decrease in tests from 81 to 80 is intended.  I have these queued,
> > but it may be some hours before they are externally visible.
> 
> Interesting, I didn't notice and I'm not observing this when running
> qemu-s390x (the userland version), I'm currently rebuilding the kernel
> to compare and will let you know. Thanks for checking!

So after a re-check, I'm constantly seeing 82 tests passed and a success
here. I don't understand what's differing, and would be interested in a
copy of your "run.out" in the "tools/testing/selftests/nolibc" subdir to
compare with mine, as it's possible we have a bug somewhere in the way
tests are run (or maybe we're still facing a mangled qemu output).

You can just send this to me privately, no need to spam the list, the
file is moderately large and uninteresting.

Thanks!
Willy

  reply	other threads:[~2023-01-10  9:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  8:09 [PATCH 0/4] nolibc: add support for the s390 platform Willy Tarreau
2023-01-09  8:09 ` [PATCH 1/4] nolibc: add support for s390 Willy Tarreau
2023-01-09  8:09 ` [PATCH 2/4] selftests/nolibc: add s390 support Willy Tarreau
2023-01-09  8:09 ` [PATCH 3/4] rcutorture: add support for s390 Willy Tarreau
2023-01-09  8:09 ` [PATCH 4/4] rcutorture: build initrd for rcutorture with nolibc Willy Tarreau
2023-01-09 19:15 ` [PATCH 0/4] nolibc: add support for the s390 platform Paul E. McKenney
2023-01-09 22:04   ` Paul E. McKenney
2023-01-10  7:32   ` Willy Tarreau
2023-01-10  9:25     ` Willy Tarreau [this message]
2023-01-10 14:53       ` Paul E. McKenney
2023-01-10 16:12         ` Willy Tarreau
2023-01-10 16:32           ` Paul E. McKenney
2023-01-10 17:53             ` Willy Tarreau
2023-01-10 21:29               ` Paul E. McKenney
2023-01-11  6:45             ` Sven Schnelle
2023-01-11  6:51               ` Willy Tarreau

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=20230110092517.GA4626@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=svens@linux.ibm.com \
    /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