From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Lis, Tomasz" <tomasz.lis@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/xe/vf: Introduce helpers to access GGTT configuration
Date: Tue, 3 Jun 2025 12:28:16 +0200 [thread overview]
Message-ID: <bf2aeade-2686-4f24-9fc8-e10d99ce1357@intel.com> (raw)
In-Reply-To: <c37bdcfa-f5a1-4493-8f83-037e7895bc1d@intel.com>
On 03.06.2025 01:32, Lis, Tomasz wrote:
>
> On 02.06.2025 12:33, Michal Wajdeczko wrote:
>> In upcoming patch we want to separate tile-oriented VF functions
>> from GT-oriented functions and to allow the former access a GGTT
>> configuration stored at GT level we need to provide some helpers.
>>
>> Signed-off-by: Michal Wajdeczko<michal.wajdeczko@intel.com>
>> Cc: Tomasz Lis<tomasz.lis@intel.com>
>
> We're not changing `xe_gt_sriov_vf_balloon_ggtt_locked()` to use the new
> getters,
>
> instead we're making the change when moving the function to
> `xe_tile_sriov_vf_balloon_ggtt_locked()`
>
> in the next patch. No problem with that. So:
well, initially considered doing that, but since old function was still
gt-based, it was ok for it to access gt.sriov.vf.config data as other gt
functions do
>
> Reviewed-by: Tomasz Lis<tomasz.lis@intel.com>
thanks!
>
> -Tomasz
>
>> ---
>> drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 34 +++++++++++++++++++++++++++++
>> drivers/gpu/drm/xe/xe_gt_sriov_vf.h | 5 ++++-
>> 2 files changed, 38 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c b/drivers/gpu/drm/xe/
>> xe_gt_sriov_vf.c
>> index 4ff7ae1a5f16..acfb3b1b0832 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
>> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
>> @@ -561,6 +561,40 @@ u64 xe_gt_sriov_vf_lmem(struct xe_gt *gt)
>> return gt->sriov.vf.self_config.lmem_size;
>> }
>> +/**
>> + * xe_gt_sriov_vf_ggtt - VF GGTT configuration.
>> + * @gt: the &xe_gt
>> + *
>> + * This function is for VF use only.
>> + *
>> + * Return: size of the GGTT assigned to VF.
>> + */
>> +u64 xe_gt_sriov_vf_ggtt(struct xe_gt *gt)
>> +{
>> + xe_gt_assert(gt, IS_SRIOV_VF(gt_to_xe(gt)));
>> + xe_gt_assert(gt, gt->sriov.vf.guc_version.major);
>> + xe_gt_assert(gt, gt->sriov.vf.self_config.ggtt_size);
>> +
>> + return gt->sriov.vf.self_config.ggtt_size;
>> +}
>> +
>> +/**
>> + * xe_gt_sriov_vf_ggtt_base - VF GGTT base offset.
>> + * @gt: the &xe_gt
>> + *
>> + * This function is for VF use only.
>> + *
>> + * Return: base offset of the GGTT assigned to VF.
>> + */
>> +u64 xe_gt_sriov_vf_ggtt_base(struct xe_gt *gt)
>> +{
>> + xe_gt_assert(gt, IS_SRIOV_VF(gt_to_xe(gt)));
>> + xe_gt_assert(gt, gt->sriov.vf.guc_version.major);
>> + xe_gt_assert(gt, gt->sriov.vf.self_config.ggtt_size);
>> +
>> + return gt->sriov.vf.self_config.ggtt_base;
>> +}
>> +
>> /**
>> * xe_gt_sriov_vf_ggtt_shift - Return shift in GGTT range due to VF
>> migration
>> * @gt: the &xe_gt struct instance
>> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_vf.h b/drivers/gpu/drm/xe/
>> xe_gt_sriov_vf.h
>> index 9db41afddd5a..2f96ac0c5dca 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_sriov_vf.h
>> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_vf.h
>> @@ -20,7 +20,6 @@ int xe_gt_sriov_vf_query_runtime(struct xe_gt *gt);
>> int xe_gt_sriov_vf_prepare_ggtt(struct xe_gt *gt);
>> int xe_gt_sriov_vf_balloon_ggtt_locked(struct xe_gt *gt);
>> void xe_gt_sriov_vf_deballoon_ggtt_locked(struct xe_gt *gt);
>> -s64 xe_gt_sriov_vf_ggtt_shift(struct xe_gt *gt);
>> void xe_gt_sriov_vf_fixup_ggtt_nodes(struct xe_gt *gt, s64 shift);
>> int xe_gt_sriov_vf_notify_resfix_done(struct xe_gt *gt);
>> void xe_gt_sriov_vf_migrated_event_handler(struct xe_gt *gt);
>> @@ -28,6 +27,10 @@ void xe_gt_sriov_vf_migrated_event_handler(struct
>> xe_gt *gt);
>> u32 xe_gt_sriov_vf_gmdid(struct xe_gt *gt);
>> u16 xe_gt_sriov_vf_guc_ids(struct xe_gt *gt);
>> u64 xe_gt_sriov_vf_lmem(struct xe_gt *gt);
>> +u64 xe_gt_sriov_vf_ggtt(struct xe_gt *gt);
>> +u64 xe_gt_sriov_vf_ggtt_base(struct xe_gt *gt);
>> +s64 xe_gt_sriov_vf_ggtt_shift(struct xe_gt *gt);
>> +
>> u32 xe_gt_sriov_vf_read32(struct xe_gt *gt, struct xe_reg reg);
>> void xe_gt_sriov_vf_write32(struct xe_gt *gt, struct xe_reg reg, u32
>> val);
>>
next prev parent reply other threads:[~2025-06-03 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 10:33 [PATCH 0/3] VF: Small updates around GGTT handling Michal Wajdeczko
2025-06-02 10:33 ` [PATCH 1/3] drm/xe/vf: Introduce helpers to access GGTT configuration Michal Wajdeczko
2025-06-02 23:32 ` Lis, Tomasz
2025-06-03 10:28 ` Michal Wajdeczko [this message]
2025-06-04 9:36 ` Maarten Lankhorst
2025-06-04 12:10 ` Michal Wajdeczko
2025-06-02 10:33 ` [PATCH 2/3] drm/xe/vf: Move tile-related VF functions to separate file Michal Wajdeczko
2025-06-02 23:32 ` Lis, Tomasz
2025-06-03 10:33 ` Michal Wajdeczko
2025-06-02 10:33 ` [PATCH 3/3] drm/xe/vf: Add sanity check for GGTT configuration Michal Wajdeczko
2025-06-02 14:09 ` K V P, Satyanarayana
2025-06-02 10:38 ` ✓ CI.Patch_applied: success for VF: Small updates around GGTT handling Patchwork
2025-06-02 10:39 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-02 10:40 ` ✓ CI.KUnit: success " Patchwork
2025-06-02 10:50 ` ✓ CI.Build: " Patchwork
2025-06-02 10:53 ` ✓ CI.Hooks: " Patchwork
2025-06-02 10:54 ` ✓ CI.checksparse: " Patchwork
2025-06-02 11:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-02 16:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-02 17:32 ` 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=bf2aeade-2686-4f24-9fc8-e10d99ce1357@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tomasz.lis@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