From: Ben Widawsky <ben@bwidawsk.net>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v3 2/2] drm/i915: debugfs for register write taint
Date: Fri, 1 Apr 2011 16:54:49 -0700 [thread overview]
Message-ID: <1301702089-25644-3-git-send-email-ben@bwidawsk.net> (raw)
In-Reply-To: <1301621965-23185-1-git-send-email-ben@bwidawsk.net>
Provide an interface to see which register ranges have been tainted by
the user's interaction.
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
---
drivers/gpu/drm/i915/i915_debugfs.c | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index 87c8e29..7142a0c 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -1186,6 +1186,25 @@ static int i915_gem_framebuffer_info(struct seq_file *m, void *data)
return 0;
}
+static int i915_user_tainted_info(struct seq_file *m, void *unused)
+{
+ struct drm_info_node *node = (struct drm_info_node *) m->private;
+ struct drm_device *dev = node->minor->dev;
+ drm_i915_private_t *dev_priv = dev->dev_private;
+ struct i915_register_range *range = dev_priv->register_map.map;
+ u32 range_count = dev_priv->register_map.length;
+
+ while(range_count--) {
+ if (range->user_tainted) {
+ seq_printf(m, "tainted register range 0x%08x->0x%08x\n",
+ range->base, range->size);
+ }
+ range++;
+ }
+
+ return 0;
+}
+
static int
i915_wedged_open(struct inode *inode,
struct file *filp)
@@ -1324,6 +1343,7 @@ static struct drm_info_list i915_debugfs_list[] = {
{"i915_sr_status", i915_sr_status, 0},
{"i915_opregion", i915_opregion, 0},
{"i915_gem_framebuffer", i915_gem_framebuffer_info, 0},
+ {"i915_user_tainted", i915_user_tainted_info, 0},
};
#define I915_DEBUGFS_ENTRIES ARRAY_SIZE(i915_debugfs_list)
--
1.7.3.4
next prev parent reply other threads:[~2011-04-01 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 1:31 [PATCH] drm/i915: read/write IOCTLs Ben Widawsky
2011-04-01 1:39 ` [PATCH v2] " Ben Widawsky
2011-04-01 23:54 ` Read/Write IOCTL compromise Ben Widawsky
2011-04-06 21:38 ` No more read/write ioctls Ben Widawsky
2011-04-08 17:10 ` Eric Anholt
2011-04-08 17:29 ` Chris Wilson
2011-04-01 23:54 ` [PATCH v3 1/2] drm/i915: read/write ioctls for userspace Ben Widawsky
2011-04-04 17:14 ` Chris Wilson
2011-04-05 1:30 ` Read/Write ioctls Ben Widawsky
2011-04-05 1:30 ` [PATCH v4] drm/i915: read/write ioctls for userspace Ben Widawsky
2011-04-01 23:54 ` Ben Widawsky [this message]
2011-04-01 6:36 ` [PATCH] drm/i915: read/write IOCTLs Chris Wilson
2011-04-01 7:06 ` Ben Widawsky
2011-04-01 7:32 ` Chris Wilson
2011-04-01 18:51 ` Eric Anholt
2011-04-02 6:46 ` Chris Wilson
2011-04-02 15:16 ` Ben Widawsky
2011-04-04 1:35 ` Ben Widawsky
2011-04-04 7:36 ` Chris Wilson
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=1301702089-25644-3-git-send-email-ben@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).