All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: Mario Kleiner <mario.kleiner@tuebingen.mpg.de>,
	Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Daenzer, Michel" <Michel.Daenzer@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: Flickering with page-flipping on Acer Iconia W500 (AMD C-50 APU)
Date: Wed, 22 Feb 2012 11:20:22 -0500	[thread overview]
Message-ID: <4F4515C6.2000206@amd.com> (raw)
In-Reply-To: <4F443BA9.301@tuebingen.mpg.de>



On 12-02-21 07:49 PM, Mario Kleiner wrote:
> On 02/21/2012 09:07 PM, Alex Deucher wrote:
[snip]
>> The fix looks ok to me.  Mario any thoughts?
>>
>> Reviewed-by: Alex Deucher<alexdeucher@gmail.com>
>>
>
> Hi,
>
> the fix looks ok to me for that device, but could we make it
> conditional on the AMD C-50 APU and similar pieces? It is the right
> thing to do for that gpu, but for regular desktop gpus it is too
> pessimistic if it defers the pageflip timestamping and completion
> event for an already completed flip:
>
> 1. Makes the timestamps 1 refresh too late, causing timing sensitive
> software like mine to detect false positives -- reporting skipped
> frames were there weren't any. Not as bad as missing a really skipped
> frame, but still not great.

Agreed. I was going to perform some more experiments on other hardware
to determine what the right threshold is for different hardware
generations. I hope I'll get to that this week.

>
> 2. Can reduce the framerate due to throttling the client, especially
> on systems that are already challenged wrt. to their irq timing.
>
> Is the vblank period very short on these kind of devices? From Felix
> description is sounds as if it is only 2 scanlines?

It looks like that.

Thanks for the feedback,
  Felix

>
> thanks,
> -mario
>

-- 
 _____    Felix Kuehling
 \ _  |   MTS Software Development Eng.
 /|_| |   SW-Linux Base Gfx | AMD
|__/ \|   T 905.882.2600 x8928

  reply	other threads:[~2012-02-22 16:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:43 Flickering with page-flipping on Acer Iconia W500 (AMD C-50 APU) Felix Kuehling
2012-02-21 20:07 ` Alex Deucher
2012-02-21 23:34   ` Paul Menzel
2012-02-22  0:49   ` Mario Kleiner
2012-02-22 16:20     ` Felix Kuehling [this message]
2012-02-24 21:20       ` Felix Kuehling
2012-02-25  4:38         ` Mario Kleiner
2012-02-25 18:06           ` Alex Deucher
2012-02-27 15:47           ` Felix Kuehling
2012-02-28 14:40             ` Mario Kleiner
2012-02-28 15:06               ` Felix Kuehling
2012-02-29 10:36                 ` Dave Airlie
2012-02-29 10:57                   ` Paul Menzel

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=4F4515C6.2000206@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Michel.Daenzer@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mario.kleiner@tuebingen.mpg.de \
    /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.