Re: [PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Paul E. McKenney
On Fri, Apr 15, 2016 at 05:19:27PM -0700, Shi, Yang wrote: > 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 buildi

Re: [PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Shi, Yang
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 informa

Re: [PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Paul E. McKenney
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

Re: [PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Shi, Yang
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

Re: [PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Paul E. McKenney
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 change

[PATCH] locktorture: make verbose writable and control stats print

2016-04-15 Thread Yang Shi
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. Sign