From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/i915: Move VT-d alignment into plane->min_alignment()
Date: Tue, 28 Jan 2025 18:56:00 +0200 [thread overview]
Message-ID: <Z5kMIMhfNERQp_FL@intel.com> (raw)
In-Reply-To: <87h65j9spc.fsf@intel.com>
On Tue, Jan 28, 2025 at 11:46:23AM +0200, Jani Nikula wrote:
> On Mon, 27 Jan 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Mon, Jan 27, 2025 at 06:44:21PM +0200, Ville Syrjälä wrote:
> >> On Mon, Jan 27, 2025 at 11:50:34AM +0200, Jani Nikula wrote:
> >> > On Wed, 22 Jan 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> >> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> > >
> >> > > Currently we don't account for the VT-d alignment w/a in
> >> > > plane->min_alignment() which means that panning inside a larger
> >> > > framebuffer can still cause the plane SURF to be misaligned.
> >> > > Fix the issue by moving the VT-d alignment w/a into
> >> > > plane->min_alignment() itself (for the affected platforms).
> >> > >
> >> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> > > ---
> >> > > drivers/gpu/drm/i915/display/i9xx_plane.c | 10 ++++++++++
> >> > > drivers/gpu/drm/i915/display/intel_cursor.c | 5 +++++
> >> > > drivers/gpu/drm/i915/display/intel_fb_pin.c | 8 --------
> >> > > drivers/gpu/drm/i915/display/intel_sprite.c | 5 +++++
> >> > > drivers/gpu/drm/i915/display/skl_universal_plane.c | 4 ++++
> >> > > 5 files changed, 24 insertions(+), 8 deletions(-)
> >> > >
> >> > > diff --git a/drivers/gpu/drm/i915/display/i9xx_plane.c b/drivers/gpu/drm/i915/display/i9xx_plane.c
> >> > > index ed171fbf8720..19cc34babef3 100644
> >> > > --- a/drivers/gpu/drm/i915/display/i9xx_plane.c
> >> > > +++ b/drivers/gpu/drm/i915/display/i9xx_plane.c
> >> > > @@ -780,9 +780,14 @@ unsigned int vlv_plane_min_alignment(struct intel_plane *plane,
> >> > > const struct drm_framebuffer *fb,
> >> > > int color_plane)
> >> > > {
> >> > > + struct drm_i915_private *i915 = to_i915(plane->base.dev);
> >> > > +
> >> > > if (intel_plane_can_async_flip(plane, fb->modifier))
> >> > > return 256 * 1024;
> >> > >
> >> > > + if (intel_scanout_needs_vtd_wa(i915))
> >> > > + return 256 * 1024;
> >> >
> >> > Nitpick, would be great to convert intel_scanout_needs_vtd_wa() to
> >> > struct intel_display first, so we wouldn't have to introduce so many new
> >> > struct drm_i915_private uses.
> >>
> >> I didn't really want to add intel_display stuff to the
> >> gem side (where this is being used currently). Once
> >> its all moved into the display code (patch 3) then it
> >> makes more sense.
>
> Roger.
>
> > BTW I do have full conversion of all the low level
> > plane code (+ a bunch of other stuff including
> > intel_display_power_{put,get}() stuff) done locally.
> > But I have quite a few series on the list already
> > needing review, so not sure I should also post that
> > one right now. I can, if you especially want something
> > mundane to read?
>
> I might be up for just that, actually.
Apparently I already posted that. Go figure.
https://patchwork.freedesktop.org/series/143942/
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-01-28 16:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 15:17 [PATCH 0/5] drm/i915: Improve the display VT-d workarounds Ville Syrjala
2025-01-22 15:17 ` [PATCH 1/5] drm/i915: Move VT-d alignment into plane->min_alignment() Ville Syrjala
2025-01-27 9:50 ` Jani Nikula
2025-01-27 16:44 ` Ville Syrjälä
2025-01-27 17:27 ` Ville Syrjälä
2025-01-28 9:46 ` Jani Nikula
2025-01-28 16:56 ` Ville Syrjälä [this message]
2025-01-22 15:17 ` [PATCH 2/5] drm/i915: Use more optimal VTd alignment for planes Ville Syrjala
2025-01-22 15:17 ` [PATCH 3/5] drm/i915: Calculate the VT-d guard size in the display code Ville Syrjala
2025-01-22 15:17 ` [PATCH 4/5] drm/i915: Use per-plane VT-d guard numbers Ville Syrjala
2025-01-22 15:17 ` [PATCH 5/5] drm/i915/fbdev: Use fb->normal_view.gtt Ville Syrjala
2025-01-22 15:48 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Improve the display VT-d workarounds Patchwork
2025-01-22 15:49 ` ✓ CI.Patch_applied: success " Patchwork
2025-01-22 15:49 ` ✓ CI.checkpatch: " Patchwork
2025-01-22 15:50 ` ✓ CI.KUnit: " Patchwork
2025-01-22 16:01 ` ✓ i915.CI.BAT: " Patchwork
2025-01-22 16:07 ` ✓ CI.Build: " Patchwork
2025-01-22 16:09 ` ✓ CI.Hooks: " Patchwork
2025-01-22 16:10 ` ✗ CI.checksparse: warning " Patchwork
2025-01-22 16:37 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-23 4:16 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-23 18:32 ` ✗ i915.CI.Full: " Patchwork
2025-02-04 11:25 ` [PATCH 0/5] " Jani Nikula
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=Z5kMIMhfNERQp_FL@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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 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.