From: "Shi, Yang" <yang.shi@linaro.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] locktorture: make verbose writable and control stats print
Date: Fri, 15 Apr 2016 17:19:27 -0700 [thread overview]
Message-ID: <5711850F.3000709@linaro.org> (raw)
In-Reply-To: <20160416000930.GD3687@linux.vnet.ibm.com>
On 4/15/2016 5:09 PM, Paul E. McKenney wrote:
> On Fri, Apr 15, 2016 at 04:45:32PM -0700, Shi, Yang wrote:
>> On 4/15/2016 4:26 PM, Paul E. McKenney wrote:
>>> On Fri, Apr 15, 2016 at 01:28:11PM -0700, Yang Shi wrote:
>>>> When building locktorture test into kernel image, it keeps printing out
>>>> stats information even though there is no lock type specified.
>>>>
>>>> There is already verbose parameter to control print, but it is read-only,
>>>> so it can't be changed at runtime. Make verbose read-write and control
>>>> stats print.
>>>>
>>>> Signed-off-by: Yang Shi <yang.shi@linaro.org>
>>>
>>> Interesting change!
>>>
>>> But just out of curiosity, when you boot with locktorture built in,
>>> do you specify the shutdown_secs boot parameter? If so, another
>>
>> No, just use the default value, which is 0 for shutdown_secs.
>>
>>> approach would be to shutdown immediately upon detecting an error
>>> during initialization.
>>
>> In my case, it looks there is not error involved.
>
> You said that there is no lock type specified, but that should mean that
> the default ("spin_lock") is chosen. If so, I would expect it to just
Yes, spin_lock is chosen by default.
> do the test, at least if locktorture.torture_runnable has been set.
But, the default value of torture_runnable is 0. And, it is readonly
parameter too. This prevents torture from running if it is built into
kernel instead of module.
Actually, I'm confused why there is not LOCK_TORTURE_TEST_RUNNABLE
Kconfig like RCU torture?
Thanks,
Yang
>
> Either way, the usual way to make locktorture shut up would be to boot
> with locktorture.stat_interval=0.
>
>>> If not, I would like to know more about your use case.
>>
>> In my test, I just built locktorture test into kernel instead of a
>> module then check how it behaves, no specific purpose.
>>
>> It sounds like not a normal approach to use it.
>
> Agreed, I do believe that this is a case of "working as designed".
>
> Thanx, Paul
>
next prev parent reply other threads:[~2016-04-16 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 20:28 [PATCH] locktorture: make verbose writable and control stats print Yang Shi
2016-04-15 23:26 ` Paul E. McKenney
2016-04-15 23:45 ` Shi, Yang
2016-04-16 0:09 ` Paul E. McKenney
2016-04-16 0:19 ` Shi, Yang [this message]
2016-04-16 0:31 ` Paul E. McKenney
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=5711850F.3000709@linaro.org \
--to=yang.shi@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.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