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 D4062A0C43; Tue, 28 Sep 2021 17:31:24 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C0F6B410DB; Tue, 28 Sep 2021 17:31:24 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id E1396410D7 for ; Tue, 28 Sep 2021 17:31:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632843083; 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=XZlZs1JpBPOdzrUuR3CQ+qkBrZeZSx1ZFfxfx8nJXSI=; b=idKcNko+h3DiFy+viUsLiSXezYrPQuXbJtLDekEK7wX2+eDzaMTLN9QYhVjC32tIHOgUxL OU5F725TLX0LMNXy/FSec5yTKzm6w5EMNPOBYJpsSqCH51Zeumf+cYKM+k7sqFVqkpYPsV po2mOn06F4iLTCNOwKLy5TQq+FG+Ar0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-333-mJCEZN6uMPSW1dG5aB9sAA-1; Tue, 28 Sep 2021 11:31:19 -0400 X-MC-Unique: mJCEZN6uMPSW1dG5aB9sAA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A9D9C8E4AAD; Tue, 28 Sep 2021 15:31:18 +0000 (UTC) Received: from [10.39.208.26] (unknown [10.39.208.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AB837604CC; Tue, 28 Sep 2021 15:31:17 +0000 (UTC) Message-ID: <5e4c9794-048f-c6f0-acc9-6657cc846398@redhat.com> Date: Tue, 28 Sep 2021 17:31:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 To: Xueming Li , dev@dpdk.org Cc: Andrew Rybchenko , Chenbo Xia References: <20210823063906.1382544-1-xuemingl@nvidia.com> <20210915101204.81754-1-xuemingl@nvidia.com> From: Maxime Coquelin In-Reply-To: <20210915101204.81754-1-xuemingl@nvidia.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com 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 Subject: Re: [dpdk-dev] [PATCH v2] net/virtio: wait device ready during reset 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 Sender: "dev" On 9/15/21 12:12, Xueming Li wrote: > According to virtio spec, the device MUST reset when 0 is written to > device_status, and present 0 in device_status once reset is done. > > This patch waits status value to be 0 during reset operation, if > timeout in 3 seconds, log and continue. > > Signed-off-by: Xueming Li > Cc: Andrew Rybchenko > --- > drivers/net/virtio/virtio.c | 15 +++++++++++++-- > 1 file changed, 13 insertions(+), 2 deletions(-) > Applied to dpdk-next-virtio/main. Thanks, Maxime