Skip to content

virtio_net: apply DMA cache maintenance for a non-coherent rproc peer - #15

Open
UlasSertan wants to merge 1 commit into
t3gemstone:v6.12.24-ti-arm64-r43-t3-gem-o1from
UlasSertan:virtio-net-fix
Open

virtio_net: apply DMA cache maintenance for a non-coherent rproc peer#15
UlasSertan wants to merge 1 commit into
t3gemstone:v6.12.24-ti-arm64-r43-t3-gem-o1from
UlasSertan:virtio-net-fix

Conversation

@UlasSertan

Copy link
Copy Markdown

The J722S R5F remote core is not cache-coherent with the A53, and a legacy remoteproc virtio device cannot negotiate VIRTIO_F_ACCESS_PLATFORM, so the vring layer never syncs payload buffers. Clean RX buffers before posting, invalidate received data before reading, and clean TX payloads before publishing, against the rproc vdev's non-coherent parent device.

The J722S R5F remote core is not cache-coherent with the A53, and a
legacy remoteproc virtio device cannot negotiate
VIRTIO_F_ACCESS_PLATFORM, so the vring layer never syncs payload
buffers. Clean RX buffers before posting, invalidate received data
before reading, and clean TX payloads before publishing, against the
rproc vdev's non-coherent parent device.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant