| commit | d93e839ccd26ac95650fe31e45c91394936ddc27 | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 11 May 2022 07:40:35 +0000 (11 09:40 +0200) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Thu, 12 May 2022 10:29:44 +0000 (12 12:29 +0200) | ||
| tree | 119be71067a1fd78a30658fefe7c15e856373443 | treesnapshot (tar.gz zip) |
| parent | f0d43b1ecef04105e0d0f55658182510b4e0f58e | commitdiff |
vhost-backend: do not depend on CONFIG_VHOST_VSOCK
The vsock callbacks .vhost_vsock_set_guest_cid and
.vhost_vsock_set_running are the only ones to be conditional
on #ifdef CONFIG_VHOST_VSOCK. This is different from any other
device-dependent callbacks like .vhost_scsi_set_endpoint, and it
also broke when CONFIG_VHOST_VSOCK was changed to a per-target
symbol.
It would be possible to also use the CONFIG_DEVICES include, but
really there is no reason for most virtio files to be per-target
so just remove the #ifdef to fix the issue.
Reported-by: Dov Murik <dovmurik@linux.ibm.com>
Fixes: 9972ae314f ("build: move vhost-vsock configuration to Kconfig")
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
The vsock callbacks .vhost_vsock_set_guest_cid and
.vhost_vsock_set_running are the only ones to be conditional
on #ifdef CONFIG_VHOST_VSOCK. This is different from any other
device-dependent callbacks like .vhost_scsi_set_endpoint, and it
also broke when CONFIG_VHOST_VSOCK was changed to a per-target
symbol.
It would be possible to also use the CONFIG_DEVICES include, but
really there is no reason for most virtio files to be per-target
so just remove the #ifdef to fix the issue.
Reported-by: Dov Murik <dovmurik@linux.ibm.com>
Fixes: 9972ae314f ("build: move vhost-vsock configuration to Kconfig")
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| hw/virtio/vhost-backend.c | diffblobblamehistory |