From: "Paul E. McKenney" <paulmck@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>,
Josh Triplett <josh@joshtriplett.org>, rcu <rcu@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Problems with rcutorture on ppc64le: allmodconfig(2) and other failures
Date: Tue, 18 Jan 2022 09:29:04 -0800 [thread overview]
Message-ID: <20220118172904.GG947480@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <d744e653-5e8f-b874-6991-3005e6b8afd4@molgen.mpg.de>
On Tue, Jan 18, 2022 at 08:56:24AM +0100, Paul Menzel wrote:
> Dear Zhouyi,
>
>
> Thank you for your quick response.
>
>
> Am 18.01.22 um 08:34 schrieb Zhouyi Zhou:
>
> > I have studied the rcu torture test recently. I am also interested in
> > this topic.
> > But I can't open
> > [1]: https://owww.molgen.mpg.de/~pmenzel/allmodconf-Make.out.txt
> > [2]: https://owww.molgen.mpg.de/~pmenzel/rcutorture-log.txt
>
> Sorry, about that. I should have checked those. I had put them into a
> directory:
>
> [1]: https://owww.molgen.mpg.de/~pmenzel/rcutorture/allmodconf-Make.out.txt
> [2]: https://owww.molgen.mpg.de/~pmenzel/rcutorture/rcutorture-log.txt
>
> I am going to try to test your suggestions at the end of the day.
On x86 rcutorture builds successfully. However, allmodconfig
on semi-recent -next got me "Can't open perl script
"./usr/include/headers_check.pl": No such file or directory".
Which might well be a local problem or might well be fixed by now.
Either way, it looks like I need to upgrade the torture.sh script's
checks for failed builds. Thank you for reporting this!
Thanx, Paul
next prev parent reply other threads:[~2022-01-18 17:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:00 Paul Menzel
2022-01-18 7:34 ` Zhouyi Zhou
2022-01-18 7:56 ` Paul Menzel
2022-01-18 10:56 ` Zhouyi Zhou
2022-01-18 17:29 ` Paul E. McKenney [this message]
2022-01-18 23:46 ` Paul E. McKenney
2022-01-19 2:07 ` Zhouyi Zhou
2022-01-19 4:46 ` Paul E. McKenney
2022-01-19 18:21 ` Paul E. McKenney
2022-01-19 19:30 ` Zhouyi Zhou
2022-01-20 21:06 ` Paul E. McKenney
2022-01-21 0:44 ` Zhouyi Zhou
2022-01-25 16:19 ` Zhouyi Zhou
2022-01-25 18:09 ` Paul E. McKenney
2022-01-26 1:59 ` Zhouyi Zhou
2022-01-26 4:09 ` Zhouyi Zhou
2022-01-26 4:50 ` Paul E. McKenney
2022-01-26 5:14 ` Paul E. McKenney
2022-01-26 5:28 ` Zhouyi Zhou
2022-01-27 0:57 ` Zhouyi Zhou
2022-01-27 1:20 ` Paul E. McKenney
2022-01-27 1:37 ` Zhouyi Zhou
2022-01-18 8:01 ` Paul Menzel
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=20220118172904.GG947480@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=rcu@vger.kernel.org \
--cc=zhouzhouyi@gmail.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
all inboxes | Powered by JetHome®