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 6239641B91; Tue, 31 Jan 2023 18:09:04 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4449F4067B; Tue, 31 Jan 2023 18:09:04 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 30CBE40041 for ; Tue, 31 Jan 2023 18:09:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675184941; 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: in-reply-to:in-reply-to:references:references; bh=36rJJ2HXg1fDYT9zEbJ+SfHqVIzxCLWxgQLLbYR3hP4=; b=Blt7MPvl6hyxA2kJCCsq6m40yvgSyNS/csWttgf+4Os2Ju1+kTB/4+Wivbtn9Ie0TMOhzU GNU1h7qOefCLjnn0HQOamSA2UEjQwdaqlNl6LyOMxqgjaACZt9dEmb1BUiot++1px4zVoH SloEfEXNqPqacEzgLULF2/2gErJ512k= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-584-uZhycLs2OM6Zg2oHI-sPuQ-1; Tue, 31 Jan 2023 12:08:58 -0500 X-MC-Unique: uZhycLs2OM6Zg2oHI-sPuQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A3F7938173D3; Tue, 31 Jan 2023 17:08:57 +0000 (UTC) Received: from [10.39.208.22] (unknown [10.39.208.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3A87E40ED76B; Tue, 31 Jan 2023 17:08:56 +0000 (UTC) Message-ID: <287f84e5-ec79-868a-384d-501bb5673987@redhat.com> Date: Tue, 31 Jan 2023 18:08:54 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: [PATCH v4 8/9] vhost: annotate vDPA device list accesses To: David Marchand , dev@dpdk.org Cc: stephen@networkplumber.org, chenbo.xia@intel.com, jiayu.hu@intel.com, yuanx.wang@intel.com, xuan.ding@intel.com References: <20220328121758.26632-1-david.marchand@redhat.com> <20230119184620.3195267-1-david.marchand@redhat.com> <20230119184620.3195267-9-david.marchand@redhat.com> From: Maxime Coquelin In-Reply-To: <20230119184620.3195267-9-david.marchand@redhat.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 On 1/19/23 19:46, David Marchand wrote: > Access to vdpa_device_list must be protected with vdpa_device_list_lock > spinlock. > > Signed-off-by: David Marchand > --- > Changes since RFC v3: > - rebased, > > --- > lib/vhost/vdpa.c | 19 ++++++++++--------- > 1 file changed, 10 insertions(+), 9 deletions(-) > Reviewed-by: Maxime Coquelin Thanks, Maxime