From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 206CC43C90; Tue, 12 Mar 2024 11:49:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C9A5040DCE; Tue, 12 Mar 2024 11:48:59 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id E1ED0402D8 for ; Tue, 12 Mar 2024 11:48:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710240537; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Zk5iXu/sbDyVvRCl7K9dh9ssFogSWvo2QQDE/ilBINs=; b=YezDo4CjxqwoBlUqDI1NtTDpdE5ymlPYqRcYTpjAkJ7f0m8SZ1NCV62aX90RDPlbQ852G2 cntuZ6hAoGjqxNlK9g6LLyua4HUyPh78716o4w/c4WctzpF7qbyQ8lmuvK2YZHOB4knF+g Qcqwu9DRltXaMCQTdEG2K7vpeqLW60M= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-163-wQLlcY1ROpKw8D1gFTwo_A-1; Tue, 12 Mar 2024 06:48:54 -0400 X-MC-Unique: wQLlcY1ROpKw8D1gFTwo_A-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E855C8007A2; Tue, 12 Mar 2024 10:48:53 +0000 (UTC) Received: from max-p1.redhat.com (unknown [10.39.208.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id CEBB6C478A0; Tue, 12 Mar 2024 10:48:51 +0000 (UTC) From: Maxime Coquelin To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com, schalla@marvell.com Cc: Maxime Coquelin Subject: [PATCH 0/2] net/virtio: vhost-vdpa fixes Date: Tue, 12 Mar 2024 11:48:47 +0100 Message-ID: <20240312104849.667036-1-maxime.coquelin@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org While investigating vhost-vdpa intialization issue with mlx5 vDPA, we found two issues fixed by following patches. Note we still see issue with the control queue, the virtio_user driver gets stuck while waiting for a control queue message reply. This is being investigated, but I wonder whether it is reproduced on Marvell vDPA device? Maxime Coquelin (2): net/virtio: fix vDPA device init advertising control queue net/virtio: fix notification area initialization drivers/net/virtio/virtio_user/virtio_user_dev.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) -- 2.44.0