public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Flush outstanding unpin tasks before pageflipping
Date: Thu, 01 Nov 2012 16:52:05 +0000	[thread overview]
Message-ID: <3830942.fjPon6j4qR@deuteros> (raw)
In-Reply-To: <eeac1e$4rql7n@AZSMGA002.ch.intel.com>

On Thursday 01 November 2012 16:20:03 Chris Wilson wrote:
> On Thu, 1 Nov 2012 09:04:02 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> 
wrote:
> > On Thu, 01 Nov 2012 15:52:23 +0000
> > 
> > Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > > Actually I've justified the blocking here to myself, and prefer it to
> > > simply running the crtc->unpin_work. If userspace is swamping the system
> > > so badly that we can run the kthreads quick enough, it deserves a stall.
> > > Note that the unpin leak is still about the 3rd most common bug in
> > > fedora,
> > > so this stall will be forced on many machines.
> > 
> > Hm funky, why does Fedora hit it so much?  Does some of the GNOME shell
> > stuff run unthrottled or something?
> 
> I don't think so. I trust that in Tvrtko's use case, he is not so much as
> hogging the GPU as keeping the system as a whole relatively busy. So I
> suspect it is more to do with CPU starvation of the kthreads than
> anything else.
> 
> Tvrtko, do you have any feeling for why your machine was easily
> suspectible to this leak? Are the stalls noticeable and do they affect
> your performance targets?

We didn't bother looking for any stalls, but for a long time we were 
occasionally hitting this pin_count BUG i915_gem_object_pin. So it didn't in 
fact affect our performance targets as much it completely wrecked our system.

If this patch causes an occasional stall instead, given that this bug triggers 
every 3-4 hours of uptime, we are fine with that. If a frame or so is missed 
every couple hours on low end hardware we don't care that much.

More on the actual workload...

Only recently we got lucky and found a platform and workload where it happens 
reliably. And this patch reliably fixes that.

In this workload CPU is being loaded 50-60% decoding a movie and rendering it 
to a full screen window. Our proprietary compositor page flips at 60Hz only, 
not faster. Together with another small semi-transparent window being rendered 
on top of the full screen movie. Movie played is a 25fps one, which means the 
full screen window is damaged 25 out of 60 frames (give or take) which is when 
we render to our back buffer and page flip at the vsync rate (60Hz).

According to intel_gpu_top tool, GPU load is roughly at 40%, apart from the 
"Framebuffer Compression" metric which is maxed out, if that is one is at all 
valid.

This particular scenario triggers the bug only on two of our Atom based 
platform both with a NM10/Pineview G/i915 chipset.

Tvrtko

  reply	other threads:[~2012-11-01 17:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01  9:26 [PATCH] drm/i915: Flush outstanding unpin tasks before pageflipping Chris Wilson
2012-11-01 15:07 ` Jesse Barnes
2012-11-01 15:18   ` Chris Wilson
2012-11-01 15:29     ` Daniel Vetter
2012-11-01 15:34       ` Jesse Barnes
2012-11-01 15:52         ` Chris Wilson
2012-11-01 16:04           ` Jesse Barnes
2012-11-01 16:20             ` Chris Wilson
2012-11-01 16:52               ` Tvrtko Ursulin [this message]
2012-11-01 16:58                 ` Jesse Barnes
2012-11-05 11:36                   ` Simon Farnsworth
2012-11-02 21:31                 ` Eric Anholt
2012-11-20 16:15 ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2012-09-28 11:29 Chris Wilson
2012-09-28 12:05 ` Ville Syrjälä
2012-09-28 12:07   ` Chris Wilson
2012-09-28 12:20     ` Ville Syrjälä

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=3830942.fjPon6j4qR@deuteros \
    --to=tvrtko.ursulin@onelan.co.uk \
    --cc=chris@chris-wilson.co.uk \
    --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