From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Dave Airlie <airlied@linux.ie>,
daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: drm] Atomic update on pipe (A) took 119 us, max time under evasion is 100 us
Date: Thu, 4 May 2017 20:42:14 +0300 [thread overview]
Message-ID: <20170504174214.GA12629@intel.com> (raw)
In-Reply-To: <18c075da-c055-fbfc-a022-ed9efefceaef@kernel.dk>
On Thu, May 04, 2017 at 09:26:09AM -0600, Jens Axboe wrote:
> Hi,
>
> Running current -git on my laptop (20FB, X1 Carbon gen4, skylake), I get
> a lot of the below warnings. Things seem to work fine (in fact it seems
> faster in general use than previously), but it's a lot of warning spew.
>
> [ 764.877978] [drm] Atomic update on pipe (A) took 156 us, max time under evasion is 100 us
I tried to optimize this a bit recently but indeed it's stil known to be too
slow. Looks like all of that stuff did land in Linus's tree already,
so presumably you have it all already.
I did have some further ideas that should help but I got sidetracked by
other things before I managed to finish the work. I guess I'll need to get
back on that horse and try to finish what I started.
In the meantime, maybe we should just silence this error spew again
until we're more confident about meeting the deadlines. Maarten?
Do you have lockdep enabled BTW? Based on what I've seen lockdep does
seem be a major contributor to slowness here.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-04 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 15:26 drm] Atomic update on pipe (A) took 119 us, max time under evasion is 100 us Jens Axboe
2017-05-04 17:42 ` Ville Syrjälä [this message]
2017-05-04 17:43 ` Jens Axboe
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=20170504174214.GA12629@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=axboe@kernel.dk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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 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.