<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hi Patrick,<o:p></o:p> <o:p> </o:p> Can you provide the grub settings? Is iommu.passthrough=1 included?<o:p></o:p> <o:p> </o:p> Also, is qat_c62xvf loaded as well?<o:p></o:p> <o:p> </o:p> Finally, a few guidelines on the vfio driver:<o:p></o:p> At times, we need to configure the vfio driver.<o:p></o:p> On kernel vers. 5.9+ we need to load the vfio-pci driver with the additional parameter disable_denylist=1<o:p></o:p> Unload the vfio-pci driver if it is already loaded so that we can reload it with the correct parameters : sudo modprobe -r vfio_iommu_type1; sudo modprobe -r vfio_pci; sudo modprobe -r vfio_virqfd; sudo modprobe -r vfio<o:p></o:p> If you can't unload the vfio driver because it's been built into the kernel, you'll have to find another way to change VFIO parameters, or to rebuild your kernel with VFIO_PCI set as a module. Failing to do that, you might encounter issues later on when you try to bind the VFs to VFIO. Load the vfio-pci driver and bind it to QAT VFs device ids: sudo modprobe vfio-pci disable_denylist=1 enable_sriov=1 vfio-pci.ids=8086:37c9 Enable no-iommu-mode: echo "1" | sudo tee /sys/module/vfio/parameters/enable_unsafe_noiommu_mode<o:p></o:p> /sys/module/vfio/parameter is missing ?<o:p></o:p> If /sys/module/vfio/parameters does not exist, you might be missing the kernel module VFIO_NOIOMMU<o:p></o:p> <o:p> </o:p> Automatically set VFIO params on boot<o:p></o:p> It's possible to set these parameters automatically on boot by creating a /etc/modprobe.d/vfio-pci.conf file with the parameters : cat /etc/modprobe.d/vfio-pci.conf options vfio enable_unsafe_noiommu_mode=1 options vfio-pci disable_denylist=1 enable_sriov=1 vfio-pci.ids=8086:37c9<o:p></o:p> <o:p> </o:p> We haven’t encountered this issue in the past, so just making sure the configuration is correct. I don’t think having the driver static/loadable should make a difference, I will try with building statically on my setup.<o:p></o:p> <o:p> </o:p> Thank you!<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Patrick Robb <probb@iol.unh.edu> Sent: Monday, October 9, 2023 9:29 PM To: Ruifeng Wang <Ruifeng.Wang@arm.com> Cc: Juraj Linkeš <juraj.linkes@pantheon.tech>; Dharmik Jayesh Thakkar <DharmikJayesh.Thakkar@arm.com>; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; ci@dpdk.org; nd <nd@arm.com> Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server<o:p></o:p> </div> </div> <o:p> </o:p> <div> <div> Also I am just now thinking I probably should have provided dpdk-devbind.py output: probb@arm-ampere-dut:/tmp/dpdk/usertools$ dpdk-devbind.py --status Crypto devices using kernel driver ================================== 0000:03:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx unused=vfio-pci 0000:04:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx unused=vfio-pci 0000:05:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx unused=vfio-pci <o:p></o:p> </div> </div> </div> </div> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. </body> </html>