From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Zhanjun Dong <zhanjun.dong@intel.com>,
Alan Previn <alan.previn.teres.alexis@intel.com>,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH v2 0/1] drm/xe/guc: Prevent GuC register capture running on VF
Date: Mon, 21 Oct 2024 18:01:15 -0700 [thread overview]
Message-ID: <20241022010116.342240-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>
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Changes from prior revs:
v2:- Remove 2 unnecessary SRIOV check
Zhanjun Dong (1):
drm/xe/guc: Prevent GuC register capture running on VF
drivers/gpu/drm/xe/xe_guc_capture.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2024-10-22 1:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 1:01 Zhanjun Dong [this message]
2024-10-22 1:01 ` [PATCH v2 1/1] drm/xe/guc: Prevent GuC register capture running on VF Zhanjun Dong
2024-10-22 9:32 ` Michal Wajdeczko
2024-10-22 1:06 ` ✓ CI.Patch_applied: success for drm/xe/guc: Prevent GuC register capture running on VF (rev3) Patchwork
2024-10-22 1:06 ` ✓ CI.checkpatch: " Patchwork
2024-10-22 1:07 ` ✓ CI.KUnit: " Patchwork
2024-10-22 1:19 ` ✓ CI.Build: " Patchwork
2024-10-22 1:21 ` ✓ CI.Hooks: " Patchwork
2024-10-22 1:22 ` ✓ CI.checksparse: " Patchwork
2024-10-22 1:47 ` ✓ CI.BAT: " Patchwork
2024-10-22 9:13 ` ✗ CI.FULL: failure " Patchwork
2024-10-22 14:55 ` Dong, Zhanjun
2024-10-22 17:05 ` Rodrigo Vivi
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=20241022010116.342240-1-zhanjun.dong@intel.com \
--to=zhanjun.dong@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@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 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.