From: Ramalingam C <ramalingam.c@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [CI 3/4] drm/i915/selftests: fixup min_alignment usage
Date: Thu, 21 Apr 2022 14:02:14 +0530 [thread overview]
Message-ID: <20220421083214.GC18679@intel.com> (raw)
In-Reply-To: <20220420181613.70033-3-matthew.auld@intel.com>
On 2022-04-20 at 19:16:12 +0100, Matthew Auld wrote:
> Trying to cast the region id into the region type doesn't work too well,
> since the i915_vm_min_alignment() won't give us the correct value for
> the stolen-lmem case.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
> Cc: Ramalingam C <ramalingam.c@intel.com>
> ---
> drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> index 5c9bfa409ff5..bccc49a8ab5e 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_gem_gtt.c
> @@ -1150,7 +1150,7 @@ static int misaligned_pin(struct i915_address_space *vm,
> flags |= PIN_GLOBAL;
>
> for_each_memory_region(mr, vm->i915, id) {
> - u64 min_alignment = i915_vm_min_alignment(vm, (enum intel_memory_type)id);
> + u64 min_alignment = i915_vm_min_alignment(vm, mr->type);
> u64 size = min_alignment;
> u64 addr = round_down(hole_start + (hole_size / 2), min_alignment);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-04-21 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 18:16 [Intel-gfx] [CI 1/4] drm/i915: consider min_page_size when migrating Matthew Auld
2022-04-20 18:16 ` [Intel-gfx] [CI 2/4] drm/i915/buddy: sanity check the size Matthew Auld
2022-04-20 18:16 ` [Intel-gfx] [CI 3/4] drm/i915/selftests: fixup min_alignment usage Matthew Auld
2022-04-21 8:32 ` Ramalingam C [this message]
2022-04-20 18:16 ` [Intel-gfx] [CI 4/4] drm/i915/selftests: tweak the misaligned_case Matthew Auld
2022-04-21 8:46 ` Ramalingam C
2022-04-20 22:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/4] drm/i915: consider min_page_size when migrating Patchwork
2022-04-21 1:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-21 8:25 ` Matthew Auld
2022-04-25 16:05 ` [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=20220421083214.GC18679@intel.com \
--to=ramalingam.c@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