qat: Export missing symbols in qat_commonSome symbols required by dependent modules were missing fromqat_common.ko and qat_api.ko, causing load failures when local symbolresolution is disabled.
qat: Export missing symbols in qat_commonSome symbols required by dependent modules were missing fromqat_common.ko and qat_api.ko, causing load failures when local symbolresolution is disabled.PR: 291271Reviewed by: zlei, markjDifferential Revision: https://reviews.freebsd.org/D54107
show more ...
qat: add disable safe dc mode for QAT SPR devicesBuild and sysctl configuration modes are introduced for QAT SPRdevices to disable safe dc mode. A new QAT driver build option‘QAT_DISABLE_SAFE_DC_
qat: add disable safe dc mode for QAT SPR devicesBuild and sysctl configuration modes are introduced for QAT SPRdevices to disable safe dc mode. A new QAT driver build option‘QAT_DISABLE_SAFE_DC_MODE’ is required to build the QAT driverwith code that allows a request to be sent to FW to override the‘History Buffer’ mitigation. Default QAT driver builds do notinclude this ‘QAT_DISABLE_SAFE_DC_MODE’ build option. Even if theQAT driver was built with code that allows a request to be sent toFW to override the ‘History Buffer’ mitigation, the QAT driver muststill be configured using sysctl to request an override of the‘History Buffer’ mitigation if desired. The default QAT driverconfiguration option sysctl dev.qat.X.disable_safe_dc_mode does notallow override of the mitigation. The new sysctl attributedisable_safe_dc_mode is to be set to 1 for overriding the historybuffer mitigation. Firmware for qat_4xxx is updated for this change.If this mode is enabled, decompression throughput increases but mayresult in a data leak if num_user_processes is more than 1.This option is to be enabled only if your system is not prone touser data leaks.Reviewed by: markj, ziaeeMFC after: 2 weeksSponsored by: Intel CorporationDifferential Revision: https://reviews.freebsd.org/D50379
sys: Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
qat: Add Intel® 4xxx Series VF driver supportOverview:Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardwareacceleration for offloading security, authentication and compressionservices
qat: Add Intel® 4xxx Series VF driver supportOverview:Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardwareacceleration for offloading security, authentication and compressionservices from the CPU, thus significantly increasing the performance andefficiency of standard platform solutions.This commit introduces:- Intel® 4xxx Series VF driver support.- Device configurability via sysctls.- UIO support for Intel® 4xxx Series devices.Patch co-authored by: Krzysztof Zdziarski <krzysztofx.zdziarski@intel.com>Patch co-authored by: Michal Gulbicki <michalx.gulbicki@intel.com>Patch co-authored by: Julian Grajkowski <julianx.grajkowski@intel.com>Patch co-authored by: Piotr Kasierski <piotrx.kasierski@intel.com>Patch co-authored by: Lukasz Kolodzinski <lukaszx.kolodzinski@intel.com>Patch co-authored by: Karol Grzadziel <karolx.grzadziel@intel.com>Sponsored by: Intel CorporationDifferential Revision: https://reviews.freebsd.org/D39850
qat: Add Intel® 4xxx Series platform supportOverview:Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardwareacceleration for offloading security, authentication and compressionservices
qat: Add Intel® 4xxx Series platform supportOverview:Intel(R) QuickAssist Technology (Intel(R) QAT) provides hardwareacceleration for offloading security, authentication and compressionservices from the CPU, thus significantly increasing the performance andefficiency of standard platform solutions.This commit introduces:- Intel® 4xxx Series platform support.- QuickAssist kernel API implementation update for Generation 4 device. Enabled services: symmetric cryptography and data compression.- Increased default number of crypto instances in static configuration for performance purposes.OCF backend changes:- changed GCM/CCM MAC validation policy to generate MAC by HW and validate by SW due to the QAT HW limitations.Patch co-authored by: Krzysztof Zdziarski <krzysztofx.zdziarski@intel.com>Patch co-authored by: Michal Jaraczewski <michalx.jaraczewski@intel.com>Patch co-authored by: Michal Gulbicki <michalx.gulbicki@intel.com>Patch co-authored by: Julian Grajkowski <julianx.grajkowski@intel.com>Patch co-authored by: Piotr Kasierski <piotrx.kasierski@intel.com>Patch co-authored by: Adam Czupryna <adamx.czupryna@intel.com>Patch co-authored by: Konrad Zelazny <konradx.zelazny@intel.com>Patch co-authored by: Katarzyna Rucinska <katarzynax.kargol@intel.com>Patch co-authored by: Lukasz Kolodzinski <lukaszx.kolodzinski@intel.com>Patch co-authored by: Zbigniew Jedlinski <zbigniewx.jedlinski@intel.com>Sponsored by: Intel CorporationReviewed by: markj, jhbDifferential Revision: https://reviews.freebsd.org/D36254
qat: Remove non-existent path from -I.Reviewed by: markjReported by: GCC -Wmissing-include-dirsDifferential Revision: https://reviews.freebsd.org/D36779
LinuxKPI: define LINUXKPI_INCLUDES for module builds as wellWhile for in-kernel we already have LINUXKPI_INCLUDES in kern.pre.mkfor kmod builds we've not had a common define to use leading to vari
LinuxKPI: define LINUXKPI_INCLUDES for module builds as wellWhile for in-kernel we already have LINUXKPI_INCLUDES in kern.pre.mkfor kmod builds we've not had a common define to use leading to variousspellings of include paths.In order for the include list to be expanded more easily in the future,e.g., adding the "dummy" includes (for all) and to harmonize code,duplicate LINUXKPI_INCLUDES to kmod.mk and use it for all module Makefiles.MFC after: 1 weekReviewed by: hselaskyDifferential Revision: https://reviews.freebsd.org/D36683
qat: Move CWARNFLAGS down so it works.CWARNFLAGS must be added to after including kern.mk, otherwise all thewarnings set in kern.mk are ignored. This is why the-Wmissing-prototypes warnings were
qat: Move CWARNFLAGS down so it works.CWARNFLAGS must be added to after including kern.mk, otherwise all thewarnings set in kern.mk are ignored. This is why the-Wmissing-prototypes warnings were not seen previously.While here, drop -Wno-pointer-sign as it is doesn't seem to be needed,but add -Wno-cast-qual to silence warnings for various casts of constpointers to non-const pointers.Reviewed by: MichalX.Gulbicki_intel.com, markjSponsored by: DARPADifferential Revision: https://reviews.freebsd.org/D36332
qat: Import a new Intel (R) QAT driverQAT in-tree driver ported from out-of-tree release availablefrom 01.org.The driver exposes complete cryptography and data compressionAPI in the kernel and
qat: Import a new Intel (R) QAT driverQAT in-tree driver ported from out-of-tree release availablefrom 01.org.The driver exposes complete cryptography and data compressionAPI in the kernel and integrates with Open Crypto Framework.Details of supported operations, devices and usage can be foundin man and on 01.org.Patch co-authored by: Krzysztof Zdziarski <krzysztofx.zdziarski@intel.com>Patch co-authored by: Michal Jaraczewski <michalx.jaraczewski@intel.com>Patch co-authored by: Michal Gulbicki <michalx.gulbicki@intel.com>Patch co-authored by: Julian Grajkowski <julianx.grajkowski@intel.com>Patch co-authored by: Piotr Kasierski <piotrx.kasierski@intel.com>Patch co-authored by: Adam Czupryna <adamx.czupryna@intel.com>Patch co-authored by: Konrad Zelazny <konradx.zelazny@intel.com>Patch co-authored by: Katarzyna Rucinska <katarzynax.kargol@intel.com>Patch co-authored by: Lukasz Kolodzinski <lukaszx.kolodzinski@intel.com>Patch co-authored by: Zbigniew Jedlinski <zbigniewx.jedlinski@intel.com>Reviewed by: markj, jhb (OCF integration)Reviewed by: debdrup, pauamma (docs)Sponsored by: Intel CorporationDifferential Revision: https://reviews.freebsd.org/D34632