- Dec 08, 2022
-
-
Javier Diaz authored
-
Javier Diaz authored
-
- Dec 06, 2022
-
-
kmc-home authored
-
- Oct 05, 2022
-
-
kmc-home authored
-
- Oct 04, 2022
-
-
Jimmy Walker authored
Adding Art Simmons public key to answers.sls See merge request !87
-
Kevin Crotty authored
-
- Sep 21, 2022
-
-
John Ward authored
-
- Sep 07, 2022
-
-
Javier Diaz authored
-
Javier Diaz authored
-
Javier Diaz authored
-
- Aug 22, 2022
- Aug 03, 2022
-
-
Jimmy Walker authored
Cherry pick filebeat See merge request !85
-
-
- Jun 17, 2022
-
-
Jimmy Walker authored
updating pillar to remove ipa.cybbh.space See merge request !81
-
-
- Mar 29, 2022
-
-
Javier Diaz authored
-
- Mar 14, 2022
-
-
Javier Diaz authored
-
- Feb 18, 2022
-
-
Javier Diaz authored
-
- Jan 25, 2022
-
-
Javier Diaz authored
-
- Jan 21, 2022
-
-
Javier Diaz authored
-
Javier Diaz authored
- Jan 18, 2022
-
-
John Ward authored
- Jan 12, 2022
-
-
John Ward authored
-
- Jan 07, 2022
- Jan 05, 2022
-
-
Javier Diaz authored
-
Javier Diaz authored
-
John Ward authored
-
- Jan 03, 2022
-
-
John Ward authored
-
John Ward authored
The Linux kernel requires that device drivers use the DMA remapping APIs to make physical memory accessible to devices, even when no remapping hardware is present. The NVIDIA Linux driver generally adheres to this requirement, except when it detects that the remapping is implemented using the SWIOTLB, which is not supported by the NVIDIA Linux driver. When the NVIDIA Linux driver detects that the SWIOTLB is in use, it will instead calculate the correct bus address needed to access a physical allocation instead of calling the kernel DMA remapping APIs to do so, as SWIOTLB space is very limited and exhaustion can result in a kernel panic.
-
- Dec 30, 2021
- Dec 27, 2021
-
-
Javier Diaz authored
-
- Dec 23, 2021