From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Antonio Argenziano <antonio.argenziano@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/gem_exec_faulting_reloc: Use a coherent mapping
Date: Fri, 31 Jan 2020 19:55:49 -0800 [thread overview]
Message-ID: <878sln55bu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20200201001135.10927-1-antonio.argenziano@intel.com>
On Fri, 31 Jan 2020 16:11:35 -0800, Antonio Argenziano wrote:
>
> With mappable aperture not being available on some platforms, use a
> different mapping. While this is changing a portion of the test, it
> should keep intact the spirit of the same by submitting relocations to
> faulting addresses.
Apart from the nit's on the comments below:
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Signed-off-by: Antonio Argenziano <antonio.argenziano@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> tests/i915/gem_exec_faulting_reloc.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/tests/i915/gem_exec_faulting_reloc.c b/tests/i915/gem_exec_faulting_reloc.c
> index c2aea039..82d67a68 100644
> --- a/tests/i915/gem_exec_faulting_reloc.c
> +++ b/tests/i915/gem_exec_faulting_reloc.c
> @@ -39,12 +39,11 @@
> #include <sys/time.h>
> #include "drm.h"
>
> -/* Testcase: Submit patches with relocations in memory that will fault
> +/* Testcase: Submit batches with relocations in memory that will fault
> *
> - * To be really evil, use a gtt mmap for them.
"To be really evil, use a gtt mmap for them when available."?
> @@ -203,7 +202,7 @@ static void run(int object_size)
>
> handle_relocs = gem_create(fd, 4096);
> gem_write(fd, handle_relocs, 0, reloc, sizeof(reloc));
> - gtt_relocs = gem_mmap__gtt(fd, handle_relocs, 4096,
> + relocs = gem_mmap__device_coherent(fd, handle_relocs, 0, 4096,
> PROT_READ | PROT_WRITE);
>
> exec[2].handle = handle;
> @@ -212,7 +211,7 @@ static void run(int object_size)
> else
> exec[2].relocation_count = len > 40 ? 4 : 2;
> /* A newly mmap gtt bo will fault on first access. */
/* A newly mmap bo will fault on first access. */ ?
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-01 3:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 0:11 [igt-dev] [PATCH i-g-t] tests/i915/gem_exec_faulting_reloc: Use a coherent mapping Antonio Argenziano
2020-02-01 0:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-01 3:55 ` Dixit, Ashutosh [this message]
2020-02-03 10:34 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-02-04 19:18 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=878sln55bu.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=antonio.argenziano@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.