From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Robert Jennings <rcj@linux.vnet.ibm.com>
Subject: Re: [PATCH] debugfs: add get/set for atomic types
Date: Fri, 26 Oct 2012 13:46:38 -0500 [thread overview]
Message-ID: <508ADA8E.9000604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121026161315.GA13134@kroah.com>
On 10/26/2012 11:13 AM, Greg Kroah-Hartman wrote:
> On Fri, Oct 26, 2012 at 10:49:01AM -0500, Seth Jennings wrote:
>> debugfs currently lacks the ability to create attributes
>> that set/get atomic_t values.
>>
>> This patch adds support for this through a new
>> debugfs_create_atomic_t() function.
>
> Why would you want to set an atomic variable type from userspace?
In my particular use case, I'm not setting from userspace, only getting.
All the other types are symmetric, being both settable and gettable,
so I was just trying to blend with the other types.
> What in-kernel code needs this?
None, yet. I am working on code that does.
If you would rather me send this as part of the patchset for that
code, I can. I just wanted to get this in early if I could since it
is functionality I can see others using.
For an example, see drivers/staging/ramster/zcache-main.c:132 where
both atomic and non-atomic version of stats are being maintained so
that the non-atomic version can be read by debugfs.
Beside not having an in-kernel user yet, does this approach look good
to you?
Seth
next prev parent reply other threads:[~2012-10-26 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 15:49 [PATCH] debugfs: add get/set for atomic types Seth Jennings
2012-10-26 16:13 ` Greg Kroah-Hartman
2012-10-26 18:46 ` Seth Jennings [this message]
2012-10-26 23:55 ` Greg Kroah-Hartman
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=508ADA8E.9000604@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcj@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;
as well as URLs for NNTP newsgroup(s).