Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>
Subject: [PATCH v1 0/1] drm/xe/guc: Prevent GuC register capture running on VF
Date: Fri, 18 Oct 2024 15:43:24 -0700	[thread overview]
Message-ID: <20241018224325.130754-1-zhanjun.dong@intel.com> (raw)

GuC based register capture is not supported by VF, thus prevent it
running on VF.

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>

Zhanjun Dong (1):
  drm/xe/guc: Prevent GuC register capture running on VF

 drivers/gpu/drm/xe/xe_guc_capture.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-10-18 22:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 22:43 Zhanjun Dong [this message]
2024-10-18 22:43 ` [PATCH v1 1/1] drm/xe/guc: Prevent GuC register capture running on VF Zhanjun Dong
2024-10-21 18:27   ` Teres Alexis, Alan Previn
2024-10-21 19:43   ` Michal Wajdeczko
2024-10-22  0:03     ` Dong, Zhanjun
2024-10-18 23:30 ` ✓ CI.Patch_applied: success for drm/xe/guc: Prevent GuC register capture running on VF (rev2) Patchwork
2024-10-18 23:31 ` ✓ CI.checkpatch: " Patchwork
2024-10-18 23:32 ` ✓ CI.KUnit: " Patchwork
2024-10-18 23:50 ` ✓ CI.Build: " Patchwork
2024-10-18 23:53 ` ✓ CI.Hooks: " Patchwork
2024-10-18 23:54 ` ✓ CI.checksparse: " Patchwork
2024-10-19  0:30 ` ✓ CI.BAT: " Patchwork
2024-10-19 18:07 ` ✗ CI.FULL: failure " Patchwork
2024-10-21 19:14   ` Dong, Zhanjun
  -- strict thread matches above, loose matches on Subject: below --
2024-10-18 22:43 [PATCH v1 0/1] drm/xe/guc: Prevent GuC register capture running on VF Zhanjun Dong

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=20241018224325.130754-1-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@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