Received: by 10.192.165.148 with SMTP id m20csp969277imm; Thu, 10 May 2018 03:40:41 -0700 (PDT) X-Google-Smtp-Source: AB8JxZog73sudCsu7XufhDall31c2cn+NORhop0wcdXqZl/TQNAcVzbDCzPBI7vOUPvCffX1rre5 X-Received: by 2002:a17:902:43:: with SMTP id 61-v6mr901803pla.112.1525948841115; Thu, 10 May 2018 03:40:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525948841; cv=none; d=google.com; s=arc-20160816; b=cFKYDnLuSUzLR+LIfhKiDjjeLYOHJqtrNJ3CSnmgXb+u95emVa6II4MWnRODvM5zsk TCZ3l+5IBQ3LEEO9IbARAvYnX/N4gkn3hHCEHUCkvL09uXDIO4lZLjKgJ3aDPUuHVa1p rrOxgljdp769DACRuoucmp+n6ZSiiq+nicUDuJFbtY2LOD8acv+U4Z/v3K18MO+cnDoc nsGlz1nrvdffxZUSKz6+mc0lQW8envm16fS9d89n+GHLko38Cu3U6DgzGEn0GCv58Gbd VPkfzX6adWAeiLVKKDtzSAm58yAI60uZt3HPT2aG+HJ6LnjKBQxoprD8ME/k4pyrk1In lEQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=4jGWpJ4tf6dF0vQL93E8odgH7N1QsddPweII5s5+8GE=; b=IYVbKSyMmsdgKXTY5VU9zxd952e70EKV8CvkBv2+cywIk0ol8aqBXq+U8G6ijpv3AN vFTRWFvu+WrTBDt0z5SCk2pHtdniHRaewDePEjo8de7D0kGP728qs+u4y4E6sUCPSiLl EKh1IGwzbRh96V0ZFkfmWuGh90e/dQWc+1TW9NrCiBBW7yuQ+G8jO82vRIAnpFxNIdt/ IxdoQdGn/oI+3pJUIohubFSr697NWptovM/o3Nrj/6Bm8jZTFzbbnbDpY/CyH8NpvDEf xDivwt6T7jp/gSvKWBxv87NsHLGzo97mYeXh19rEH0s2qbZ3OdfrU36a+USGIfL/cqNU Cwdg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h91-v6si496058pld.559.2018.05.10.03.40.27; Thu, 10 May 2018 03:40:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757071AbeEJKjL (ORCPT + 99 others); Thu, 10 May 2018 06:39:11 -0400 Received: from mga12.intel.com ([192.55.52.136]:28913 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756780AbeEJKjK (ORCPT ); Thu, 10 May 2018 06:39:10 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 03:39:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,385,1520924400"; d="scan'208";a="227341512" Received: from debian.sh.intel.com (HELO debian) ([10.67.104.164]) by fmsmga005.fm.intel.com with ESMTP; 10 May 2018 03:39:08 -0700 Date: Thu, 10 May 2018 18:39:41 +0800 From: Tiwei Bie To: Stefan Hajnoczi Cc: mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, virtio-dev@lists.oasis-open.org, dan.daly@intel.com, cunming.liang@intel.com, zhihong.wang@intel.com Subject: Re: [PATCH v1] virtio: support VIRTIO_F_IO_BARRIER Message-ID: <20180510103941.znxka65iluybktuq@debian> References: <20180504045915.17693-1-tiwei.bie@intel.com> <20180510095317.GO1296@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180510095317.GO1296@stefanha-x1.localdomain> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 10, 2018 at 10:53:17AM +0100, Stefan Hajnoczi wrote: > On Fri, May 04, 2018 at 12:59:15PM +0800, Tiwei Bie wrote: > > diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h > > index 308e2096291f..9fb519a9df28 100644 > > --- a/include/uapi/linux/virtio_config.h > > +++ b/include/uapi/linux/virtio_config.h > > @@ -49,7 +49,7 @@ > > * transport being used (eg. virtio_ring), the rest are per-device feature > > * bits. */ > > #define VIRTIO_TRANSPORT_F_START 28 > > -#define VIRTIO_TRANSPORT_F_END 34 > > +#define VIRTIO_TRANSPORT_F_END 37 > > Have you updated "2.2 Feature Bits" in the VIRTIO spec? > > In 1.0 it says: > > 24 to 32 > Feature bits reserved for extensions to the queue and feature negotiation mechanisms > > This information is out-of-date. > No. In the latest spec draft, it's 24 to 33. And it becomes out-of-date since VIRTIO_F_RING_PACKED(34) and VIRTIO_F_IN_ORDER(35) were introduced. Do you want me to update it in the IO_BARRIER patch or do you want me to update it in a new patch? Best regards, Tiwei Bie