From: Eric Anholt <eric@anholt.net>
To: intel-gfx@lists.freedesktop.org
Cc: mesa-dev@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [Intel-gfx] [PATCH 04/10] i965: setup system routine
Date: Mon, 18 Jul 2011 11:19:17 -0700 [thread overview]
Message-ID: <874o2jjvtm.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1310945148-6777-5-git-send-email-ben@bwidawsk.net>
[-- Attachment #1.1: Type: text/plain, Size: 750 bytes --]
On Sun, 17 Jul 2011 16:25:42 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> Upload the system routine as part of the invariant state if debugging.
>
> Remove SIP setting if not debugging to make it more friendly for others
> that may be debugging shaders or media kernels.
>
> v2: removed comment per Chris
This patch doesn't really make sense to me. Nothing good will come of
my driver's buffer execution landing inside someone else's debug kernel,
right? So why should my driver's batchbuffer be leaving their SIP in
place?
Of course, if we're landing in a SIP at all from our !brw->wm.debugging
batchbuffers, we're screwed if we don't have actual SIP instructions in
place, so I guess this doesn't *really* change anything.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
next prev parent reply other threads:[~2011-07-18 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 23:25 [PATCH 00/10] fs debugging: incorporated Chris' feedback Ben Widawsky
2011-07-17 23:25 ` [PATCH 01/10] intel: shared header for shader debugging Ben Widawsky
2011-07-17 23:25 ` [PATCH 02/10] i965: copy in system routine, reserve extra scratch Ben Widawsky
2011-07-17 23:25 ` [PATCH 03/10] i965: Reserve scratch space for debugger communication Ben Widawsky
2011-07-17 23:25 ` [PATCH 04/10] i965: setup system routine Ben Widawsky
2011-07-18 18:19 ` Eric Anholt [this message]
2011-07-19 4:48 ` Ben Widawsky
2011-07-17 23:25 ` [PATCH 05/10] i965: emit breakpoints Ben Widawsky
2011-07-17 23:25 ` [PATCH 06/10] i965: attach to a listening debugger Ben Widawsky
2011-07-17 23:25 ` [PATCH 07/10] intel-gpu-tools: register range handling for forcewake hooks Ben Widawsky
2011-07-17 23:25 ` [PATCH 08/10] intel-gpu-tools/forcewaked: sample forcewake app Ben Widawsky
2011-07-17 23:25 ` [PATCH 09/10] debugging: add important debug regs Ben Widawsky
2011-07-17 23:25 ` [PATCH 10/10] debugging: shader debugging Ben Widawsky
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=874o2jjvtm.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mesa-dev@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.