From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915: Improve the display VT-d workarounds
Date: Tue, 04 Feb 2025 13:25:22 +0200 [thread overview]
Message-ID: <87pljy54v1.fsf@intel.com> (raw)
In-Reply-To: <20250122151755.6928-1-ville.syrjala@linux.intel.com>
On Wed, 22 Jan 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Try to make the display VT-d workarounds more robust.
Okay, so I didn't hunt all the details in bspec, and I'm not sure if
anyone's going to, so I'm just going to trust you. Everything else
checks out and makes sense.
Series is
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Ville Syrjälä (5):
> drm/i915: Move VT-d alignment into plane->min_alignment()
> drm/i915: Use more optimal VTd alignment for planes
> drm/i915: Calculate the VT-d guard size in the display code
> drm/i915: Use per-plane VT-d guard numbers
> drm/i915/fbdev: Use fb->normal_view.gtt
>
> drivers/gpu/drm/i915/display/i9xx_plane.c | 15 ++++++
> drivers/gpu/drm/i915/display/intel_cursor.c | 8 ++++
> .../drm/i915/display/intel_display_types.h | 2 +
> drivers/gpu/drm/i915/display/intel_fb.c | 48 +++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_fb.h | 3 ++
> drivers/gpu/drm/i915/display/intel_fb_pin.c | 20 ++++----
> drivers/gpu/drm/i915/display/intel_fb_pin.h | 1 +
> drivers/gpu/drm/i915/display/intel_fbdev.c | 7 ++-
> drivers/gpu/drm/i915/display/intel_overlay.c | 2 +-
> drivers/gpu/drm/i915/display/intel_sprite.c | 15 ++++++
> .../drm/i915/display/skl_universal_plane.c | 7 +++
> drivers/gpu/drm/i915/gem/i915_gem_domain.c | 15 ++----
> drivers/gpu/drm/i915/gem/i915_gem_object.h | 2 +-
> drivers/gpu/drm/xe/display/xe_fb_pin.c | 1 +
> drivers/gpu/drm/xe/display/xe_plane_initial.c | 2 +-
> 15 files changed, 120 insertions(+), 28 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-02-04 11:25 UTC|newest]
Thread overview: 20+ 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ä
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:49 ` ✓ CI.Patch_applied: success for drm/i915: Improve the display VT-d workarounds Patchwork
2025-01-22 15:49 ` ✓ CI.checkpatch: " Patchwork
2025-01-22 15:50 ` ✓ CI.KUnit: " 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-02-04 11:25 ` Jani Nikula [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=87pljy54v1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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