num_vfs is always calculated as zero.
Signed-off-by: George Cherian <george.cher...@cavium.com>
---
drivers/net/ethernet/cavium/thunder/thunder_bgx.c | 1 +
drivers/net/ethernet/cavium/thunder/thunder_bgx.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/net/ethernet/cavium/t
+0x24/0x28
[35322.773042] Code: d503201f f9400e93 b940e280 91051274 (f9403261)
Reported-by: Joseph DeVincentis <joseph.devincen...@cavium.com>
Signed-off-by: George Cherian <george.cher...@cavium.com>
---
include/linux/ptr_ring.h | 13 +
1 file changed, 13 insertions(+)
eed to order these reads.
It is not the case that producer is reading the value, but the consumer
reading stale value. So we need to have a strict rmb in place .
Reported-by: George Cherian <george.cher...@cavium.com>
Suggested-by: Jason Wang <jasow...@redhat.com>
Signed-off-b
assumption being that producers do not need to read the value so we do
not need to order these reads.
Reported-by: George Cherian <george.cher...@cavium.com>
Suggested-by: Jason Wang <jasow...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
I'm asked for asking fo
