Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lis, Tomasz" <tomasz.lis@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
	"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
	"Dnyaneshwar Bhadane" <dnyaneshwar.bhadane@intel.com>
Subject: Re: [PATCH] drm/xe/sriov: Mark NVL as SR-IOV capable
Date: Wed, 13 May 2026 02:08:51 +0200	[thread overview]
Message-ID: <827126ad-ed22-4f2b-909c-b21c8df8925c@intel.com> (raw)
In-Reply-To: <20260331220744.GD183713@mdroper-desk1.amr.corp.intel.com>

Reviewed-by: Tomasz Lis <tomasz.lis@intel.com>

-Tomasz

On 4/1/2026 12:07 AM, Matt Roper wrote:
> On Tue, Mar 31, 2026 at 03:22:59PM +0000, Jakub Kolakowski wrote:
>> Enable SR-IOV support for NVL platforms.
>>
>> Signed-off-by: Jakub Kolakowski <jakub1.kolakowski@intel.com>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
>> Cc: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> ---
>>   drivers/gpu/drm/xe/xe_pci.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
>> index 1df3f08e2e1c..e7d7f0b6b998 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.c
>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>> @@ -443,6 +443,7 @@ static const struct xe_device_desc nvls_desc = {
>>   	.has_display = true,
>>   	.has_flat_ccs = 1,
>>   	.has_pre_prod_wa = 1,
>> +	.has_sriov = true,
> Since the structure field is defined as
>
>          u8 has_sriov:1;
>
> it might be slightly more idiomatic to assign 1 rather than 'true.'
> We're a bit inconsistent in the handling of the other flags in these
> structures as well.  Anyway, it doesn't really matter that much, so up
> to you whether you want to change it or not.  At some point we'll
> probably do a general cleanup to handle all of the flags in a consistent
> manner.
>
> Since we don't have CI setup for this platform yet, I'll let someone
> from the SR-IOV team give the formal r-b on this patch confirming that
> we have everything in place necessary to flip the switch here and start
> allowing SR-IOV use.
>
>
> Matt
>
>>   	.max_gt_per_tile = 2,
>>   	MULTI_LRC_MASK,
>>   	.require_force_probe = true,
>> @@ -481,6 +482,7 @@ static const struct xe_device_desc nvlp_desc = {
>>   	.has_flat_ccs = 1,
>>   	.has_page_reclaim_hw_assist = true,
>>   	.has_pre_prod_wa = true,
>> +	.has_sriov = true,
>>   	.max_gt_per_tile = 2,
>>   	MULTI_LRC_MASK,
>>   	.require_force_probe = true,
>> -- 
>> 2.34.1
>>

      reply	other threads:[~2026-05-13  0:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 15:22 [PATCH] drm/xe/sriov: Mark NVL as SR-IOV capable Jakub Kolakowski
2026-03-31 15:44 ` ✓ CI.KUnit: success for " Patchwork
2026-03-31 16:40 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-31 21:59 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-07 10:48   ` Kolakowski, Jakub1
2026-03-31 22:07 ` [PATCH] " Matt Roper
2026-05-13  0:08   ` Lis, Tomasz [this message]

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=827126ad-ed22-4f2b-909c-b21c8df8925c@intel.com \
    --to=tomasz.lis@intel.com \
    --cc=dnyaneshwar.bhadane@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=piotr.piorkowski@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