From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-4329-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [66.179.20.138]) by lists.oasis-open.org (Postfix) with ESMTP id 0A0C51CB80ED for ; Mon, 11 Jun 2018 00:50:35 -0700 (PDT) Date: Mon, 11 Jun 2018 15:50:31 +0800 From: Tiwei Bie Message-ID: <20180611075031.GA18161@debian> References: <20180608065928.2456-1-tiwei.bie@intel.com> <20180608093617.3fc9b951.cohuck@redhat.com> <20180608190440-mutt-send-email-mst@kernel.org> <20180611091100.7a828d00.cohuck@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180611091100.7a828d00.cohuck@redhat.com> Subject: [virtio-dev] Re: [PATCH] content: enhance device requirements for feature bits To: Cornelia Huck , "Michael S. Tsirkin" Cc: stefanha@redhat.com, pbonzini@redhat.com, virtio-dev@lists.oasis-open.org, dan.daly@intel.com, cunming.liang@intel.com, zhihong.wang@intel.com List-ID: On Mon, Jun 11, 2018 at 09:11:00AM +0200, Cornelia Huck wrote: > On Fri, 8 Jun 2018 19:05:30 +0300 > "Michael S. Tsirkin" wrote: > > > On Fri, Jun 08, 2018 at 09:36:17AM +0200, Cornelia Huck wrote: > > > On Fri, 8 Jun 2018 14:59:28 +0800 > > > Tiwei Bie wrote: > > > > > > > Suggested-by: Michael S. Tsirkin > > > > Signed-off-by: Tiwei Bie > > > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/14 > > > > --- > > > > content.tex | 7 +++++++ > > > > 1 file changed, 7 insertions(+) > > > > > > > > diff --git a/content.tex b/content.tex > > > > index f996fad..8374d3f 100644 > > > > --- a/content.tex > > > > +++ b/content.tex > > > > @@ -125,6 +125,13 @@ which was not offered. The device SHOULD accept any valid subset > > > > of features the driver accepts, otherwise it MUST fail to set the > > > > FEATURES_OK \field{device status} bit when the driver writes it. > > > > > > > > +If a device has successfully negotiated a set of features > > > > +at least once (by setting the FEATURES_OK \field{device > > > > +status} bit when the driver writes it), then it SHOULD NOT > > > > > > Hm, it's the driver that sets FEATURES_OK, not the device. What about > > > "by succeeding to set"? > > > > I think the best terminology we have is > > "accept the FEATURES_OK status bit during device initialization" > > that's from the mmio chapter. > > Yes, that sounds better. I'll send a new version! Best regards, Tiwei Bie > > > > > > > +fail re-negotiation of the same set of features after a > > > > +device or system reset. Failure to do so would interfere > > > > +with the resuming from suspend and error recovery. > > > > > > s/the resuming/resuming/ > > > > > > > + > > > > \subsection{Legacy Interface: A Note on Feature > > > > Bits}\label{sec:Basic Facilities of a Virtio Device / Feature > > > > Bits / Legacy Interface: A Note on Feature Bits} > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org