From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Paul Berry <stereotype441@gmail.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/6] Page faults to help user space debug
Date: Sat, 29 Jun 2013 14:20:40 -0700 [thread overview]
Message-ID: <20130629212040.GA690@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uGkBab385rzYhvwhKtULSt9Du-nL=w3PwaDjJ7MihS9AQ@mail.gmail.com>
On Sat, Jun 29, 2013 at 04:38:00PM +0200, Daniel Vetter wrote:
> On Sat, Jun 29, 2013 at 12:23 AM, Ben Widawsky <ben@bwidawsk.net> wrote:
> > 2. echo 2 > /sys/kernel/debug/dri/0/i915_debug_flags
> > Unbind all buffers synchronously, so any batch which has bad code will fault
> > every time and not get lucky by hitting a buffer it bound. This will not catch
> > cases where it accidentally reads/writes someone else's buffer.
>
> We already have this as the drop_caches debugfs interface. Chris used
> it to reproduce the 3.7 reloc-tree regression, the only downside is
> that no one ever got around to write the respective i-g-t ... :(
> -Daniel
In order to achieve the same behavior, one must instrument every GPU
client to use that interface before, and after every batch (you can skip
one if you're positive all clients have opted in). Also, every client
must be run as root.
This mechanism I've introduced is much simpler to achieve the intended
result.
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-06-29 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 22:23 [PATCH 0/6] Page faults to help user space debug Ben Widawsky
2013-06-28 22:23 ` [PATCH 1/6] drm/i915: Faults for scratch PTEs Ben Widawsky
2013-06-28 22:23 ` [PATCH 2/6] drm/i915: Debugfs for setting debug_flags Ben Widawsky
2013-06-28 22:23 ` [PATCH 3/6] drm/i915: Reset scratch pages when using debug_flags Ben Widawsky
2013-06-28 22:23 ` [PATCH 4/6] drm/i915: Synchronous execbuf for debug Ben Widawsky
2013-06-28 22:23 ` [PATCH 5/6] drm/i915: Let userspace create a faultable pad page Ben Widawsky
2013-06-28 22:23 ` [PATCH 6/6] drm/i915: distinguish pad and fault pages Ben Widawsky
2013-06-28 22:39 ` [PATCH 0/6] Page faults to help user space debug Chris Wilson
2013-06-28 23:30 ` Ben Widawsky
2013-06-29 7:02 ` Chris Wilson
2013-07-02 19:00 ` Paul Berry
2013-07-02 19:03 ` Chris Wilson
2013-07-02 19:18 ` Paul Berry
2013-07-06 20:11 ` Ben Widawsky
2013-07-02 19:04 ` Ben Widawsky
2013-06-29 14:38 ` Daniel Vetter
2013-06-29 21:20 ` Ben Widawsky [this message]
2013-06-29 21:28 ` Daniel Vetter
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=20130629212040.GA690@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stereotype441@gmail.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