Bug 109290

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@gem_pwrite@huge-cpu - skip - Estimated that we need \d+ objects and \d+ MiB for the test, but only have \d+ MiB available \(RAM\) and a maximum of ...
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb2/igt@gem_pwrite@huge-cpu-fbr.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb5/igt@gem_pwrite@huge-cpu-forwards.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_pwrite@huge-cpu-random.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_pwrite@huge-cpu-backwards.html

A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@gem_pwrite@huge-cpu - skip - Estimated that we need \d+ objects and \d+ MiB for the test, but only have \d+ MiB available \(RAM\) and a maximum of ... -}
{+ ICL: igt@gem_pwrite@huge-* - skip - Estimated that we need \d+ objects and \d+ MiB for the test, but only have \d+ MiB available \(RAM\) and a maximum of ... +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb2/igt@gem_pwrite@huge-gtt-backwards.html
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb2/igt@gem_pwrite@huge-gtt-random.html
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_pwrite@huge-gtt-forwards.html
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_pwrite@huge-gtt-fbr.html

Nah. Give me a machine with 49-bits of memory and I want to test what happens if we have a full 48-bit GTT. (Not that it really matters, since the interesting GTT is the global one, mappable vs non-mappable at a stretch limits.)

A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@gem_pwrite@huge-* - skip - Estimated that we need \d+ objects and \d+ MiB for the test, but only have \d+ MiB available \(RAM\) and a maximum of ... -}
{+ ICL: igt@* - skip - Estimated that we need \d+ objects and \d+ MiB for the test, but only have \d+ MiB available \(RAM\) and a maximum of ... +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb5/igt@gem_exec_big.html
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_userptr_blits@coherency-sync.html
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5388/shard-iclb6/igt@gem_userptr_blits@coherency-unsync.html

(In reply to Chris Wilson from comment #3)
> Nah. Give me a machine with 49-bits of memory and I want to test what
> happens if we have a full 48-bit GTT. (Not that it really matters, since the
> interesting GTT is the global one, mappable vs non-mappable at a stretch
> limits.)

Hehe :p

Separate tests for the inspection around the more likely breakpoints of mappable and non-mappable.

(In reply to Chris Wilson from comment #6)
> Separate tests for the inspection around the more likely breakpoints of
> mappable and non-mappable.

Do you want to write the test yourself or should we add it to Francesco's todo list? If the latter, please Cc: him about it for him to create a task :)