From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id DA31098606D for ; Wed, 11 Aug 2021 10:05:58 +0000 (UTC) Date: Wed, 11 Aug 2021 15:35:50 +0530 From: Srivatsa Vaddagiri Message-ID: <20210811100550.GC21582@quicinc.com> Reply-To: Srivatsa Vaddagiri References: <87h7gh5od5.fsf@redhat.com> <87eebl5msn.fsf@redhat.com> <20210726091851-mutt-send-email-mst@kernel.org> <20210726141737-mutt-send-email-mst@kernel.org> <09b74816-8a1e-f993-640f-eb790a4a4698@redhat.com> MIME-Version: 1.0 In-Reply-To: <09b74816-8a1e-f993-640f-eb790a4a4698@redhat.com> Subject: Re: [virtio-dev] Re: [PATCH v1] virtio-mmio: Specify wait needed in driver during reset Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline To: Jason Wang Cc: "Michael S. Tsirkin" , Srivatsa Vaddagiri , Cornelia Huck , "virtio-dev@lists.oasis-open.org" , Trilok Soni , Pratik Patel List-ID: * Jason Wang [2021-08-02 14:06:38]: > >Maybe if it sees status was not read it can just > >stay in reset state and not exit it? > > > > > > Or I wonder we can use increase the version instead. What should be the guidance for backend/devices here? Go with version 3 only if it requires driver to poll on reset? Otherwise it may break existing setups - lets say Qemu is updated to report version 3 which will break older guest images that understood version 2 - this is despite the same Qemu being capable of serving those guests. - vatsa --- Qualcomm Innovation Center, Inc. is submitting the attached "feedback" as a non-member to the virtio-dev mailing list for consideration and inclusion. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org