From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Rodrigo Vivi <rodrigo.vivi@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Add Baytrail PSR Support.
Date: Wed, 29 Jan 2014 20:20:08 +0100 [thread overview]
Message-ID: <20140129192008.GJ7444@phenom.ffwll.local> (raw)
In-Reply-To: <20140129142603.GF28110@nuc-i3427.alporthouse.com>
On Wed, Jan 29, 2014 at 02:26:03PM +0000, Chris Wilson wrote:
> On Wed, Jan 29, 2014 at 12:23:15PM -0200, Rodrigo Vivi wrote:
> > ok, got it.
> >
> > So, the correct here is to remove inactivate from set_domain and add
> > gem_bo_busy call on MMAP_GTT testcase?
>
> That would match what we should do today. It's just whether we take the
> opportunity to define a consistent behaviour...
Afaik we don't do a gem_bo_busy after gtt access, at least no everwhere.
Which sucks, but meh. At least I've thought that the busy is just after
gpu rendering.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-01-29 19:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 18:16 [PATCH 1/4] drm/i915: Set primary plane enable at dpcntrl Rodrigo Vivi
2014-01-23 18:16 ` [PATCH 2/4] drm/i915: move psr_setup_done to psr struct Rodrigo Vivi
2014-01-24 14:50 ` Ville Syrjälä
2014-01-24 16:02 ` Rodrigo Vivi
2014-01-23 18:16 ` [PATCH 3/4] drm/i915: Update PSR on resume Rodrigo Vivi
2014-02-05 19:04 ` [PATCH 1/2] " Rodrigo Vivi
2014-01-23 18:16 ` [PATCH 4/4] drm/i915: Add Baytrail PSR Support Rodrigo Vivi
2014-01-23 19:19 ` [PATCH] " Rodrigo Vivi
2014-01-24 14:53 ` Ville Syrjälä
2014-01-24 16:05 ` Rodrigo Vivi
2014-01-24 17:41 ` Ville Syrjälä
2014-01-28 19:47 ` [PATCH 4/4] " Rodrigo Vivi
2014-01-29 12:47 ` [PATCH] " Rodrigo Vivi
2014-01-29 13:12 ` Chris Wilson
2014-01-29 13:24 ` Rodrigo Vivi
2014-01-29 13:27 ` Chris Wilson
2014-01-29 13:54 ` Rodrigo Vivi
2014-01-29 14:02 ` Chris Wilson
2014-01-29 14:23 ` Rodrigo Vivi
2014-01-29 14:26 ` Chris Wilson
2014-01-29 19:20 ` Daniel Vetter [this message]
2014-01-29 14:55 ` Rodrigo Vivi
2014-01-29 19:21 ` Daniel Vetter
2014-02-01 11:34 ` Chris Wilson
2014-02-04 10:49 ` Daniel Vetter
2014-01-29 14:56 ` Ville Syrjälä
2014-01-29 15:47 ` Rodrigo Vivi
2014-01-29 16:38 ` Ville Syrjälä
2014-01-29 17:48 ` Rodrigo Vivi
2014-01-29 18:24 ` Ville Syrjälä
2014-01-29 15:50 ` Rodrigo Vivi
2014-01-30 13:02 ` Chris Wilson
2014-01-30 17:01 ` Rodrigo Vivi
2014-02-04 10:53 ` Daniel Vetter
2014-02-04 13:03 ` Rodrigo Vivi
2014-02-04 13:54 ` Daniel Vetter
2014-02-05 19:04 ` [PATCH 2/2] " Rodrigo Vivi
2014-02-07 17:24 ` Ville Syrjälä
2014-02-07 18:05 ` Rodrigo Vivi
2014-02-07 18:39 ` Ville Syrjälä
2014-02-12 16:29 ` [PATCH] " Daniel Vetter
2014-01-23 19:19 ` [PATCH] drm/i915: Set primary plane enable at dpcntrl Rodrigo Vivi
2014-01-24 14:58 ` Ville Syrjälä
2014-01-28 19:46 ` [PATCH 1/4] " Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
2013-12-17 19:57 [PATCH 1/2] drm/i915: move psr_setup_done to psr struct Rodrigo Vivi
2013-12-17 20:31 ` [PATCH] drm/i915: Add Baytrail PSR Support Rodrigo Vivi
2013-12-18 10:03 ` Chris Wilson
2013-12-18 10:27 ` Rodrigo Vivi
2013-12-18 10:30 ` Rodrigo Vivi
2013-12-18 10:37 ` 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=20140129192008.GJ7444@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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 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.