Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Adam Miszczak <adam.miszczak@linux.intel.com>,
	Lukasz Laguna <lukasz.laguna@intel.com>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Michal Winiarski <michal.winiarski@intel.com>,
	Narasimha C V <narasimha.c.v@intel.com>,
	Piotr Piorkowski <piotr.piorkowski@intel.com>,
	Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
	Tomasz Lis <tomasz.lis@intel.com>
Subject: Re: [PATCH 2/2] drm/xe/vf: Don't apply Wa_22019338487 for VF
Date: Mon, 9 Dec 2024 10:44:42 +0100	[thread overview]
Message-ID: <d083b661-04ee-4201-8962-480a093924a2@linux.intel.com> (raw)
In-Reply-To: <20241205210436.GH3224633@mdroper-desk1.amr.corp.intel.com>



On 12/5/2024 10:04 PM, Matt Roper wrote:
> On Thu, Dec 05, 2024 at 06:18:14PM +0000, Jakub Kolakowski wrote:
>> Don't use Wa_22019338487 for VF.
> 
> Would it make sense to add some kind of "PFONLY" RTP action that can be
> applied to workaround definitions that should only apply when running on
> the PF and not on the VF?  Then we could just add that flag to this
> workaround in xe_wa_oob.rules and we wouldn't need to change the
> callsite(s) where XE_WA is invoked.
> 
> I'm not sure how common PF-only (or VF-only for that matter) workarounds
> are going to be going forward.
> 
> 
> Matt
> 

As first step I would add something like NOT VF,
that should better handle the case SR-IOV is disabled.

So adding a helper to xe_rtp.c:

bool xe_rtp_match_not_sriov_vf(const struct xe_gt *gt,
                               const struct xe_hw_engine *hwe)
{
        return !IS_SRIOV_VF(gt_to_xe(gt));
}

and updating rules:

  22019338487    MEDIA_VERSION(2000)
                 GRAPHICS_VERSION(2001)
-               MEDIA_VERSION(3000), MEDIA_STEP(A0, B0)
+               MEDIA_VERSION(3000), MEDIA_STEP(A0, B0), 
FUNC(match_not_sriov_vf)

It looks the rules on each line are ORed, so here the generated output is:

{ XE_RTP_NAME("22019338487"),
   XE_RTP_RULES(MEDIA_VERSION(2000), OR,
         GRAPHICS_VERSION(2001), OR,
         MEDIA_VERSION(3000), MEDIA_STEP(A0, B0), 
FUNC(match_not_sriov_vf)) }

--
marcin

>>
>> Signed-off-by: Jakub Kolakowski <jakub1.kolakowski@intel.com>
>> Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
>> Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
>> Cc: Lukasz Laguna <lukasz.laguna@intel.com>
>> Cc: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Michal Winiarski <michal.winiarski@intel.com>
>> Cc: Narasimha C V <narasimha.c.v@intel.com>
>> Cc: Piotr Piorkowski <piotr.piorkowski@intel.com>
>> Cc: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
>> Cc: Tomasz Lis <tomasz.lis@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_ggtt.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_ggtt.c b/drivers/gpu/drm/xe/xe_ggtt.c
>> index 05154f9de1a6..11aba2437818 100644
>> --- a/drivers/gpu/drm/xe/xe_ggtt.c
>> +++ b/drivers/gpu/drm/xe/xe_ggtt.c
>> @@ -238,7 +238,7 @@ int xe_ggtt_init_early(struct xe_ggtt *ggtt)
>>   	if (ggtt->size > GUC_GGTT_TOP)
>>   		ggtt->size = GUC_GGTT_TOP;
>>   
>> -	if (GRAPHICS_VERx100(xe) >= 1270)
>> +	if (GRAPHICS_VERx100(xe) >= 1270 && !IS_SRIOV_VF(xe))
>>   		ggtt->pt_ops = (ggtt->tile->media_gt &&
>>   			       XE_WA(ggtt->tile->media_gt, 22019338487)) ||
>>   			       XE_WA(ggtt->tile->primary_gt, 22019338487) ?
>> -- 
>> 2.25.1
>>
> 


  reply	other threads:[~2024-12-09  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 18:18 [PATCH 0/2] VF: Avoid reading inaccessible registers Jakub Kolakowski
2024-12-05 18:18 ` [PATCH 1/2] drm/xe/vf: Don't check has flat ccs in bios on VF Jakub Kolakowski
2024-12-05 21:00   ` Matt Roper
2024-12-05 18:18 ` [PATCH 2/2] drm/xe/vf: Don't apply Wa_22019338487 for VF Jakub Kolakowski
2024-12-05 21:04   ` Matt Roper
2024-12-09  9:44     ` Bernatowicz, Marcin [this message]
2024-12-09 16:47       ` Matt Roper
2024-12-05 19:39 ` ✓ CI.Patch_applied: success for VF: Avoid reading inaccessible registers Patchwork
2024-12-05 19:39 ` ✓ CI.checkpatch: " Patchwork
2024-12-05 19:40 ` ✓ CI.KUnit: " Patchwork
2024-12-05 19:58 ` ✓ CI.Build: " Patchwork
2024-12-05 20:01 ` ✓ CI.Hooks: " Patchwork
2024-12-05 20:02 ` ✓ CI.checksparse: " Patchwork
2024-12-05 20:24 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-12-05 21:57 ` ✗ Xe.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=d083b661-04ee-4201-8962-480a093924a2@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=narasimha.c.v@intel.com \
    --cc=piotr.piorkowski@intel.com \
    --cc=satyanarayana.k.v.p@intel.com \
    --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