On 12/11/19 9:42 AM, Lu Baolu wrote:
Current map_sg stores trace message in a coarse manner. This
extends it so that more detailed messages could be traced.
The map_sg trace message looks like:
map_sg: dev=:00:17.0 [1/9] dev_addr=0xf8f9 phys_addr=0x158051000
size=4096
map_sg: dev=:
On 12/19/19 1:18 PM, Lu Baolu wrote:
Currently if flush queue initialization fails, we return error
or enforce the system-wide strict mode. These are unnecessary
because we always check the existence of a flush queue before
queuing any iova's for lazy flushing. Printing a informational
message is
On 12/19/19 1:18 PM, Lu Baolu wrote:
If Intel IOMMU strict mode is enabled by users, it's unnecessary
to create the iova flush queue.
Signed-off-by: Lu Baolu
Queued for v5.6.
Thanks,
-baolu
___
iommu mailing list
iommu@lists.linux-foundation.org
htt
On 12/3/19 3:58 AM, Jacob Pan wrote:
Mostly extracted from nested SVA/SVM series based on review comments of v7.
https://lkml.org/lkml/2019/10/24/852
This series also adds a few important fixes for native use of SVA. Nested
SVA new code will be submitted separately as a smaller set. Based on the
On 11/12/19 2:39 PM, Lu Baolu wrote:
This adds Kconfig option INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
to make it easier for distributions to enable or disable the
Intel IOMMU scalable mode by default during kernel build.
Signed-off-by: Lu Baolu
Queued for v5.6.
Thanks,
-baolu
___
From: Xiaotao Yin
[ Upstream commit 472d26df5e8075eda677b6be730e0fbf434ff2a8 ]
During ethernet(Marvell octeontx2) set ring buffer test:
ethtool -G eth1 rx tx
following kmemleak will happen sometimes:
unreferenced object 0x000b85421340 (size 64):
comm "ethtool", pid 867, jiffies 42953235
From: Xiaotao Yin
[ Upstream commit 472d26df5e8075eda677b6be730e0fbf434ff2a8 ]
During ethernet(Marvell octeontx2) set ring buffer test:
ethtool -G eth1 rx tx
following kmemleak will happen sometimes:
unreferenced object 0x000b85421340 (size 64):
comm "ethtool", pid 867, jiffies 42953235
