public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Updated drm-intel-testing
Date: Tue, 12 Apr 2016 10:55:50 +0100	[thread overview]
Message-ID: <570CC626.3060702@linux.intel.com> (raw)
In-Reply-To: <20160412092139.GN4329@intel.com>


On 12/04/16 10:21, Ville Syrjälä wrote:
> On Mon, Apr 11, 2016 at 09:45:11PM +0200, Daniel Vetter wrote:
>> Hi all,
>>
>> New -testing cycle with cool stuff:
>> - make modeset hw state checker atomic aware (Maarten)
>> - close races in gpu stuck detection/seqno reading (Chris)
>> - tons&tons of small improvements from Chris Wilson all over the gem code
>> - more dsi/bxt work from Ramalingam&Jani
>> - macro polish from Joonas
>> - guc fw loading fixes (Arun&Dave)
>> - vmap notifier (acked by Andrew) + i915 support by Chris Wilson
>> - create bottom half for execlist irq processing (Chris Wilson)
>> - vlv/chv pll cleanup (Ville)
>> - rework DP detection, especially sink detection (Shubhangi Shrivastava)
>> - make color manager support fully atomic (Maarten)
>> - avoid livelock on chv in execlist irq handler (Chris)
>
> The chv irq handler change needs to be backed out, or more preferably
> fixed in another way. Currently chv isn't in the best shape due to this.

Could be that the revert is not a big deal since, if the tasklet is 
working fine, the work is not done in the irq handler any longer so the 
even the looping handler will not be causing huge irqoff latencies.

Regards,

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

  reply	other threads:[~2016-04-12  9:55 UTC|newest]

Thread overview: 123+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 19:45 Updated drm-intel-testing Daniel Vetter
2016-04-11 20:26 ` Felix Miata
2016-04-12  9:21 ` Ville Syrjälä
2016-04-12  9:55   ` Tvrtko Ursulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-22 15:31 Jani Nikula
2018-11-02 10:08 Jani Nikula
2018-09-21 11:03 Joonas Lahtinen
2018-09-06 12:35 Joonas Lahtinen
2018-05-14 13:05 Jani Nikula
2018-04-13 12:28 Jani Nikula
2018-03-08 13:17 Joonas Lahtinen
2018-02-21 18:02 Joonas Lahtinen
2018-02-07  8:58 Joonas Lahtinen
2017-12-22 20:57 Rodrigo Vivi
2017-12-14 20:14 Rodrigo Vivi
2017-12-02  1:09 Rodrigo Vivi
2017-11-17 22:48 Rodrigo Vivi
2017-11-10 18:36 Rodrigo Vivi
2017-10-23 10:03 Jani Nikula
2017-10-12 19:03 Jani Nikula
2017-09-29 11:38 Jani Nikula
2017-09-07 12:03 Jani Nikula
2017-08-21 15:28 Daniel Vetter
2017-07-31  8:18 Daniel Vetter
2017-07-17  7:28 Daniel Vetter
2017-07-03  6:58 Daniel Vetter
2017-06-19  7:44 Daniel Vetter
2017-05-29 13:14 Daniel Vetter
2017-05-15  7:55 Daniel Vetter
2017-05-02  7:34 Daniel Vetter
2017-04-18  9:36 Daniel Vetter
2017-04-03  6:05 Daniel Vetter
2017-03-20  7:37 Daniel Vetter
2017-03-06  9:43 Daniel Vetter
2017-02-06  9:41 Daniel Vetter
2017-01-23  7:36 Daniel Vetter
2017-01-09  9:16 Daniel Vetter
2016-12-26 16:09 Daniel Vetter
2016-12-05  8:40 Daniel Vetter
2016-12-05  8:41 ` Daniel Vetter
2016-12-05  8:51   ` Argotti, Yann
2016-11-21  9:41 Daniel Vetter
2016-11-08  7:13 Daniel Vetter
2016-10-24  6:28 Daniel Vetter
2016-10-10  9:11 Daniel Vetter
2016-09-19  9:13 Daniel Vetter
2016-09-02  6:46 Daniel Vetter
2016-08-22  7:21 Daniel Vetter
2016-08-08  7:57 Daniel Vetter
2016-07-25  6:21 Daniel Vetter
2016-07-11  7:37 Daniel Vetter
2016-06-19 22:37 Daniel Vetter
2016-06-05 22:39 Daniel Vetter
2016-05-22 16:31 Daniel Vetter
2016-05-08 16:32 Daniel Vetter
2016-04-25  8:03 Daniel Vetter
2016-03-30  8:47 Daniel Vetter
2016-03-14  7:31 Daniel Vetter
2016-02-29  9:20 Daniel Vetter
2016-02-14 21:49 Daniel Vetter
2016-01-25  7:16 Daniel Vetter
2016-01-10 23:29 Daniel Vetter
2015-12-18 19:31 Daniel Vetter
2015-12-04 17:01 Daniel Vetter
2015-11-20 16:10 Daniel Vetter
2015-10-23 10:02 Daniel Vetter
2015-10-12  6:53 Daniel Vetter
2015-09-28  6:39 Daniel Vetter
2015-09-11 20:00 Daniel Vetter
2015-08-28 16:08 Daniel Vetter
2015-07-31  9:06 Daniel Vetter
2015-07-17 21:14 Daniel Vetter
2015-06-19 19:22 Daniel Vetter
2015-05-22 17:48 Daniel Vetter
2015-05-26  8:23 ` Daniel Martin
2015-05-08 15:42 Daniel Vetter
2015-04-23 20:12 Daniel Vetter
2015-04-10  7:36 Daniel Vetter
2015-03-27 19:25 Daniel Vetter
2015-03-13 21:20 Daniel Vetter
2015-02-27 18:16 Daniel Vetter
2015-02-13 23:47 Daniel Vetter
2015-01-30 21:42 Daniel Vetter
2015-01-17  9:46 Daniel Vetter
2014-12-19 15:26 Daniel Vetter
2014-12-05 15:02 Daniel Vetter
2014-11-21  9:42 Daniel Vetter
2014-11-07 18:12 Daniel Vetter
2014-10-24 14:51 Daniel Vetter
2014-10-03 15:41 Daniel Vetter
2014-09-19 15:09 Daniel Vetter
2014-09-05 13:16 Daniel Vetter
2014-09-09  5:08 ` Sun, Yi
2014-09-09  9:37   ` Daniel Vetter
2014-09-09 10:04     ` Daniel Vetter
2014-08-22 20:46 Daniel Vetter
2014-08-08 18:49 Daniel Vetter
2014-07-25 20:57 Daniel Vetter
2014-07-11  9:41 Daniel Vetter
2014-06-20  8:45 Daniel Vetter
2014-06-06 20:32 Daniel Vetter
2014-05-23 11:53 Daniel Vetter
2014-05-06  8:53 Daniel Vetter
2014-04-16 18:39 Daniel Vetter
2014-04-04 15:12 Daniel Vetter
2014-03-21 15:39 Daniel Vetter
2014-03-07 23:02 Daniel Vetter
2014-02-14 17:54 Daniel Vetter
2014-02-07 16:12 Daniel Vetter
2014-01-10 21:48 Daniel Vetter
2013-12-13 17:20 Daniel Vetter
2013-11-29 15:27 Daniel Vetter
2013-11-03 13:47 Daniel Vetter
2013-10-18 15:04 Daniel Vetter
2013-10-04  9:07 Daniel Vetter
2013-09-20 22:24 Daniel Vetter
2013-09-06 16:26 Daniel Vetter
2013-08-23 19:16 Daniel Vetter
2013-08-09 19:08 Daniel Vetter
2013-06-30 11:13 Daniel Vetter
2013-06-18 13:24 Daniel Vetter
2013-03-23 11:31 Daniel Vetter
2013-02-01 14:27 updated drm-intel-testing 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=570CC626.3060702@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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