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 44E99A0542; Tue, 5 Jul 2022 12:53:27 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D01344021D; Tue, 5 Jul 2022 12:53:26 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 81637400D7; Tue, 5 Jul 2022 12:53:25 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2AB085C011B; Tue, 5 Jul 2022 06:53:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 05 Jul 2022 06:53:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1657018403; x= 1657104803; bh=wqtb9u5hGjeHV3ZfreHWRLesM4dg/b2MUpxZO+TkkmA=; b=a Zcdw/b+8/EAjVmdCUz0hxtZcaBWupoQd7RcLZGJyMUcl0RFEyh/AgfqBLkVZc9eo rUpO3oJ07UN91ra7GUt6MyFxJzcP/NLUoP4QOsNFG+LOFFQuPmDhYalQStKsnbJI hgYk7GUNYCawoTUjBy/V2zkks/F1kNpuV+wj/d6R6/XK5eQQ4vLa5lxEfLkA0AHj kQ0iV9cL9zM7168n+EsPJlpKxpPxfZrz5rQPxc7VOH0flJcYxJSfqRoq5s5rn6TZ MJ0wE0Dv4MHSfZ/cTOFDb7US+IGz3jRVxQ5IO6cd9NSdQ3vZni9alHuE0+VnzW+N YyHnFJ3jzsjASN0DqgkWA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1657018403; x= 1657104803; bh=wqtb9u5hGjeHV3ZfreHWRLesM4dg/b2MUpxZO+TkkmA=; b=O nvzpYVtcJbOYNpo/VnX5EkGUuR+1cKauLttVJx8oTWdeSWXSuC/Wxy51+YoMkjlH L0bzwdDjinKEnc6QHXuxJkuzcX95zZC2nk3NKlMq2XevqJZsTPNiz/u6dBqHYify 1Q4b5WWLsY/eVHhvP3kpFYPVE2yUoWVC5TECzRFFZUeLEkXFANgcCJrFe17aip0T cc+1nL1rSOGHAUY63h9Au6829xf+8ynOfsBna6ofFhq2hDLX1oErivgw0cxCqmiF o9nZY/TyDC8OO6VRqPQ9oJT1URrANbUNHZ6rF1nWaNWS2qEPt/hFFZBbjZh131m3 niSRG0lTPBJQ69SvrwK7g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeiuddgfeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 5 Jul 2022 06:53:21 -0400 (EDT) From: Thomas Monjalon To: Yuan Wang , David Marchand Cc: stable@dpdk.org, Maxime Coquelin , "Xia, Chenbo" , dev , Jiayu Hu , "He, Xingguang" , Cheng Jiang , Harman Kalra , dpdk stable Subject: Re: [PATCH] net/virtio-user: restore callfds index for Rx interrupts Date: Tue, 05 Jul 2022 12:53:19 +0200 Message-ID: <33172877.6xKfjbll68@thomas> In-Reply-To: References: <20220704070428.2051264-1-yuanx.wang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 04/07/2022 09:42, David Marchand: > On Mon, Jul 4, 2022 at 9:11 AM Yuan Wang wrote: > > > > The callfds[] array stores eventfds sequentially for Rx and Tx vq. > > > > Fixes: d61138d4f0e2 ("drivers: remove direct access to interrupt handle") > > Cc: stable@dpdk.org > > > > Signed-off-by: Yuan Wang > > Good catch... > > This is what I had fixed in 848e93d9001e ("net/virtio-user: fix Rx > interrupts with multi-queue"). > I suppose the issue has been reintroduced when rebasing Harman series. Then we can re-use your commit title which better convey what is fixed from a user perspective: net/virtio-user: fix Rx interrupts with multi-queue