From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Move pageflip request from vblank IRQ to ioctl
Date: Wed, 6 Jul 2011 18:44:30 +0100 [thread overview]
Message-ID: <201107061844.30779.simon.farnsworth@onelan.co.uk> (raw)
In-Reply-To: <CAH3drwYLfu4TTAM8NPrOM4rpqf+5MEVQa00Y80vjCtNUNehMtA@mail.gmail.com>
On Wednesday 6 July 2011, Jerome Glisse <j.glisse@gmail.com> wrote:
> On Wed, Jul 6, 2011 at 12:29 PM, Simon Farnsworth
>
> > In particular, I'm a bit hazy about what the fence in pageflip is
> > doing - I assume it's there to synchronize drawing and scanout, so
> > that I don't flip to a buffer that's still being drawn on by the GPU.
> >
> In my view all the fence stuff become useless as when the irq handler
> call we know we can unpin previous scanout (the crtc is scanning from
> new buffer). Otherwise it looks good (beside the optimization of
> computing how much time we should sleep instead of while msleep but
> this can be left as a latter patch).
>
So, I don't know why this makes a difference - but removing the fence
completely causes the second pageflip to stall forever. Changing it for a
radeon_bo_wait on the new frontbuffer still results in infinite stalls.
I've noticed a couple of minor issues in the patch anyway (a redundant
lock/unlock pair left in, and I should be using usleep_range not msleep, given
that I want to wait for less than a millisecond normally), so I'll respin
anyway.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
prev parent reply other threads:[~2011-07-06 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:29 [PATCH] drm/radeon: Move pageflip request from vblank IRQ to ioctl Simon Farnsworth
2011-07-06 16:43 ` Jerome Glisse
2011-07-06 17:44 ` Simon Farnsworth [this message]
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=201107061844.30779.simon.farnsworth@onelan.co.uk \
--to=simon.farnsworth@onelan.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.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