From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Subject: Re: [PATCH 3/5] drm/xe/vf: Drop IS_VF_CCS_INIT_NEEDED macro
Date: Thu, 4 Sep 2025 20:27:59 -0700 [thread overview]
Message-ID: <aLpYv8usHFC/dE0N@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250904192918.7346-4-michal.wajdeczko@intel.com>
On Thu, Sep 04, 2025 at 09:29:15PM +0200, Michal Wajdeczko wrote:
> We only use this macro once and we can open-code it to explicitly
> show relevant conditions and avoid duplications.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_sriov_vf_ccs.c | 6 +++++-
> drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h | 6 ------
> 2 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf_ccs.c b/drivers/gpu/drm/xe/xe_sriov_vf_ccs.c
> index 19786f64a7da..b01bb3660fb1 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf_ccs.c
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf_ccs.c
> @@ -15,6 +15,7 @@
> #include "xe_migrate.h"
> #include "xe_sa.h"
> #include "xe_sriov_printk.h"
> +#include "xe_sriov_vf.h"
> #include "xe_sriov_vf_ccs.h"
> #include "xe_sriov_vf_ccs_types.h"
>
> @@ -263,7 +264,10 @@ int xe_sriov_vf_ccs_init(struct xe_device *xe)
> u32 flags;
> int err;
>
> - if (!IS_VF_CCS_INIT_NEEDED(xe))
> + xe_assert(xe, IS_SRIOV_VF(xe));
> + xe_assert(xe, xe_sriov_vf_migration_supported(xe));
> +
> + if (IS_DGFX(xe) || !xe_device_has_flat_ccs(xe))
> return 0;
>
> for_each_ccs_rw_ctx(ctx_id) {
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h b/drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h
> index 93435a6f4cb6..0df6b4130e7c 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf_ccs_types.h
> @@ -15,12 +15,6 @@
> ___xe->sriov.vf.ccs.initialized; \
> })
>
> -#define IS_VF_CCS_INIT_NEEDED(xe) ({\
> - struct xe_device *___xe = (xe); \
> - IS_SRIOV_VF(___xe) && !IS_DGFX(___xe) && \
> - xe_device_has_flat_ccs(___xe) && GRAPHICS_VER(___xe) >= 20; \
> - })
> -
> enum xe_sriov_vf_ccs_rw_ctxs {
> XE_SRIOV_VF_CCS_READ_CTX,
> XE_SRIOV_VF_CCS_WRITE_CTX,
> --
> 2.47.1
>
next prev parent reply other threads:[~2025-09-05 3:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 19:29 [PATCH 0/5] Small improvements around VF CCS Michal Wajdeczko
2025-09-04 19:29 ` [PATCH 1/5] drm/xe/guc: Rename xe_guc_register_exec_queue Michal Wajdeczko
2025-09-05 7:05 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 2/5] drm/xe/guc: Use proper flag definitions when registering context Michal Wajdeczko
2025-09-04 19:36 ` Matthew Brost
2025-09-04 19:29 ` [PATCH 3/5] drm/xe/vf: Drop IS_VF_CCS_INIT_NEEDED macro Michal Wajdeczko
2025-09-05 3:27 ` Matthew Brost [this message]
2025-09-05 7:18 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 4/5] drm/xe/vf: Use single check when calling VF CCS functions Michal Wajdeczko
2025-09-05 7:40 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 5/5] drm/xe/bo: Add xe_bo_has_valid_ccs_bb helper Michal Wajdeczko
2025-09-04 20:31 ` Matthew Brost
2025-09-05 7:42 ` K V P, Satyanarayana
2025-09-04 19:36 ` ✓ CI.KUnit: success for Small improvements around VF CCS Patchwork
2025-09-04 20:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-05 11:55 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-05 12:34 ` Michal Wajdeczko
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=aLpYv8usHFC/dE0N@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=satyanarayana.k.v.p@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