intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm/i915: Allow mmio updates on all platforms.
Date: Thu, 24 Mar 2016 15:42:28 +0100	[thread overview]
Message-ID: <56F3FCD4.9060202@linux.intel.com> (raw)
In-Reply-To: <20160324142603.GB4329@intel.com>

Op 24-03-16 om 15:26 schreef Ville Syrjälä:
> On Thu, Mar 24, 2016 at 09:35:04AM +0100, Maarten Lankhorst wrote:
>> Op 23-03-16 om 16:07 schreef Ville Syrjälä:
>>> On Wed, Mar 23, 2016 at 02:24:30PM +0100, Maarten Lankhorst wrote:
>>>> Rename intel_unpin_work to intel_flip_work and use it for mmio flips
>>>> and unpinning. Use flip_queued_req to hold the wait request in the
>>>> mmio case and allow the vblank interrupt to complete mmio work to
>>>> have mmio flips run correctly on g4 and earlier.
>>> Before you actually go and trust drm_vblank_count() you should make it
>>> race free.
>> How about adding the below to the patch?
> You can't just mix the hw and sw counter. Using the hw counter would be
> neat because it doesn't require so much work to be race-free, but that
> leaves out gen2 which I don't like. My atomic code used the hw counter
> though, but I had plans to fall back to the sw counter on gen2
> eventually.
>
So I dug in a little bit more..

MMIO updates don't require accurate vblank count for anything, so even if it was completely removed it would work.
The only thing it's used for is for cs flips, if more than 1 vblank passed since submission, the request gets a rps boost.

If more than 3 vblanks have passed after the request the cs flip waits on completed, the cs page flip is considered stuck
and will be forcefully completed.

With stale values the worst case rps boost might get applied right away, or the cs flip is forcefully completed after only 2 vblanks.
Neither affects mmio flips, so ignore this extra hunk and look at the original patch. :)

~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-24 14:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 13:24 [PATCH 0/6] drm/i915: Rework page flip to be more atomic like Maarten Lankhorst
2016-03-23 13:24 ` [PATCH 1/6] drm/i915: Remove stallcheck special handling Maarten Lankhorst
2016-03-23 13:24 ` [PATCH 2/6] drm/i915: Remove intel_prepare_page_flip Maarten Lankhorst
2016-03-23 15:06   ` Ville Syrjälä
2016-03-23 13:24 ` [PATCH 3/6] drm/i915: Add the exclusive fence to plane_state Maarten Lankhorst
2016-03-23 13:24 ` [PATCH 4/6] drm/i915: Allow mmio updates on all platforms Maarten Lankhorst
2016-03-23 15:07   ` Ville Syrjälä
2016-03-24  8:35     ` Maarten Lankhorst
2016-03-24 14:26       ` Ville Syrjälä
2016-03-24 14:42         ` Maarten Lankhorst [this message]
2016-03-24 14:48           ` Ville Syrjälä
2016-03-24 15:19             ` Maarten Lankhorst
2016-03-24 15:32               ` Ville Syrjälä
2016-03-29  8:03                 ` Maarten Lankhorst
2016-03-30 13:04                   ` Ville Syrjälä
2016-03-23 13:24 ` [PATCH 5/6] drm/i915: Convert flip_work to a list Maarten Lankhorst
2016-03-23 13:24 ` [PATCH 6/6] drm/i915: Rework intel_crtc_page_flip to be almost atomic Maarten Lankhorst

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=56F3FCD4.9060202@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).