From: "Kahola, Mika" <mika.kahola@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 0/7] drm/i915/fbc: FBC frontbuffer stuff
Date: Wed, 13 Apr 2022 13:51:13 +0000 [thread overview]
Message-ID: <7e8b9c6dd2ac4324995ebf3bdf80568e@intel.com> (raw)
In-Reply-To: <20220315140001.1172-1-ville.syrjala@linux.intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 15, 2022 4:00 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 0/7] drm/i915/fbc: FBC frontbuffer stuff
>
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Avoid all the FBC frontbuffer vs. atomic commit raciness by not doing any FBC
> nukes while a flip is pending. Allows us to remove the last locks from the i9xx
> plane code.
>
> I also want to explore the idea of always generating DSB batches for pipe
> commits and just excuting them on the CPU if no DSB hardware is available.
> Locked register writes (and any register reads, of which there are still a few)
> prevent me from doing that.
>
As far as I have understood, what we try to achieve with this series looks ok to me.
Reviewed-by: Mika Kahola <mika.kahola@intel.com>
> Ville Syrjälä (7):
> drm/i915/fbc: Eliminate possible_framebuffer_bits
> drm/i915/fbc: Streamline frontbuffer busy bits handling
> drm/i915/fbc: Skip nuke when flip is pending
> drm/i915: Remove remaining locks from i9xx plane udpates
> drm/i915/fbc: Remove intel_fbc_global_disable()
> drm/i915/fbc: Introduce intel_fbc_sanitize()
> drm/i915/fbc: Call intel_fbc_activate() directly from frontbuffer
> flush
>
> drivers/gpu/drm/i915/display/i9xx_plane.c | 12 ---
> drivers/gpu/drm/i915/display/intel_display.c | 4 +-
> drivers/gpu/drm/i915/display/intel_fbc.c | 88 +++++++++-----------
> drivers/gpu/drm/i915/display/intel_fbc.h | 2 +-
> drivers/gpu/drm/i915/i915_suspend.c | 4 -
> 5 files changed, 44 insertions(+), 66 deletions(-)
>
> --
> 2.34.1
prev parent reply other threads:[~2022-04-13 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 13:59 [Intel-gfx] [PATCH 0/7] drm/i915/fbc: FBC frontbuffer stuff Ville Syrjala
2022-03-15 13:59 ` [Intel-gfx] [PATCH 1/7] drm/i915/fbc: Eliminate possible_framebuffer_bits Ville Syrjala
2022-03-15 14:49 ` Jani Nikula
2022-03-15 13:59 ` [Intel-gfx] [PATCH 2/7] drm/i915/fbc: Streamline frontbuffer busy bits handling Ville Syrjala
2022-03-15 13:59 ` [Intel-gfx] [PATCH 3/7] drm/i915/fbc: Skip nuke when flip is pending Ville Syrjala
2022-03-15 13:59 ` [Intel-gfx] [PATCH 4/7] drm/i915: Remove remaining locks from i9xx plane udpates Ville Syrjala
2022-03-15 13:59 ` [Intel-gfx] [PATCH 5/7] drm/i915/fbc: Remove intel_fbc_global_disable() Ville Syrjala
2022-03-15 14:00 ` [Intel-gfx] [PATCH 6/7] drm/i915/fbc: Introduce intel_fbc_sanitize() Ville Syrjala
2022-03-15 14:00 ` [Intel-gfx] [PATCH 7/7] drm/i915/fbc: Call intel_fbc_activate() directly from frontbuffer flush Ville Syrjala
2022-03-15 14:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/fbc: FBC frontbuffer stuff Patchwork
2022-03-15 15:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-15 17:24 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-04-13 13:51 ` Kahola, Mika [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=7e8b9c6dd2ac4324995ebf3bdf80568e@intel.com \
--to=mika.kahola@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