aboutsummaryrefslogtreecommitdiff
path: root/hw
diff options
context:
space:
mode:
authorStefano Garzarella <sgarzare@redhat.com>2024-06-18 12:00:35 +0200
committerMichael S. Tsirkin <mst@redhat.com>2024-07-02 09:27:56 -0400
commit4c58843e5d3192c67394b28a3330144ea56eefac (patch)
tree0e12866de3389d23f69bdf03cad9ae50d1a4007f /hw
parentebdede644bbf5744f91dbe0d39742f17b03c4e10 (diff)
downloadqemu-4c58843e5d3192c67394b28a3330144ea56eefac.zip
qemu-4c58843e5d3192c67394b28a3330144ea56eefac.tar.gz
qemu-4c58843e5d3192c67394b28a3330144ea56eefac.tar.bz2
vhost-user-server: do not set memory fd non-blocking
In vhost-user-server we set all fd received from the other peer in non-blocking mode. For some of them (e.g. memfd, shm_open, etc.) it's not really needed, because we don't use these fd with blocking operations, but only to map memory. In addition, in some systems this operation can fail (e.g. in macOS setting an fd returned by shm_open() non-blocking fails with errno = ENOTTY). So, let's avoid setting fd non-blocking for those messages that we know carry memory fd (e.g. VHOST_USER_ADD_MEM_REG, VHOST_USER_SET_MEM_TABLE). Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Acked-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: David Hildenbrand <david@redhat.com> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com> Message-Id: <20240618100043.144657-6-sgarzare@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'hw')
0 files changed, 0 insertions, 0 deletions