Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Karas, Anna" <anna.karas@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Lahtinen, Joonas" <joonas.lahtinen@intel.com>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [igt-dev] [RFC 0/2] lib/xe_gpu: Introduce xe_gpu library
Date: Thu, 20 Apr 2023 20:38:45 +0000	[thread overview]
Message-ID: <e45eac2d1c40ed492887d96020d361c179706c6f.camel@intel.com> (raw)
In-Reply-To: <20230420191454.497237-1-anna.karas@intel.com>

On Thu, 2023-04-20 at 21:14 +0200, Anna Karas wrote:
> OPENS:
> 1. Lack of wedged concept in XE: @Matthew informed me that there is no
> intent to have reporting wedged device in XE. However, @Joonas believes
> that it may be useful - "it's used at least in specific diagnostics and
> hardware repair flows for PVC and FLR for all platforms, where we
> prevent further accesses to the hardware. So an alternative mechanism is
> needed for those". Since xe_require_gpu() is a direct port of i915's 
> igt_require_gem() stripped of wedged device reporting, this could be a
> good opportunity to discuss this.

I guess you could create a Xe engine, submit NOPs and check for XE_ENGINE_GET_PROPERTY_BAN to detect if GPU is wedged.

> 
> 2. igt_require_gem() was also responsible for restoring reset and
> enable_hangcheck modparams. Do we need those parameters here? Do/will we
> need different ones do restore?
> 
> 3. Would you find adding equivalent of gem_quiescent_gpu here worth?
> 
> Reference: Jira VLK-46235
> Signed-off-by: Anna Karas <anna.karas@intel.com>
> 
> Anna Karas (2):
>   lib/xe_gpu: Introduce xe_gpu library
>   tests/xe: Use xe_require_gpu() in existing tests
> 
>  lib/meson.build                 |   1 +
>  lib/xe/xe_gpu.c                 | 136 ++++++++++++++++++++++++++++++++
>  lib/xe/xe_gpu.h                 |  19 +++++
>  tests/xe/xe_compute.c           |   2 +
>  tests/xe/xe_create.c            |   2 +
>  tests/xe/xe_debugfs.c           |   2 +
>  tests/xe/xe_dma_buf_sync.c      |   2 +
>  tests/xe/xe_evict.c             |   2 +
>  tests/xe/xe_exec_balancer.c     |   2 +
>  tests/xe/xe_exec_basic.c        |   2 +
>  tests/xe/xe_exec_compute_mode.c |   2 +
>  tests/xe/xe_exec_fault_mode.c   |   2 +
>  tests/xe/xe_exec_reset.c        |   2 +
>  tests/xe/xe_exec_threads.c      |   2 +
>  tests/xe/xe_guc_pc.c            |   2 +
>  tests/xe/xe_huc_copy.c          |   2 +
>  tests/xe/xe_mmap.c              |   2 +
>  tests/xe/xe_mmio.c              |   2 +
>  tests/xe/xe_noexec_ping_pong.c  |   2 +
>  tests/xe/xe_pm.c                |   2 +
>  tests/xe/xe_prime_self_import.c |   2 +
>  tests/xe/xe_query.c             |   2 +
>  tests/xe/xe_vm.c                |   2 +
>  tests/xe/xe_waitfence.c         |   2 +
>  24 files changed, 198 insertions(+)
>  create mode 100644 lib/xe/xe_gpu.c
>  create mode 100644 lib/xe/xe_gpu.h
> 


  parent reply	other threads:[~2023-04-20 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 19:14 [igt-dev] [RFC 0/2] lib/xe_gpu: Introduce xe_gpu library Anna Karas
2023-04-20 19:14 ` [igt-dev] [RFC 1/2] " Anna Karas
2023-04-21  7:56   ` Zbigniew Kempczyński
2023-05-15  9:51   ` Manszewski, Christoph
2023-05-15 18:01     ` Karas, Anna
2023-04-20 19:14 ` [igt-dev] [RFC 2/2] tests/xe: Use xe_require_gpu() in existing tests Anna Karas
2023-04-20 20:38 ` Souza, Jose [this message]
2023-04-24 11:38   ` [igt-dev] [RFC 0/2] lib/xe_gpu: Introduce xe_gpu library Karas, Anna
2023-04-25  3:41     ` Zbigniew Kempczyński
2023-04-20 20:58 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-21  5:28 ` [igt-dev] ✓ Fi.CI.IGT: " 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=e45eac2d1c40ed492887d96020d361c179706c6f.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=anna.karas@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=joonas.lahtinen@intel.com \
    --cc=maarten.lankhorst@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