dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCHv2] drm/radeon: Move pageflip request from vblank IRQ to ioctl
Date: Wed, 06 Jul 2011 22:54:06 +0200	[thread overview]
Message-ID: <1309985646.4583.24.camel@mattotaupa> (raw)
In-Reply-To: <1309975448-24373-1-git-send-email-simon.farnsworth@onelan.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 969 bytes --]

Am Mittwoch, den 06.07.2011, 19:04 +0100 schrieb Simon Farnsworth:
> The radeon pageflip ioctl handler delayed submitting the pageflip to
> hardware until the vblank IRQ handler. On AMD Fusion (PALM GPU, G-T56N
> CPU), when using a reduced blanking CVT mode, a pageflip submitted to
> hardware in the IRQ handler failed to complete before the end of the
> vblank, resulting in a guaranteed halving of frame rate despite having
> plenty of spare CPU and GPU resource.
> 
> Fix this by moving the pageflip request to hardware into the pageflip
> ioctl, waiting until we are outside a vblank period so that pageflip
> timing is still accurate.
> 
> This doubles my frame rate in reduced blanking modes, and does not
> have an impact on CPU usage in normal blanking modes.
> 
> Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>

Please mention the bug number the commit closes/addresses in the commit
message.

[…]


Thanks,

Paul

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-07-06 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 18:04 [PATCHv2] drm/radeon: Move pageflip request from vblank IRQ to ioctl Simon Farnsworth
2011-07-06 20:54 ` Paul Menzel [this message]
2011-07-07  7:46 ` Michel Dänzer

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=1309985646.4583.24.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=dri-devel@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