From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, Ben Widawsky <ben@bwidawsk.net>,
intel-gfx@lists.freedesktop.org
Subject: Re: No more read/write ioctls
Date: Fri, 08 Apr 2011 18:29:29 +0100 [thread overview]
Message-ID: <b7da2f$r17vi7@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <87fwpsfz49.fsf@pollan.anholt.net>
On Fri, 08 Apr 2011 07:10:14 -1000, Eric Anholt <eric@anholt.net> wrote:
> I thought previously we had issues with debugfs nodes which could wedge
> the system (out of range mmio reads)?
Yes, we have indeed triggered hard hards by trying to read the wrong
registers before. That's why I was interested in seeing Ben codify the
reserved ranges so that we can have at least a warning before doing
something idiotic.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-08 17:29 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 [this message]
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 ` [PATCH v3 2/2] drm/i915: debugfs for register write taint Ben Widawsky
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='b7da2f$r17vi7@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=eric@anholt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.