intel / idxd-config

Accel-config / libaccel-config
Other
59 stars 35 forks source link

Unable to turn on user SVA feature when intel_iommu=on,sm_on #46

Open eiclpy opened 1 year ago

eiclpy commented 1 year ago

I rebooted the system with "intel_iommu=on,sm_on" but the "Unable to turn on user SVA function" is still there.

CPU: Intel(R) Xeon(R) Gold 6448H System: Ubuntu 22.04 Kernel: 6.2.0-34-generic

$ accel-config -v
4.1.1.git435fa62b

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.2.0-34-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro intel_iommu=on,sm_on iommu=pt no5lvl

$ sudo dmesg | grep idxd
[    7.927615] idxd 0000:f2:01.0: enabling device (0144 -> 0146)
[    7.927634] idxd 0000:f2:01.0: Unable to turn on user SVA feature.
[    7.947937] idxd 0000:f2:01.0: Intel(R) Accelerator Device (v100)
[    7.947971] idxd 0000:f2:02.0: enabling device (0140 -> 0142)
[    7.947990] idxd 0000:f2:02.0: Unable to turn on user SVA feature.
[    7.987380] idxd 0000:f2:02.0: Intel(R) Accelerator Device (v100)
[ 1543.197818] idxd 0000:f2:01.0: Unable to turn on user SVA feature.
[ 1543.202996] idxd 0000:f2:01.0: Intel(R) Accelerator Device (v100)
[ 1543.203158] idxd 0000:f2:02.0: Unable to turn on user SVA feature.
[ 1543.208112] idxd 0000:f2:02.0: Intel(R) Accelerator Device (v100)

$ sudo dmesg | grep -i dmar
[    0.010986] ACPI: DMAR 0x000000006FF7A000 00027C (v01 SUPERM SMCI--MB 00000001 INTL 20091013)
[    0.011060] ACPI: Reserving DMAR table memory at [mem 0x6ff7a000-0x6ff7a27b]
[    0.170988] DMAR: IOMMU enabled
[    0.170989] DMAR: Enable scalable mode if hardware supports
[    0.432222] DMAR: Host address width 46
[    0.432224] DMAR: DRHD base: 0x000000a9ffc000 flags: 0x0
[    0.432231] DMAR: dmar0: reg_base_addr a9ffc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432236] DMAR: DRHD base: 0x000000be3fc000 flags: 0x0
[    0.432240] DMAR: dmar1: reg_base_addr be3fc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432244] DMAR: DRHD base: 0x000000d27fc000 flags: 0x0
[    0.432251] DMAR: dmar2: reg_base_addr d27fc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432254] DMAR: DRHD base: 0x000000e6bfc000 flags: 0x0
[    0.432259] DMAR: dmar3: reg_base_addr e6bfc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432263] DMAR: DRHD base: 0x000000faffc000 flags: 0x0
[    0.432267] DMAR: dmar4: reg_base_addr faffc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432270] DMAR: DRHD base: 0x000000fb7fc000 flags: 0x0
[    0.432275] DMAR: dmar5: reg_base_addr fb7fc000 ver 6:0 cap 9ed008c40780466 ecap 3ef9e86f050df
[    0.432278] DMAR: DRHD base: 0x000000957fc000 flags: 0x1
[    0.432282] DMAR: dmar6: reg_base_addr 957fc000 ver 6:0 cap 9ed008c40780466 ecap 3ee9e86f050df
[    0.432286] DMAR: RMRR base: 0x00000076edf000 end: 0x00000076f01fff
[    0.432289] DMAR: RMRR base: 0x000000748bc000 end: 0x00000074b05fff
[    0.432291] DMAR: ATSR flags: 0x0
[    0.432293] DMAR: RHSA base: 0x000000957fc000 proximity domain: 0x0
[    0.432296] DMAR: RHSA base: 0x000000a9ffc000 proximity domain: 0x0
[    0.432298] DMAR: RHSA base: 0x000000be3fc000 proximity domain: 0x0
[    0.432299] DMAR: RHSA base: 0x000000d27fc000 proximity domain: 0x0
[    0.432301] DMAR: RHSA base: 0x000000e6bfc000 proximity domain: 0x0
[    0.432303] DMAR: RHSA base: 0x000000faffc000 proximity domain: 0x0
[    0.432305] DMAR: RHSA base: 0x000000fb7fc000 proximity domain: 0x0
[    0.432307] DMAR: SATC flags: 0x0
[    0.432310] DMAR-IR: IOAPIC id 8 under DRHD base  0x957fc000 IOMMU 6
[    0.432313] DMAR-IR: HPET id 0 under DRHD base 0x957fc000
[    0.432315] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.433621] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    4.537603] DMAR: IOMMU feature pasid inconsistent
[    4.537604] DMAR: IOMMU feature pasid inconsistent
[    4.537606] DMAR: IOMMU feature pasid inconsistent
[    4.537607] DMAR: IOMMU feature pasid inconsistent
[    4.537609] DMAR: IOMMU feature pasid inconsistent
[    4.537610] DMAR: IOMMU feature pasid inconsistent
[    4.537611] DMAR: dmar5: Using Queued invalidation
[    4.537618] DMAR: dmar4: Using Queued invalidation
[    4.537620] DMAR: dmar3: Using Queued invalidation
[    4.537622] DMAR: dmar2: Using Queued invalidation
[    4.537625] DMAR: dmar1: Using Queued invalidation
[    4.537630] DMAR: dmar0: Using Queued invalidation
[    4.537632] DMAR: dmar6: Using Queued invalidation
[    4.542595] DMAR: Intel(R) Virtualization Technology for Directed I/O

$ sudo lspci -vvv -s f2:01.0
f2:01.0 System peripheral: Intel Corporation Device 0b25
        Subsystem: Intel Corporation Device 0000
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        NUMA node: 0
        IOMMU group: 1
        Region 0: Memory at 21bffff50000 (64-bit, prefetchable) [size=64K]
        Region 2: Memory at 21bffff20000 (64-bit, prefetchable) [size=128K]
        Capabilities: [40] Express (v2) Root Complex Integrated Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0
                        ExtTag+ RBE+ FLReset+
                DevCtl: CorrErr- NonFatalErr- FatalErr+ UnsupReq-
                        RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
                        MaxPayload 512 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
                         10BitTagComp+ 10BitTagReq+ OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
                         EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
                         FRS-
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis+ LTR- OBFF Disabled,
                         AtomicOpsCtl: ReqEn-
        Capabilities: [80] MSI-X: Enable+ Count=9 Masked-
                Vector table: BAR=0 offset=00002000
                PBA: BAR=0 offset=00003000
        Capabilities: [90] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [100 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
                UESvrt: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
                AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
                        MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
                HeaderLog: 00000000 00000000 00000000 00000000
        Capabilities: [150 v1] Latency Tolerance Reporting
                Max snoop latency: 0ns
                Max no snoop latency: 0ns
        Capabilities: [160 v1] Transaction Processing Hints
                Device specific mode supported
                Steering table in TPH capability structure
        Capabilities: [170 v1] Virtual Channel
                Caps:   LPEVC=1 RefClk=100ns PATEntryBits=1
                Arb:    Fixed+ WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
                VC1:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=1 ArbSelect=Fixed TC/VC=02
                        Status: NegoPending- InProgress-
        Capabilities: [200 v1] Designated Vendor-Specific: Vendor=8086 ID=0005 Rev=0 Len=24 <?>
        Capabilities: [220 v1] Address Translation Service (ATS)
                ATSCap: Invalidate Queue Depth: 00
                ATSCtl: Enable+, Smallest Translation Unit: 00
        Capabilities: [230 v1] Process Address Space ID (PASID)
                PASIDCap: Exec- Priv+, Max PASID Width: 14
                PASIDCtl: Enable+ Exec- Priv+
        Capabilities: [240 v1] Page Request Interface (PRI)
                PRICtl: Enable- Reset-
                PRISta: RF- UPRGI- Stopped+
                Page Request Capacity: 00000200, Page Request Allocation: 00000000
        Kernel driver in use: idxd
        Kernel modules: idxd

$ cat /sys/bus/dsa/devices/dsa0/pasid_enabled
0
b1gby commented 1 year ago

Hi, I have the same problem. Have you solved it?

ramesh-thomas commented 1 year ago

@fyu1 @davejiang looks like this is caused by iommu not getting enabled. Is there any BIOS or other configuration that needs to be changed from default? Following is the cpu and kernel. CPU: Intel(R) Xeon(R) Gold 6448H Kernel: 6.2.0-34-generic

fyu1 commented 1 year ago

PRI is not enabled and thus SVA cannot be enabled: Capabilities: [240 v1] Page Request Interface (PRI) PRICtl: Enable- Reset-

Could you remove "iommu=pt" in the kernel option?

Jonas-Heinrich commented 1 year ago

Did somebody solve this issue? I am just using intel_iommu=on,sm_on without iommu=pt as kernel options, but still get the warning and disabled PRI/pasid.

The IAA User Guide specifies that DSA/IAX option should be enabled under IOAT in the BIOS. As far as I can tell that is related to the I/O acceleration technology DMA engine, so perhaps this is relevant (?). As I am using a Dell motherboard/BIOS however, there does not seem to be an equivalent to this option.

ramesh-thomas commented 11 months ago

@Jonas-Heinrich can you give more details of the CPU/Platform, what you are trying to do and what errors are you getting?

@fyu1 do you know what is going on?

eiclpy commented 11 months ago

I have the same problem as @Jonas-Heinrich . Here is the output of inxi -F @ramesh-thomas

System:
  Host: xxx Kernel: 6.2.0-37-generic x86_64 bits: 64
    Console: pty pts/1 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
  Type: Unknown System: Supermicro product: Super Server v: 0123456789
    serial: 0123456789
  Mobo: Supermicro model: X13DEI v: 1.01 serial: xxxxxxxxx
    UEFI: American Megatrends LLC. v: 1.4 date: 08/09/2023
CPU:
  Info: 32-core model: Intel Xeon Gold 6448H bits: 64 type: MT MCP cache:
    L2: 64 MiB
  Speed (MHz): avg: 1247 min/max: 800/4100 cores: 1: 800 2: 800 3: 800
    4: 804 5: 800 6: 3808 7: 3100 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800
    14: 2600 15: 2406 16: 2600 17: 800 18: 2600 19: 2400 20: 800 21: 800
    22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800
    31: 800 32: 800 33: 800 34: 800 35: 2600 36: 800 37: 2500 38: 800 39: 800
    40: 1639 41: 800 42: 800 43: 2000 44: 800 45: 800 46: 2400 47: 800
    48: 2400 49: 1700 50: 800 51: 800 52: 800 53: 800 54: 800 55: 800
    56: 4100 57: 800 58: 800 59: 800 60: 800 61: 800 62: 800 63: 2600 64: 800
Graphics:
  Device-1: ASPEED Graphics Family driver: ast v: kernel
  Display: server: No display server data found. Headless machine?
  Message: GL data unavailable for root.
Audio:
  Message: No device data found.
Network:
  Device-1: Mellanox MT43244 BlueField-3 integrated ConnectX-7 network
    driver: mlx5_core
  IF: ibs2f0 state: down
    mac: 00:00:06:36:fe:80:00:00:00:00:00:00:a0:88:c2:03:00:80:ee:76
  Device-2: Mellanox MT43244 BlueField-3 integrated ConnectX-7 network
    driver: mlx5_core
  IF: ibs2f1 state: down
    mac: 00:00:05:95:fe:80:00:00:00:00:00:00:a0:88:c2:03:00:80:ee:77
  Device-3: Broadcom NetXtreme BCM5720 Gigabit Ethernet PCIe driver: tg3
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 7c:c2:55:80:d4:ac
  Device-4: Broadcom NetXtreme BCM5720 Gigabit Ethernet PCIe driver: tg3
  IF: eno2 state: down mac: 7c:c2:55:80:d4:ad
  IF-ID-1: docker0 state: down mac: 02:42:f6:b2:88:a9
  IF-ID-2: enxbe3af2b6059f state: down mac: be:3a:f2:b6:05:9f
  IF-ID-3: tmfifo_net0 state: unknown speed: 10000 Mbps duplex: full
    mac: 00:1a:ca:ff:ff:02
Bluetooth:
  Device-1: Insyde RNDIS/Ethernet Gadget type: USB driver: rndis_host
  Report: This feature requires one of these tools: hciconfig/bt-adapter
Drives:
  Local Storage: total: 1.82 TiB used: 789.39 GiB (42.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
Partition:
  ID-1: / size: 1.79 TiB used: 788.75 GiB (43.1%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot size: 1.9 GiB used: 641.5 MiB (33.0%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 1.05 GiB used: 6.1 MiB (0.6%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) file: /swap.img
Sensors:
  Message: No ipmi sensor data found.
  System Temperatures: lm-sensors cpu: 23.0 0.0 mobo: N/A sodimm: DIMM 0.0
  Fan Speeds (RPM): lm-sensors N/A
Info:
  Processes: 946 Uptime: 12m Memory: 125.48 GiB used: 2.49 GiB (2.0%)
  Shell: Sudo inxi: 3.3.13
Jonas-Heinrich commented 11 months ago

@ramesh-thomas @fyu1 I sent you an email from my TU Munich (TUM) address with more details, there's some parts that I cannot share here.

I got it working by setting "EDKII Menu -> Socket Configuration -> IIO Configuration -> Opt-Out Illegal MSI Mitigation: Enable" in the BIOS of another machine. As I had to find out, this option is not available on e.g. Dell motherboards (to the best of my knowledge).

ramesh-thomas commented 11 months ago

@eiclpy @Jonas-Heinrich please work with @fyu1 to get this issue resolved and update this issue with your findings. Thanks.

SgtPepperr commented 11 months ago

Hi,I have the same problem.I ran the command as the dsa user guide,but something is not right.Here is my information.Thanks!@ramesh-thomas @fyu1

CPU:Intel(R) Xeon(R) Platinum 8475BL System: Ubuntu 22.04 kernel:https://gitee.com/anolis/anck-next/tree/devel-6.1


$ accel-config -v
4.1.3.git71676025

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on

$ sudo dmesg | grep idxd
[    5.275363] idxd 0000:00:06.0: Unable to turn on user SVA feature.
[    5.279597] idxd 0000:00:06.0: Failed to initialize perfmon. No PMU support: -19
[    5.288915] idxd 0000:00:06.0: Intel(R) Accelerator Device (v0)
[    5.289087] idxd 0000:00:07.0: Unable to turn on user SVA feature.
[    5.290949] idxd 0000:00:07.0: Failed to initialize perfmon. No PMU support: -19
[    5.292351] idxd 0000:00:07.0: Intel(R) Accelerator Device (v0)

$ sudo dmesg | grep iommu
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on
[    0.022942] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.27+ root=UUID=424deffb-478e-4611-834c-609e9ba58e75 ro vga=792 console=tty0 console=ttyS0,115200n8 net.ifnames=0 noibrs crashkernel=0M-1G:0M,1G-4G:192M,4G-128G:384M,128G-:512M nvme_core.io_timeout=4294967295 nvme_core.admin_timeout=4294967295 intel_iommu=on,sm_on
[    0.629394] iommu: Default domain type: Passthrough

$ sudo lspci -vvv -s 00:06.0
00:06.0 System peripheral: Intel Corporation Device 0b25
    Subsystem: Intel Corporation Device 2010
    Physical Slot: 6
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Region 0: Memory at fa248000 (64-bit, prefetchable) [size=8K]
    Region 2: Memory at fa24a000 (64-bit, prefetchable) [size=8K]
    Expansion ROM at fea12000 [disabled] [size=2K]
    Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
        Vector table: BAR=0 offset=00000600
        PBA: BAR=0 offset=00000000
    Capabilities: [50] Express (v2) Root Complex Integrated Endpoint, MSI 00
        DevCap: MaxPayload 128 bytes, PhantFunc 0
            ExtTag- RBE- FLReset-
        DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
            RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
            MaxPayload 128 bytes, MaxReadReq 128 bytes
        DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
        DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR-
             10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix+, MaxEETLPPrefixes 1
             EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
             FRS-
             AtomicOpsCap: 32bit- 64bit- 128bitCAS-
        DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
             AtomicOpsCtl: ReqEn-
    Kernel driver in use: idxd
    Kernel modules: idxd
(I lost many capabilities compared with others)

$ cat /sys/bus/dsa/devices/dsa0/pasid_enabled
0

$accel-config load-config -c contrib/configs/app_profile.conf -e
dsa0 is active. Skipping...
(why i can't config my dsa device)
ramesh-thomas commented 11 months ago

"dsa0 is active. Skipping..."

The device was already enabled. You can give the -f option to disable enabled devices.

eiclpy commented 11 months ago

I get an error instead of a warning when I configure the device. @fyu1 @ramesh-thomas

$ sudo dmesg | grep iommu
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.2.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro intel_iommu=on,sm_on no5lvl
[    0.171459] Kernel command line: BOOT_IMAGE=/vmlinuz-6.2.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro intel_iommu=on,sm_on no5lvl
[    2.779978] iommu: Default domain type: Translated
[    2.779978] iommu: DMA domain TLB invalidation policy: lazy mode

$ accel-config -v
4.1.3+

$ sudo accel-config load-config -c contrib/configs/app_profile.conf -e
Enabling device dsa0
Error enabling device
Error[0x800c0000] dsa0: wq error - no shared wq support (platform configuration error)
SgtPepperr commented 11 months ago

Thank you!I have disabled the dsa0, and run the command again.But I get a new error message.@ramesh-thomas(I am root)


$      accel-config load-config -c contrib/configs/app_profile.conf -e
libaccfg: accfg_device_set_read_buffer_limit: dsa0: write failed: Operation not permitted
device set read_buffer_limit value failed
Parse json and set device fail: -1

$     ls /sys/bus/dsa/devices/dsa0
cdev_major    engine0.1  group0.0          max_tokens            op_cap             subsystem
clients       engine0.2  max_batch_size    max_transfer_size     pasid_enabled      token_limit
cmd_status    engine0.3  max_engines       max_work_queues       power              uevent
configurable  errors     max_groups        max_work_queues_size  read_buffer_limit  version
engine0.0     gen_cap    max_read_buffers  numa_node             state              wq0.0
Lhoddy commented 10 months ago

I had the exact same problem as you, did you solve it? @eiclpy

Johnnyjax commented 8 months ago

Does anyone have any update on fixing this. I also have the very same issue of PRICtl being disabled and it shows "Unable to turn on SVA feature" when I boot up.

NikoZHAI commented 5 months ago

For anybody who has seen 'SVM disabled, incompatible paging mode' in the kernel message, try disable 5-level pagetable and reboot. (add 'no5lvl' to your kernel command line)