diff options
| author | Ronak Doshi <[email protected]> | 2021-01-27 18:08:16 -0800 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2021-01-29 21:07:03 -0800 |
| commit | de1da8bcf40564a2adada2d5d5426e05355f66e8 (patch) | |
| tree | 947f76c45089f8a1a83f8ce1c4680ea0cfcb0f45 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 6c13d75beee5313a38adab7e14365724e301886f (diff) | |
vmxnet3: Remove buf_info from device accessible structures
buf_info structures in RX & TX queues are private driver data that
do not need to be visible to the device. Although there is physical
address and length in the queue descriptor that points to these
structures, their layout is not standardized, and device never looks
at them.
So lets allocate these structures in non-DMA-able memory, and fill
physical address as all-ones and length as zero in the queue
descriptor.
That should alleviate worries brought by Martin Radev in
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20210104/022829.html
that malicious vmxnet3 device could subvert SVM/TDX guarantees.
Signed-off-by: Petr Vandrovec <[email protected]>
Signed-off-by: Ronak Doshi <[email protected]>
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions