From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gtt: reduce overzealous alignment constraints for GGTT
Date: Tue, 8 Mar 2022 14:02:04 +0100 [thread overview]
Message-ID: <42e30a3e-1724-df69-4530-383ee4f215f5@linux.intel.com> (raw)
In-Reply-To: <20220303100229.839282-1-matthew.auld@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
|Acked-by: Nirmoy Das <nirmoy.das@intel.com>|
On 03/03/2022 11:02, Matthew Auld wrote:
> Currently this will enforce both 2M alignment and padding for any LMEM
> pages inserted into the GGTT. However, this was only meant to be applied
> to the compact-pt layout with the ppGTT. For the GGTT we can reduce the
> alignment and padding to 64K.
>
> Bspec: 45015
> Fixes: 87bd701ee268 ("drm/i915: enforce min GTT alignment for discrete cards")
> Signed-off-by: Matthew Auld<matthew.auld@intel.com>
> Cc: Thomas Hellström<thomas.hellstrom@linux.intel.com>
> Cc: Robert Beckett<bob.beckett@collabora.com>
> Cc: Ramalingam C<ramalingam.c@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gtt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gtt.c b/drivers/gpu/drm/i915/gt/intel_gtt.c
> index 4bcdfcab3642..a5f5b2dda332 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gtt.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gtt.c
> @@ -234,7 +234,8 @@ void i915_address_space_init(struct i915_address_space *vm, int subclass)
> memset64(vm->min_alignment, I915_GTT_MIN_ALIGNMENT,
> ARRAY_SIZE(vm->min_alignment));
>
> - if (HAS_64K_PAGES(vm->i915) && NEEDS_COMPACT_PT(vm->i915)) {
> + if (HAS_64K_PAGES(vm->i915) && NEEDS_COMPACT_PT(vm->i915) &&
> + subclass == VM_CLASS_PPGTT) {
> vm->min_alignment[INTEL_MEMORY_LOCAL] = I915_GTT_PAGE_SIZE_2M;
> vm->min_alignment[INTEL_MEMORY_STOLEN_LOCAL] = I915_GTT_PAGE_SIZE_2M;
> } else if (HAS_64K_PAGES(vm->i915)) {
[-- Attachment #2: Type: text/html, Size: 2419 bytes --]
next prev parent reply other threads:[~2022-03-08 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 10:02 [Intel-gfx] [PATCH] drm/i915/gtt: reduce overzealous alignment constraints for GGTT Matthew Auld
2022-03-03 10:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-03 14:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-03 18:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gtt: reduce overzealous alignment constraints for GGTT (rev2) Patchwork
2022-03-04 5:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-04 17:25 ` [Intel-gfx] [PATCH] drm/i915/gtt: reduce overzealous alignment constraints for GGTT Thomas Hellström (Intel)
2022-03-07 13:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gtt: reduce overzealous alignment constraints for GGTT (rev3) Patchwork
2022-03-07 16:56 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-08 12:27 ` Matthew Auld
2022-03-08 13:02 ` Das, Nirmoy [this message]
2022-03-08 17:17 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
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=42e30a3e-1724-df69-4530-383ee4f215f5@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@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