<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/stable/linux.git/drivers/vdpa, branch master</title>
<subtitle>Linux kernel stable tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/'/>
<updated>2026-08-19T10:38:48+00:00</updated>
<entry>
<title>vduse: Add suspend</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:33:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b282418bc366194677eafd1dad180d92254586ac'/>
<id>urn:sha1:b282418bc366194677eafd1dad180d92254586ac</id>
<content type='text'>
Implement suspend operation for vduse devices, so vhost-vdpa will offer
that backend feature and userspace can effectively suspend the device.

This is a must before get virtqueue indexes (base) for live migration,
since the device could modify them after userland gets them.

This patch does not implement resume, so VMM resets the whole device
to recover from a live migration failure.  Resume optimization can be
implemented on top of these patches, as other vDPA devices have done in
the past.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707123344.244575-3-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vduse: do not take rwsem at reset work flush</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:33:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=675087c762f95c498524164de7417f9f77d3ed15'/>
<id>urn:sha1:675087c762f95c498524164de7417f9f77d3ed15</id>
<content type='text'>
Next patches need to check suspend flag at this work item, and the
rwlock is used to protect the suspend flag update.  If the work takes
the rwlock too it will produce a deadlock.

Make flushing work do nothing when called by de-initializing everything:
vq-&gt;ready, vq-&gt;kickfd, vq-&gt;cb.callback.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707123344.244575-2-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vduse: add F_QUEUE_READY feature</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:25:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4c318d91cc60a0c2c94bcb6db2630baed43e9387'/>
<id>urn:sha1:4c318d91cc60a0c2c94bcb6db2630baed43e9387</id>
<content type='text'>
Add the VDUSE_F_QUEUE_READY feature flag. This allows the kernel module
to explicitly signal userspace when a specific virtqueue has been
enabled.

In scenarios like Live Migration of VirtIO net devices, the dataplane
starts after the control virtqueue allowing QEMU to apply configuration
in the destination device.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707122502.239022-5-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vduse: add VDUSE_SET_FEATURES ioctl</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:25:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3b441820cb61ac1137dd4b336adfb4892cda4233'/>
<id>urn:sha1:3b441820cb61ac1137dd4b336adfb4892cda4233</id>
<content type='text'>
Add an ioctl to allow VDUSE instances to set the VDUSE features
supported by the userland VDUSE instance.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707122502.239022-4-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vduse: add VDUSE_GET_FEATURES ioctl</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:25:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a596238c2ab6944861404dc597133ffd4ad062d5'/>
<id>urn:sha1:a596238c2ab6944861404dc597133ffd4ad062d5</id>
<content type='text'>
Add an ioctl to allow VDUSE instances to query the available features
supported by the kernel module.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707122502.239022-3-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vduse: store control device pointer</title>
<updated>2026-08-19T10:38:48+00:00</updated>
<author>
<name>Eugenio Pérez</name>
<email>eperezma@redhat.com</email>
</author>
<published>2026-07-07T12:24:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0ff906166f00ac7b2ccc36c57be6ad4be0dd9e90'/>
<id>urn:sha1:0ff906166f00ac7b2ccc36c57be6ad4be0dd9e90</id>
<content type='text'>
This helps log the errors in next patches.  The alternative is to
perform a linear search for it with class_find_device_by_devt(class, devt),
as device_destroy do for cleaning.

Signed-off-by: Eugenio Pérez &lt;eperezma@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260707122502.239022-2-eperezma@redhat.com&gt;
</content>
</entry>
<entry>
<title>vdpa: Remove redundant dev_err()</title>
<updated>2026-08-19T10:38:47+00:00</updated>
<author>
<name>Pan Chuang</name>
<email>panchuang@vivo.com</email>
</author>
<published>2026-07-16T14:13:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3e4cddec63db5dc5c199101df7ac0504975b1203'/>
<id>urn:sha1:3e4cddec63db5dc5c199101df7ac0504975b1203</id>
<content type='text'>
Since commit 55b48e23f5c4 ("genirq/devres: Add error handling in
devm_request_*_irq()"), devm_request_irq() automatically logs
detailed error messages on failure. Remove the now-redundant
driver-specific dev_err() calls.

Signed-off-by: Pan Chuang &lt;panchuang@vivo.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260716141349.158824-1-panchuang@vivo.com&gt;
</content>
</entry>
<entry>
<title>vdpa/mlx5: roll back MR update after VQ setup failure</title>
<updated>2026-08-19T10:38:47+00:00</updated>
<author>
<name>Weimin Xiong</name>
<email>xiongwm2026@163.com</email>
</author>
<published>2026-07-16T05:43:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=11f79e2780043ad94424a8db02a7a9022ba93252'/>
<id>urn:sha1:11f79e2780043ad94424a8db02a7a9022ba93252</id>
<content type='text'>
mlx5_vdpa_change_map() must install the new MR before rebuilding or
resuming virtqueues, because both paths read the MR keys from
mvdev-&gt;mres.mr[].

If rebuilding the virtqueue resources fails, the new MR must not remain
installed after its reference is released. Keep an extra reference to
the old MR before replacing it. On setup failure, restore the old MR;
the saved reference then becomes the map reference, while replacing the
new MR drops its map reference.

Make mlx5_vdpa_change_map() consume new_mr on all error paths so that
set_map_data() does not release an MR already released during rollback.

v2:
- Keep the new MR installed while virtqueues are rebuilt.
- Restore the old MR only after setup_vq_resources() fails.

Signed-off-by: Weimin Xiong &lt;xiongwm2026@163.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

Message-ID: &lt;20260716054353.155805-1-xiongwm2026@163.com&gt;
</content>
</entry>
<entry>
<title>vdpa/solidrun: fix typos in snet_ctrl comments</title>
<updated>2026-08-19T10:38:47+00:00</updated>
<author>
<name>xiongweimin</name>
<email>xiongweimin@kylinos.cn</email>
</author>
<published>2026-07-14T02:45:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9b38c0ff7b6d68b06c2b2363be5a8c374c713d7'/>
<id>urn:sha1:c9b38c0ff7b6d68b06c2b2363be5a8c374c713d7</id>
<content type='text'>
Correct "readind" and "the an error" in the DPU control path comments.

Signed-off-by: xiongweimin &lt;xiongweimin@kylinos.cn&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260714024527.188645-1-15927021679@163.com&gt;
</content>
</entry>
<entry>
<title>vdpa/mlx5: fix wrong MLX5_ADDR_OF struct type in alloc_inout()</title>
<updated>2026-08-19T10:38:47+00:00</updated>
<author>
<name>Li RongQing</name>
<email>lirongqing@baidu.com</email>
</author>
<published>2026-07-06T06:09:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2de85565762ebd3c6a7fb397cafdfcabb8cd8caa'/>
<id>urn:sha1:2de85565762ebd3c6a7fb397cafdfcabb8cd8caa</id>
<content type='text'>
In alloc_inout(), the qpc field offset was computed using
MLX5_ADDR_OF(rst2init_qp_in, ...) in both the INIT2RTR_QP and
RTR2RTS_QP cases. This is a copy-paste error: each case should use
its own input structure type to get the correct qpc offset.

Fix the INIT2RTR_QP case to use MLX5_ADDR_OF(init2rtr_qp_in, ...)
and the RTR2RTS_QP case to use MLX5_ADDR_OF(rtr2rts_qp_in, ...).

Signed-off-by: Li RongQing &lt;lirongqing@baidu.com&gt;
Reviewed-by: Dragos Tatulea &lt;dtatulea@nvidia.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Message-ID: &lt;20260706060902.2341-1-lirongqing@baidu.com&gt;
</content>
</entry>
</feed>
