Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org, Keith@freedesktop.org
Subject: Re: [PATCH 1/3] i915: Remove implied length of 2 from GFX_OP_PIPE_CONTROL #define.
Date: Tue, 11 Oct 2011 11:53:56 -0700	[thread overview]
Message-ID: <20111011115356.0663b544@jbarnes-desktop> (raw)
In-Reply-To: <20111011113936.7a4291d0@bwidawsk.net>


[-- Attachment #1.1: Type: text/plain, Size: 870 bytes --]

On Tue, 11 Oct 2011 11:39:36 -0700
Ben Widawsky <ben@bwidawsk.net> wrote:

> On Tue, 11 Oct 2011 10:20:04 -0700
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> 
> > On Tue, 11 Oct 2011 13:09:17 +0200
> > Daniel Vetter <daniel@ffwll.ch> wrote:
> > 
> > > Switching to PIPE_CONTROL with the snb workaround seems to fix the hangs I
> > > see when running cairo-perf-traces.
> > > 
> > > Tested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > 
> > Ah wow, so it actually fixes a bug.  Let's get this upstream soon then;
> > Ben do you want to re-post or should I?
> > 
> > Thanks,
> If nobody else thinks it's a good idea, just slap on my r-b and call it
> done.
> 
> I don't care enough to repost or ask you to do so.

Ok as long as it still applies, great.

Keith can you pick this up?

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2011-10-11 18:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  6:02 [PATCH 1/3] i915: Remove implied length of 2 from GFX_OP_PIPE_CONTROL #define Kenneth Graunke
2011-10-04  6:02 ` [PATCH 2/3] i915: Rename PIPE_CONTROL bit defines to be less terse Kenneth Graunke
2011-10-04  8:30   ` Daniel Vetter
2011-10-05  5:13     ` Kenneth Graunke
2011-10-05 10:05       ` Daniel Vetter
2011-10-05 22:29   ` Ben Widawsky
2011-10-04  6:02 ` [PATCH 3/3] drm/i915: Use PIPE_CONTROL for flushing on gen6+ Kenneth Graunke
2011-10-05 22:57   ` Ben Widawsky
2011-10-05 23:36     ` Chris Wilson
2011-10-05 23:54       ` Daniel Vetter
2011-10-06  0:59     ` Eric Anholt
2011-10-06  5:15       ` Ben Widawsky
2011-10-06 18:00         ` Eric Anholt
2011-10-06 19:01           ` Ben Widawsky
2011-10-05 23:39   ` Ben Widawsky
2011-10-05 20:35 ` [PATCH 1/3] i915: Remove implied length of 2 from GFX_OP_PIPE_CONTROL #define Ben Widawsky
2011-10-11 11:09 ` Daniel Vetter
2011-10-11 17:20   ` Jesse Barnes
2011-10-11 18:39     ` Ben Widawsky
2011-10-11 18:53       ` Jesse Barnes [this message]
2011-10-11 22:17         ` Keith Packard

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=20111011115356.0663b544@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=Keith@freedesktop.org \
    --cc=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