From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 5/6] drm/xe/vf: Custom hardware config load step if VF
Date: Thu, 16 May 2024 12:11:16 +0200 [thread overview]
Message-ID: <20240516101116.ugyoubng4e5ww3su@intel.com> (raw)
In-Reply-To: <20240512154915.2040-6-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on nie [2024-maj-12 17:49:14 +0200]:
> The VF drivers may immediately communicate with the GuC to obtain
> the hardware config since the firmware shall already be running.
>
> With the GuC communication established, VFs can also obtain the
> values of the runtime registers (fuses) from the PF driver.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 0c9938e0ab8c..762fab403b86 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -19,6 +19,7 @@
> #include "xe_force_wake.h"
> #include "xe_gt.h"
> #include "xe_gt_printk.h"
> +#include "xe_gt_sriov_vf.h"
> #include "xe_guc_ads.h"
> #include "xe_guc_ct.h"
> #include "xe_guc_hwconfig.h"
> @@ -538,6 +539,38 @@ static int __xe_guc_upload(struct xe_guc *guc)
> return 0 /* FIXME: ret, don't want to stop load currently */;
> }
>
> +static int vf_guc_min_load_for_hwconfig(struct xe_guc *guc)
> +{
> + struct xe_gt *gt = guc_to_gt(guc);
> + int ret;
> +
> + ret = xe_gt_sriov_vf_bootstrap(gt);
> + if (ret)
> + return ret;
> +
> + ret = xe_gt_sriov_vf_query_config(gt);
> + if (ret)
> + return ret;
> +
> + ret = xe_guc_hwconfig_init(guc);
> + if (ret)
> + return ret;
> +
> + ret = xe_guc_enable_communication(guc);
> + if (ret)
> + return ret;
> +
> + ret = xe_gt_sriov_vf_connect(gt);
> + if (ret)
> + return ret;
> +
> + ret = xe_gt_sriov_vf_query_runtime(gt);
> + if (ret)
> + return ret;
> +
> + return 0;
> +}
> +
> /**
> * xe_guc_min_load_for_hwconfig - load minimal GuC and read hwconfig table
> * @guc: The GuC object
> @@ -553,6 +586,9 @@ int xe_guc_min_load_for_hwconfig(struct xe_guc *guc)
> {
> int ret;
>
> + if (IS_SRIOV_VF(guc_to_xe(guc)))
> + return vf_guc_min_load_for_hwconfig(guc);
> +
> xe_guc_ads_populate_minimal(&guc->ads);
>
> /* Raise GT freq to speed up HuC/GuC load */
LGTM:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> --
> 2.43.0
>
--
next prev parent reply other threads:[~2024-05-16 10:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 15:49 [PATCH 0/6] Add support for VF to query its configuration Michal Wajdeczko
2024-05-12 15:49 ` [PATCH 1/6] drm/xe/guc: Add VF2GUC_MATCH_VERSION to ABI Michal Wajdeczko
2024-05-14 12:47 ` Piotr Piórkowski
2024-05-14 12:56 ` Piotr Piórkowski
2024-05-14 16:05 ` Michal Wajdeczko
2024-05-12 15:49 ` [PATCH 2/6] drm/xe/guc: Add VF2GUC_VF_RESET " Michal Wajdeczko
2024-05-14 12:59 ` Piotr Piórkowski
2024-05-12 15:49 ` [PATCH 3/6] drm/xe/guc: Add VF2GUC_QUERY_SINGLE_KLV " Michal Wajdeczko
2024-05-16 7:17 ` Piotr Piórkowski
2024-05-12 15:49 ` [PATCH 4/6] drm/xe/vf: Add support for VF to query its configuration Michal Wajdeczko
2024-05-16 10:08 ` Piotr Piórkowski
2024-05-16 10:26 ` Michal Wajdeczko
2024-05-12 15:49 ` [PATCH 5/6] drm/xe/vf: Custom hardware config load step if VF Michal Wajdeczko
2024-05-16 10:11 ` Piotr Piórkowski [this message]
2024-05-12 15:49 ` [PATCH 6/6] drm/xe/vf: Expose SR-IOV VF attributes to GT debugfs Michal Wajdeczko
2024-05-16 10:19 ` Piotr Piórkowski
2024-05-13 8:08 ` ✓ CI.Patch_applied: success for Add support for VF to query its configuration Patchwork
2024-05-13 8:09 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-13 8:10 ` ✓ CI.KUnit: success " Patchwork
2024-05-13 8:21 ` ✓ CI.Build: " Patchwork
2024-05-13 8:24 ` ✗ CI.Hooks: failure " Patchwork
2024-05-13 8:25 ` ✓ CI.checksparse: success " Patchwork
2024-05-13 8:47 ` ✓ CI.BAT: " Patchwork
2024-05-13 9:47 ` ✓ CI.FULL: " 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=20240516101116.ugyoubng4e5ww3su@intel.com \
--to=piotr.piorkowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox