[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+wgaPOkMmVHYeKAx3bjBF_Yn=XAA8Jf7CbeJygy8xPTS06NdA@mail.gmail.com>
Date: Fri, 27 Sep 2019 11:11:15 -0700
From: Hridya Valsaraju <hridya@...gle.com>
To: Christian Brauner <christian.brauner@...ntu.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arve Hjønnevåg <arve@...roid.com>,
Todd Kjos <tkjos@...roid.com>,
Martijn Coenen <maco@...roid.com>,
Joel Fernandes <joel@...lfernandes.org>,
"open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
LKML <linux-kernel@...r.kernel.org>,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH v3 0/4] Add binder state and statistics to binderfs
On Fri, Sep 27, 2019 at 6:19 AM Christian Brauner
<christian.brauner@...ntu.com> wrote:
>
> On Tue, Sep 03, 2019 at 09:16:51AM -0700, Hridya Valsaraju wrote:
> > Currently, the only way to access binder state and
> > statistics is through debugfs. We need a way to
> > access the same even when debugfs is not mounted.
> > These patches add a mount option to make this
> > information available in binderfs without affecting
> > its presence in debugfs. The following debugfs nodes
> > will be made available in a binderfs instance when
> > mounted with the mount option 'stats=global' or 'stats=local'.
> >
> > /sys/kernel/debug/binder/failed_transaction_log
> > /sys/kernel/debug/binder/proc
> > /sys/kernel/debug/binder/state
> > /sys/kernel/debug/binder/stats
> > /sys/kernel/debug/binder/transaction_log
> > /sys/kernel/debug/binder/transactions
>
> I'm sitting in a talk from Jonathan about kernel documentation and what
> I realized is that we forgot to update the documentation I wrote for
> binderfs in Documentation/admin-guide/binderfs.rst to reflect the new
> stats=global mount option. Would be great if we could add that after rc1
> is out. Would you have time to do that, Hridya?
Thanks for catching that Christian, sorry about the miss! I will send
out a patch ASAP to add the documentation.
Regards,
Hridya
>
> Should just be a new entry under:
>
> Options
> -------
> max
> binderfs instances can be mounted with a limit on the number of binder
> devices that can be allocated. The ``max=<count>`` mount option serves as
> a per-instance limit. If ``max=<count>`` is set then only ``<count>`` number
> of binder devices can be allocated in this binderfs instance.
> stats
> <description>
>
> Thanks!
> Christian
Powered by blists - more mailing lists