From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/prime_self_import: Swap gtt mapping for cpu
Date: Fri, 22 Feb 2019 09:19:15 -0800 [thread overview]
Message-ID: <1e07fb2f-a266-66be-3d2d-833abaa19b88@intel.com> (raw)
In-Reply-To: <155085453789.4937.11051023274884383159@skylake-alporthouse-com>
On 22/02/19 08:55, Chris Wilson wrote:
> Quoting Antonio Argenziano (2019-02-22 16:50:07)
>>
>>
>> On 21/02/19 15:37, Chris Wilson wrote:
>>> Quoting Antonio Argenziano (2019-02-21 22:38:59)
>>>> The test uses gtt mapping to check two BOs have the same content, since
>>>> it seems there is no contention on the BOs use cpu mapping to make it
>>>> compatible with platforms that do not have a mappable aperture.
>>>>
>>>> v2:
>>>> - Need to have an explicit set_domain. (Chris)
>>>>
>>>> Signed-off-by: Antonio Argenziano <antonio.argenziano@intel.com>
>>>
>>> I don't think has any semantic impact, so no need to verify every write
>>> to one of the cloned fd is visible in the other, just once is enough.
>>
>> Keep only one set_domain then?
>
> No, I was talking about whether we needed to do this for all the
> different mmap paths, and decided that we aren't doing any coherency
> checks just verifying that we had one objects.
>
> Whether to use one or two set-domain here is an interesting question
> relating to how much we want to assume we only have a single bo here
> (which is the object of the exercise ofc). I think I favour keeping it
> as two distinct handles with the test being only that the memory
> contents are the same. Otherwise we might as well just use one handle ;)
>
>> Any objections to splitting this from the series and merge?
>
> This can be applied right away.
Pushed, thanks for the review.
Antonio
> -Chris
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-22 17:19 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 19:27 [igt-dev] [RFC 0/5] Modify tests for unavailable mappable aperture Antonio Argenziano
2019-02-21 19:27 ` [igt-dev] [RFC 1/5] tests/prime_self_import: Swap gtt mapping for cpu Antonio Argenziano
2019-02-21 19:46 ` Chris Wilson
2019-02-21 21:51 ` Antonio Argenziano
2019-02-21 22:08 ` Chris Wilson
2019-02-21 22:38 ` [igt-dev] [PATCH i-g-t] " Antonio Argenziano
2019-02-21 23:37 ` Chris Wilson
2019-02-22 16:50 ` Antonio Argenziano
2019-02-22 16:55 ` Chris Wilson
2019-02-22 17:19 ` Antonio Argenziano [this message]
2019-02-21 19:27 ` [igt-dev] [RFC 2/5] lib/ioctl_wrappers: add mmap_offset support Antonio Argenziano
2019-02-21 19:47 ` Chris Wilson
2019-02-21 21:13 ` Antonio Argenziano
2019-02-21 21:19 ` Chris Wilson
2019-02-22 21:59 ` [igt-dev] [PATCH i-g-t] lib/i915: " Antonio Argenziano
2019-02-22 22:01 ` Antonio Argenziano
2019-02-22 22:13 ` Chris Wilson
2019-02-22 22:29 ` Chris Wilson
2019-02-22 22:44 ` Antonio Argenziano
2019-02-25 18:28 ` [igt-dev] [PATCH i-g-t v3 1/2] " Antonio Argenziano
2019-02-25 18:28 ` [igt-dev] [PATCH i-g-t v3 2/2] tests/i915/gem_mmap_wc: Add local MMAP wrapper Antonio Argenziano
2019-02-25 22:24 ` Chris Wilson
2019-02-25 22:33 ` Antonio Argenziano
2019-02-25 22:46 ` [igt-dev] [PATCH i-g-t v3 1/2] lib/i915: add mmap_offset support Chris Wilson
2019-02-21 19:27 ` [igt-dev] [RFC 3/5] igt/lib: Add wrapper to check if gtt mapping is available Antonio Argenziano
2019-02-21 19:49 ` Chris Wilson
2019-02-21 21:37 ` Antonio Argenziano
2019-02-21 21:54 ` Chris Wilson
2019-02-22 22:20 ` [igt-dev] [PATCH i-g-t v2] " Antonio Argenziano
2019-02-21 19:27 ` [igt-dev] [RFC 4/5] igt/i915: Require GTT mapping to be available when needed Antonio Argenziano
2019-02-21 19:57 ` Chris Wilson
2019-02-23 0:01 ` Antonio Argenziano
2019-02-23 0:17 ` Chris Wilson
2019-04-09 0:12 ` Vanshidhar Konda
2019-02-21 19:27 ` [igt-dev] [RFC 5/5] igt/lib: If mappable aperture is missing return 0 size Antonio Argenziano
2019-02-21 20:01 ` Chris Wilson
2019-02-21 21:45 ` Antonio Argenziano
2019-02-21 21:51 ` Chris Wilson
2019-03-07 15:51 ` Antonio Argenziano
2019-03-07 15:58 ` Chris Wilson
2019-03-07 16:29 ` Antonio Argenziano
2019-03-07 16:45 ` Chris Wilson
2019-03-07 16:50 ` Chris Wilson
2019-03-07 17:03 ` Antonio Argenziano
2019-02-21 20:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Modify tests for unavailable mappable aperture Patchwork
2019-02-21 23:24 ` [igt-dev] ✓ Fi.CI.BAT: success for Modify tests for unavailable mappable aperture (rev2) Patchwork
2019-02-22 8:04 ` [igt-dev] ✓ Fi.CI.IGT: success for Modify tests for unavailable mappable aperture Patchwork
2019-02-22 12:26 ` [igt-dev] ✓ Fi.CI.IGT: success for Modify tests for unavailable mappable aperture (rev2) Patchwork
2019-02-22 22:10 ` [igt-dev] ✗ Fi.CI.BAT: failure for Modify tests for unavailable mappable aperture (rev3) Patchwork
2019-02-22 22:30 ` [igt-dev] ✗ Fi.CI.BAT: failure for Modify tests for unavailable mappable aperture (rev4) Patchwork
2019-02-25 18:37 ` [igt-dev] ✗ Fi.CI.BAT: failure for Modify tests for unavailable mappable aperture (rev6) 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=1e07fb2f-a266-66be-3d2d-833abaa19b88@intel.com \
--to=antonio.argenziano@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox