From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v1 1/1] drm/xe/guc: Prevent GuC register capture running on VF
Date: Mon, 21 Oct 2024 18:27:07 +0000 [thread overview]
Message-ID: <92a1772edbc8c772d45b8821b8a9df15ac6bc3e4.camel@intel.com> (raw)
In-Reply-To: <20241018224325.130754-2-zhanjun.dong@intel.com>
Straight forward - LGTM:
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
On Fri, 2024-10-18 at 15:43 -0700, Zhanjun Dong wrote:
> GuC based register capture is not supported by VF, thus prevent it
> running on VF.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_capture.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2024-10-21 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 22:43 [PATCH v1 0/1] drm/xe/guc: Prevent GuC register capture running on VF Zhanjun Dong
2024-10-18 22:43 ` [PATCH v1 1/1] " Zhanjun Dong
2024-10-21 18:27 ` Teres Alexis, Alan Previn [this message]
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
2024-10-18 22:43 ` [PATCH v1 1/1] " 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=92a1772edbc8c772d45b8821b8a9df15ac6bc3e4.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=zhanjun.dong@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