On Thu, Apr 13, 2023 at 03:49:29PM +0300, Leon Romanovsky wrote: > > that it fixes a setup with VF and VM, so I think thats an ok thing to > > call out as the goal. > > VF or VM came from user perspective of where this behavior is not > correct. Avihai saw this in QEMU, so he described it in terms which > are more clear to the end user. Except it is not clear, the VF/VM issue is more properly solved by showing the real relaxed order cap to the VM. This series really is about fixing the FW mistake that had a dynamic cap bit for relaxed ordering. The driver does not support cap bits that change during runtime. mlx5 racily bodged around the broken cap by by protecting the feature with the same test the FW was using to make the cap dynamic, but this is all just wrong. The new cap bit is static, doesn't change like a cap bit should, and so we don't need the bodge anymore. That the bodge didn't work in VMs because of a qmeu/vfio issue is another bad side effect, but it isn't really the point of this series. This is why I'd like it if the code was more closely organized to make it clear that the old cap is OLD and that the bodge that goes along with it is part of making the cap bit work. It kind of gets lost in the way things are organized what is old/new. Jason
