mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Jones <rob.jones@codethink.co.uk>
To: gregkh@linuxfoundation.org
Cc: rdunlap@infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kernel@lists.codethink.co.uk,
	ian.molton@codethink.co.uk, ben.dooks@codethink.co.uk,
	rob.jones@codethink.co.uk
Subject: [PATCH 0/1] A debugfs file system for managed resources (devres)
Date: Thu, 24 Jul 2014 16:18:00 +0100	[thread overview]
Message-ID: <1406215081-15113-1-git-send-email-rob.jones@codethink.co.uk> (raw)

A fairly low overhead debug tool that may be useful to anyone developing
a device driver that uses managed resources.

It allows limited inspection from userspace of managed resources currently
allocated to devices.

When building the kernel, setting flag DEVRES_DEBUGFS adds debug code that
causes a directory to be created in the debugfs file system which will
contain a file for each device that uses managed resources. When read,
this file returns some basic debug information about all the managed
resources currently allocated to that device.

It is possible to trivially identify resources such as GPIOs, IRQs and
memory allocated using devm_kmalloc() without the use of intrusive debug
tools.

Rob Jones (1):
  Managed Devices devres_debugfs file system

 Documentation/driver-model/devres-debugfs.txt |  140 +++++++++
 drivers/base/Kconfig                          |   18 ++
 drivers/base/devres.c                         |  387 +++++++++++++++++++++++++
 3 files changed, 545 insertions(+)
 create mode 100644 Documentation/driver-model/devres-debugfs.txt

-- 
1.7.10.4


             reply	other threads:[~2014-07-24 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 15:18 Rob Jones [this message]
2014-07-24 15:18 ` [PATCH 1/1] Managed Devices devres_debugfs file system Rob Jones
2014-07-24 15:35   ` Tobias Klauser
2014-07-24 15:59   ` Greg KH
2014-07-25 11:11     ` Rob Jones
2014-07-27  3:31       ` Greg KH

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=1406215081-15113-1-git-send-email-rob.jones@codethink.co.uk \
    --to=rob.jones@codethink.co.uk \
    --cc=ben.dooks@codethink.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=ian.molton@codethink.co.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@lists.codethink.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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

all inboxes | Powered by JetHome®