From: Ben Widawsky <ben@bwidawsk.net>
To: Paul Berry <stereotype441@gmail.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/6] Page faults to help user space debug
Date: Tue, 2 Jul 2013 12:04:33 -0700 [thread overview]
Message-ID: <20130702190432.GA937@bwidawsk.net> (raw)
In-Reply-To: <CA+yLL64oqDgc+43OcP8X_E0Vj3-+EZHJ1XVZ5knabgwa3xuNwA@mail.gmail.com>
On Tue, Jul 02, 2013 at 12:00:48PM -0700, Paul Berry wrote:
> On 28 June 2013 15:39, Chris Wilson <[1]chris@chris-wilson.co.uk>
> wrote:
>
[snip]
> I'll try to give the patches a shot soon to make sure they work.
By the way, if it wasn't clear, any combinations of the debug flags
should work, ie. echo 7 > ....
>
> References
>
> 1. mailto:chris@chris-wilson.co.uk
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-07-02 19:04 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 [this message]
2013-06-29 14:38 ` Daniel Vetter
2013-06-29 21:20 ` Ben Widawsky
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=20130702190432.GA937@bwidawsk.net \
--to=ben@bwidawsk.net \
--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