[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1512557468-52633-1-git-send-email-lianglihao@huawei.com>
Date: Wed, 6 Dec 2017 18:51:06 +0800
From: <lianglihao@...wei.com>
To: <paulmck@...ux.vnet.ibm.com>
CC: <guohanjun@...wei.com>, <lihao.liang@...il.com>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] rcutorture: Add parameter usage warnings
From: Lihao Liang <lianglihao@...wei.com>
Hi Paul,
Please find a patch series that adds rcutorture parameter usage warnings
against your git branch rcu/dev
commit e2c83bca7e80 ("EXP: rcu: Add ->boost_tasks to assertion")
Patch no.1 contains the actual changes. Patch no.2 is for testing purposes only
and is not intended to be merged. It seems that the scripts didn’t pick up the
lines in BUSTED02.boot that set the value of gp_normal and gp_exp. But when I
hard-coded gp_normal to true in rcutorture.c, it did print out
"rcu_torture_writer3: gp_sync without primitives" as expected.
It may be better to have more informative warning messages for the new if-else blocks
in patch no.1. Feel free to revise them.
Please let me know if you have any questions.
Many thanks,
Lihao.
Lihao Liang (2):
rcutorture: Add param usage warnings
rcutorture: Add tests of param usage warnings
kernel/rcu/rcutorture.c | 16 ++++++++++++++--
tools/testing/selftests/rcutorture/configs/rcu/BUSTED02 | 7 +++++++
.../selftests/rcutorture/configs/rcu/BUSTED02.boot | 1 +
tools/testing/selftests/rcutorture/configs/rcu/CFLIST | 2 ++
4 files changed, 24 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/BUSTED02
create mode 100644 tools/testing/selftests/rcutorture/configs/rcu/BUSTED02.boot
--
2.7.4
Powered by blists - more mailing lists