All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Arjun Melkaveri <arjun.melkaveri@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/gem_bad_reloc: Added check for verifying aperture support
Date: Tue, 12 Oct 2021 17:44:42 -0700	[thread overview]
Message-ID: <871r4pkb2d.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211011071332.18492-1-arjun.melkaveri@intel.com>

On Mon, 11 Oct 2021 00:13:32 -0700, Arjun Melkaveri wrote:
>
> Added check for verifying aperture support.
> "negative_reloc" subtest  uses gtt address spaze size

This is calling gem_aperture_size() which is a I915_CONTEXT_PARAM_GTT_SIZE
which seems to be the per context VM size not the GGTT size. Look at the
i915 code.

> and "negative_reloc_blt" uses fences, which needs aperture support.

This again looks like fences will only be used if the object is tiled which
doesn't seem to be in this case?

> This would avoid test failure for platfom that doesnt support this.

Where are we saying failures? Is there a bug?

> diff --git a/tests/i915/gem_bad_reloc.c b/tests/i915/gem_bad_reloc.c
> index 3ca0f345..d0902e6c 100644
> --- a/tests/i915/gem_bad_reloc.c
> +++ b/tests/i915/gem_bad_reloc.c
> @@ -195,6 +195,7 @@ igt_main
>		/* Check if relocations supported by platform */
>		igt_require(gem_has_relocations(fd));
>		gem_require_blitter(fd);
> +		gem_require_mappable_ggtt(fd);

      parent reply	other threads:[~2021-10-13  0:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  7:13 [igt-dev] [PATCH i-g-t] tests/i915/gem_bad_reloc: Added check for verifying aperture support Arjun Melkaveri
2021-10-11  8:14 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-11 10:02 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-10-13  0:44 ` Dixit, Ashutosh [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=871r4pkb2d.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=arjun.melkaveri@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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.