News: 0001569293

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

SR-IOV Will Only Be Supported On Intel Arc Pro Graphics Cards

([Intel] 84 Minutes Ago SR-IOV Only For Arc Pro)


[1]SR-IOV for virtualization with the Intel Xe kernel graphics driver will only be supported on the Arc Pro products and -- unfortunately -- not the consumer Arc B-Series graphics cards.

While [2]SR-IOV will be found with Panther Lake Xe3 graphics and other select integrated graphics, when it comes to the [3]Battlemage discrete graphics processors it will only be supported with the Arc Pro products.

Upstreamed for Linux 6.17 was [4]enabling SR-IOV support for Battlemage GPUs with the Xe kernel graphics driver. That followed Intel earlier this year promoting SR-IOV for virtualization as part of [5]the Project Battlematrix plans :

With the enablement patches for Linux it only talked of SR-IOV enablement for "Battlemage" without mentioning any specific products. Thus many Linux users were hopeful that SR-IOV would also be coming to the consumer Battlemage graphics cards like the [6]Arc B580 and [7]Arc B570 .

I received confirmation from Intel today that SR-IOV will only be supported with their Pro products. So, unfortunately, like with AMD and NVIDIA you will need to be using the professional product SKUs for SR-IOV with Intel discrete graphics cards.



[1] https://www.phoronix.com/search/SR-IOV

[2] https://www.phoronix.com/news/Intel-SR-IOV-PTL-ARL-State

[3] https://www.phoronix.com/search/Battlemage

[4] https://www.phoronix.com/news/Intel-Enables-BMG-SR-IOV-Linux

[5] https://www.phoronix.com/review/intel-arc-pro-b-series

[6] https://www.phoronix.com/review/intel-arc-b580-gpu-compute

[7] https://www.phoronix.com/review/intel-arc-b570-linux


rabcor

Bushe

fitzie

dimko

pr0spekt

Developer12

touchdown

davidbepo

Developer12

It is a very humbling experience to make a multimillion-dollar mistake, but
it is also very memorable. I vividly recall the night we decided how to
organize the actual writing of external specifications for OS/360. The
manager of architecture, the manager of control program implementation, and
I were threshing out the plan, schedule, and division of responsibilities.
The architecture manager had 10 good men. He asserted that they
could write the specifications and do it right. It would take ten months,
three more than the schedule allowed.
The control program manager had 150 men. He asserted that they
could prepare the specifications, with the architecture team coordinating;
it would be well-done and practical, and he could do it on schedule.
Furthermore, if the architecture team did it, his 150 men would sit twiddling
their thumbs for ten months.
To this the architecture manager responded that if I gave the control
program team the responsibility, the result would not in fact be on time,
but would also be three months late, and of much lower quality. I did, and
it was. He was right on both counts. Moreover, the lack of conceptual
integrity made the system far more costly to build and change, and I would
estimate that it added a year to debugging time.
-- Frederick Brooks Jr., "The Mythical Man Month"