Thread (23 messages) flat view 23 messages, 4 authors, 2021-02-20

Re: [PATCH v1] vdpa/mlx5: Restore the hardware used index after change map

From: Eli Cohen <hidden>
Date: 2021-02-17 06:52:50
Also in: lkml

On Tue, Feb 16, 2021 at 04:25:20PM -0800, Si-Wei Liu wrote:
quoted
quoted
The saved mvq->avail_idx will be used to recreate hardware virtq object and
the used index in create_virtqueue(), once status DRIVER_OK is set. I
suspect we should pass the index to mvq->used_idx in
mlx5_vdpa_set_vq_state() below instead.
Right, that's what I am checking but still no final conclusions. I need
to harness hardware guy to provide me with clear answers.
OK. Could you update what you find from the hardware guy and let us know
e.g. if the current firmware interface would suffice?
Te answer I got is that upon query_virtqueue, the hardware available and
used indices should always return the same value for virtqueues that
complete in order - that's the case for network virtqueues. The value
returned is the consumer index of the hardware. These values should be
provided when creating a virtqueue; in case of attaching to an existing
virtqueue (e.g. after suspend and resume), the values can be non zero.

Currently there's a bug in the firmware where for RX virtqueue, the
value returned for the available index is wrong. However, the value
returned for used index is the correct value.

Therefore, we need to return the hardware used index in get_vq_state()
and restore this value into both the new object's available and used
indices.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help