From: Guillaume Morin <guillaume@morinfr.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Guillaume Morin <guillaume@morinfr.org>,
gregkh@linuxfoundation.org, stable@vger.kernel.org,
neelx@redhat.com
Subject: Re: [PATCH for stable 5.x] rcu: Tighten rcu_advance_cbs_nowake() checks
Date: Mon, 24 Jan 2022 19:12:55 +0100 [thread overview]
Message-ID: <Ye7sJ+7szTW0mKYd@bender.morinfr.org> (raw)
In-Reply-To: <20220120233331.GS947480@paulmck-ThinkPad-P17-Gen-1>
On 20 Jan 15:33, Paul E. McKenney wrote:
> > ---- TREE01 8: Kernel present. Thu 20 Jan 2022 05:03:55 PM EST
> > ---- TREE04 8: Kernel present. Thu 20 Jan 2022 05:03:55 PM EST
> > ---- Starting kernels. Thu 20 Jan 2022 05:03:55 PM EST
> > ---- All kernel runs complete. Thu 20 Jan 2022 05:14:05 PM EST
> > ---- TREE01 8: Build/run results:
> > --- Thu 20 Jan 2022 05:02:37 PM EST: Starting build
> > --- Thu 20 Jan 2022 05:03:55 PM EST: Starting kernel
> > CPU-hotplug kernel, adding rcutorture onoff.
> > Monitoring qemu job at pid 46081
> > Grace period for qemu job at pid 46081
> > ---- TREE04 8: Build/run results:
> > --- Thu 20 Jan 2022 05:03:16 PM EST: Starting build
> > :CONFIG_HOTPLUG_CPU: improperly set
> > --- Thu 20 Jan 2022 05:03:55 PM EST: Starting kernel
> > CPU-hotplug kernel, adding rcutorture onoff.
> > Monitoring qemu job at pid 45847
> > Grace period for qemu job at pid 45847
> >
> >
> > --- Thu 20 Jan 2022 05:02:37 PM EST Test summary:
> > Results directory: /usr/scratch/kernel/tools/testing/selftests/rcutorture/res/2022.01.20-17:02:37
> > tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 60 --duration 10 --configs TREE01 TREE04
> > TREE01 ------- 12719 GPs (21.1983/s) [rcu: g94609 f0x0 ]
> > TREE04 ------- 3128 GPs (5.21333/s) [rcu: g23621 f0x0 ]
> > :CONFIG_HOTPLUG_CPU: improperly set
>
> This run was successful, so good!
Greg, so could you please queue up
614ddad17f22a22e035e2ea37a04815f50362017 for 5.4+ stable branches?
Thank you
Guillaume.
--
Guillaume Morin <guillaume@morinfr.org>
next prev parent reply other threads:[~2022-01-24 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:55 [PATCH for stable 5.x] rcu: Tighten rcu_advance_cbs_nowake() checks Guillaume Morin
2022-01-20 19:16 ` Paul E. McKenney
2022-01-20 19:26 ` Guillaume Morin
2022-01-20 20:57 ` Paul E. McKenney
2022-01-20 22:21 ` Guillaume Morin
2022-01-20 23:33 ` Paul E. McKenney
2022-01-24 18:12 ` Guillaume Morin [this message]
2022-01-24 18:16 ` Greg KH
2022-01-27 15:31 ` Greg KH
2022-01-22 18:40 ` Daniel Vacek
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=Ye7sJ+7szTW0mKYd@bender.morinfr.org \
--to=guillaume@morinfr.org \
--cc=gregkh@linuxfoundation.org \
--cc=neelx@redhat.com \
--cc=paulmck@kernel.org \
--cc=stable@vger.kernel.org \
/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).