From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/9] drm/xe/pf: Use migration-friendly VRAM auto-provisioning
Date: Mon, 16 Feb 2026 17:14:18 +0100 [thread overview]
Message-ID: <20260216161418.grmul6n3t4voclia@intel.com> (raw)
In-Reply-To: <20260215203323.595-5-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on nie [2026-lut-15 21:33:18 +0100]:
> Instead of trying very hard to find the largest fair VRAM (aka LMEM)
> size that could be allocated for VFs on the current tile, pick some
> smaller rounded down to power-of-two value that is more likely to be
> provisioned in the same manner by the other PF instances.
>
> In some cases, the outcome of above calculation might not be optimal,
> but it's expected that admin will do fine-tuning using sysfs files.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c | 27 ++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> index 23af49dc1bfa..43041af81518 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_config.c
> @@ -1919,6 +1919,26 @@ static u64 pf_estimate_fair_lmem(struct xe_gt *gt, unsigned int num_vfs)
> return fair;
> }
>
> +static u64 pf_profile_fair_lmem(struct xe_gt *gt, unsigned int num_vfs)
> +{
> + struct xe_tile *tile = gt_to_tile(gt);
> + bool admin_only_pf = xe_sriov_pf_admin_only(tile->xe);
> + u64 usable = xe_vram_region_usable_size(tile->mem.vram);
> + u64 shareable = ALIGN_DOWN(usable, SZ_1G);
> + u64 alignment = pf_get_lmem_alignment(gt);
> + u64 fair;
> +
> + if (admin_only_pf)
> + fair = div_u64(shareable, num_vfs);
> + else
> + fair = div_u64(shareable, 1 + num_vfs);
> +
> + if (!admin_only_pf && fair)
> + fair = rounddown_pow_of_two(fair);
> +
> + return ALIGN_DOWN(fair, alignment);
I would add a hard guarantee that for admin_only_pf, PF will not be left without a minimum
amount of VRAM.
Currently, under certain conditions, it may run out of VRAM - although this is unlikely.
I have already discussed this with Michal offline and I am leaving it up to him to decide
what to do about it.
> +}
> +
> /**
> * xe_gt_sriov_pf_config_set_fair_lmem - Provision many VFs with fair LMEM.
> * @gt: the &xe_gt (can't be media)
> @@ -1932,6 +1952,7 @@ static u64 pf_estimate_fair_lmem(struct xe_gt *gt, unsigned int num_vfs)
> int xe_gt_sriov_pf_config_set_fair_lmem(struct xe_gt *gt, unsigned int vfid,
> unsigned int num_vfs)
> {
> + u64 profile;
> u64 fair;
>
> xe_gt_assert(gt, vfid);
> @@ -1948,6 +1969,12 @@ int xe_gt_sriov_pf_config_set_fair_lmem(struct xe_gt *gt, unsigned int vfid,
> if (!fair)
> return -ENOSPC;
>
> + profile = pf_profile_fair_lmem(gt, num_vfs);
> + fair = min(fair, profile);
> + if (fair < profile)
> + xe_gt_sriov_info(gt, "Using non-profile provisioning (%s %llu vs %llu)\n",
> + "VRAM", fair, profile);
> +
> return xe_gt_sriov_pf_config_bulk_set_lmem(gt, vfid, num_vfs, fair);
> }
>
Apart from what I mentioned earlier, the code is fine for me,
In the worst case (highly unlikely), provisioning will just fail.
So still:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> --
> 2.47.1
>
--
next prev parent reply other threads:[~2026-02-16 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 20:33 [PATCH 0/9] drm/xe/pf: Allow to change VFs VRAM quota using sysfs Michal Wajdeczko
2026-02-15 20:33 ` [PATCH 1/9] drm/xe/pf: Add locked variants of VRAM configuration functions Michal Wajdeczko
2026-02-16 14:37 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 2/9] drm/xe/pf: Add functions for VRAM provisioning Michal Wajdeczko
2026-02-16 15:02 ` Piotr Piórkowski
2026-02-16 15:11 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 3/9] drm/xe/pf: Allow to change VFs VRAM quota using sysfs Michal Wajdeczko
2026-02-16 15:29 ` Piotr Piórkowski
2026-02-18 21:07 ` Rodrigo Vivi
2026-02-15 20:33 ` [PATCH 4/9] drm/xe/pf: Use migration-friendly VRAM auto-provisioning Michal Wajdeczko
2026-02-16 16:14 ` Piotr Piórkowski [this message]
2026-02-15 20:33 ` [PATCH 5/9] drm/xe/tests: Add KUnit tests for new VRAM fair provisioning Michal Wajdeczko
2026-02-16 16:23 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 6/9] drm/xe/pf: Don't check for empty config Michal Wajdeczko
2026-02-16 16:27 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 7/9] drm/xe/pf: Prefer guard(mutex) when doing fair LMEM provisioning Michal Wajdeczko
2026-02-16 16:36 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 8/9] drm/xe/pf: Skip VRAM auto-provisioning if already provisioned Michal Wajdeczko
2026-02-16 16:59 ` Piotr Piórkowski
2026-02-15 20:33 ` [PATCH 9/9] drm/xe/pf: Add documentation for vram_quota Michal Wajdeczko
2026-02-16 17:04 ` Piotr Piórkowski
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=20260216161418.grmul6n3t4voclia@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