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 17:12:49 +0100	[thread overview]
Message-ID: <20230110161249.GB4649@1wt.eu> (raw)
In-Reply-To: <20230110145334.GL4028633@paulmck-ThinkPad-P17-Gen-1>

On Tue, Jan 10, 2023 at 06:53:34AM -0800, Paul E. McKenney wrote:
> Here is one of them, based on both the fixes and Sven's s390 support.
> Please let me know if you need any other combination.

Thanks, here's the problem:

> 0 getpid = 1                             [OK]
> 1 getppid = 0                            [OK]
> 3 gettid = 1                             [OK]
> 5 getpgid_self = 0                       [OK]
> 6 getpgid_bad = -1 ESRCH                 [OK]
> 7 kill_0[    1.940442] tsc: Refined TSC clocksource calibration: 2399.981 MHz
> [    1.942334] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x229825a5278, max_idle_ns: 440795306804 ns
>  = 0                             [OK]
> 8 kill_CONT = 0           [    1.944987] clocksource: Switched to clocksource tsc
>                [OK]
> 9 kill_BADPID = -1 ESRCH                 [OK]
(...)

It's clear that "grep -c ^[0-9].*OK" will not count all of them (2 are
indeed missing).

We could probably start with "quiet" but that would be against the
principle of using this to troubleshoot issues. I think we just stick
to the current search of "FAIL" and that as long as a success is
reported and the number of successes is within the expected range
that could be OK. At least I guess :-/

Thanks,
Willy

  reply	other threads:[~2023-01-10 16:13 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
2023-01-10 14:53       ` Paul E. McKenney
2023-01-10 16:12         ` Willy Tarreau [this message]
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=20230110161249.GB4649@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