Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Marcello Sylvester Bauer <marcello.bauer@9elements.com>,
	intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Badal Nilawar" <badal.nilawar@intel.com>
Subject: Re: Intel Xe SR-IOV support status
Date: Tue, 1 Jul 2025 16:52:02 +0200	[thread overview]
Message-ID: <bb783b7b-80d8-4779-a8a4-ad495dd9948c@intel.com> (raw)
In-Reply-To: <72fd3ae7-46da-4203-b583-3fb857e73542@9elements.com>

Hi Marcello,

On 30.06.2025 13:47, Marcello Sylvester Bauer wrote:
> Hi,
> 
> Starting with Tiger Lake, support for GVT-g was discontinued in favor of
> SR-IOV for graphics virtualization[1]. Currently, the upstream Xe
> drivers only support SR-IOV on Panther Lake. The table below summarizes
> the current state based on the .has_sriov flag.
> 
> | Intel Gen | drm-xe-next[2] | xe-for-CI[2] | intel lts i915[3] |
> | --------- | -------------- | ------------ | ----------------- |
> | TGL       |             no | no           | v5.15             |
> | ADL/RPL   |             no | yes (debug)  | v5.15             |
> | MTL       |             no | no           | v6.1              |
> | ARL       |             no | no           | no                |
> | PTL       |        v6.13.1 | yes          | no                |

Note that we also have

  | ATSM      |             no | yes (debug)  |

> 
> Interestingly, the xe/topic/xe-for-CI testing branch only covers SR-IOV
> testing on the ADL platform and not the MTL or ARL platforms.
> 
> Is there a reason why SR-IOV has not yet been enabled on the other
> platforms? 

Since platforms before LNL are not officially supported by the Xe
driver, we have only enabled SR-IOV on those SDV platforms which are
actively used and tested by our public CI.


> Are there any plans or timeline for adding support for them?

AFAIK it’s unlikely. While in case of TGL the enabling is just a
one-liner patch with new .has_sriov flag, however for robust MTL it
would require much more SR-IOV specific code to be added, but there is
no point to add anything until those platforms itself will be fully
tested in the native mode (non-virtualized).

Michal

> 
> Kind regards,
> Marcello
> ---
> [1] https://www.intel.com/content/www/us/en/support/articles/000058558/
> graphics.html
> [2] https://gitlab.freedesktop.org/drm/xe
> [3] https://github.com/intel/linux-intel-lts
> [4] https://patchwork.freedesktop.org/patch/603316/


  reply	other threads:[~2025-07-01 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 11:47 Intel Xe SR-IOV support status Marcello Sylvester Bauer
2025-07-01 14:52 ` Michal Wajdeczko [this message]
2025-07-01 16:15   ` Marcello Sylvester Bauer

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=bb783b7b-80d8-4779-a8a4-ad495dd9948c@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=airlied@gmail.com \
    --cc=badal.nilawar@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=marcello.bauer@9elements.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.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