Received: by 10.192.165.148 with SMTP id m20csp1791154imm; Thu, 3 May 2018 05:34:45 -0700 (PDT) X-Google-Smtp-Source: AB8JxZq8wwc653cKnP4aOvJjPnHe890FdfPL1DbYEHnTF+AONfrrqe4H3jXPmeMZooliUAqx8LXu X-Received: by 2002:a17:902:7795:: with SMTP id o21-v6mr3843959pll.36.1525350885334; Thu, 03 May 2018 05:34:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525350885; cv=none; d=google.com; s=arc-20160816; b=eEhX0p4YqdZC/2kb5IWDaEAjV8XZjHvJBWe6mHrevp1r6NhWKWx2ZVk3rJsoxazXWg 0nHNWqsMbaOteXNBI5p5SwE5RNHj78q7r14K8pHB6jSY+I6+JEHBTzjHVZDx/Uktiuv9 nEGcpkbgL8gLJn8RgP6f8liFk8PrgHHIvp2l0JCoZjdBbwRox4r/OX/ACXcRSKUHOFBz 9PjbhonV3cEgyPylYT7cI9Cf1ytXgKJHp0hn4q9GfD81YPSazA/OJMdZ4rTmLI0BFx1p aadJgyZDbLDpxNx7FHUsuJvUv6BtkZPm0LaSyHOIBg/Tkr3f2HVdPZy+edP25Rn8thwG 1ZJw== 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=qOy/6FS15aHP7Dfg2AR18lMJm/WvBpztRJNZMJkECVY=; b=G9TobM91Me628+ZSLNBw8x0hWSuyynN6RwGkMJhZmmgrVUASzoEIuJC7LuGUc3ol1i YP6xCBxQOtZUTU2j0gfMXZwUjJLiqISziNtvpCu3hI4wCQsntbKsu06n1/LH5kUdlKKv 9zT/rDEk8mU34Ddw6P6mvsbrYMLhGp0DPmRwT8Crjx+T+Xaa+6/zvjmM0irf6ppPjZif 6I589M1Zh6yQKyG1gc/LDta+8aE7pif9Snwjf+4ifLl5rmlkNhtehFkqYTK438waUy+/ tCP1GVxmgUosNCjJO637XMIEbmFHXr4EYKF1BxfJsdXn0RvbAGrjYqwBZzirWJDIL3Iz 5Wpw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e5-v6si5308192pgp.461.2018.05.03.05.34.31; Thu, 03 May 2018 05:34:45 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751495AbeECMeY (ORCPT + 99 others); Thu, 3 May 2018 08:34:24 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:47826 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750999AbeECMeX (ORCPT ); Thu, 3 May 2018 08:34:23 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E826A818B10C; Thu, 3 May 2018 12:34:22 +0000 (UTC) Received: from localhost (ovpn-116-71.ams2.redhat.com [10.36.116.71]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5E62B83B79; Thu, 3 May 2018 12:34:20 +0000 (UTC) Date: Thu, 3 May 2018 10:06:52 +0100 From: Stefan Hajnoczi To: Tiwei Bie Cc: mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, dan.daly@intel.com, cunming.liang@intel.com, zhihong.wang@intel.com Subject: Re: [RFC] virtio: support VIRTIO_F_IO_BARRIER Message-ID: <20180503090652.GB5301@stefanha-x1.localdomain> References: <20180503025955.28816-1-tiwei.bie@intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qlTNgmc+xy1dBmNv" Content-Disposition: inline In-Reply-To: <20180503025955.28816-1-tiwei.bie@intel.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Thu, 03 May 2018 12:34:22 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Thu, 03 May 2018 12:34:22 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'stefanha@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --qlTNgmc+xy1dBmNv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 03, 2018 at 10:59:55AM +0800, Tiwei Bie wrote: > This patch introduces the support for VIRTIO_F_IO_BARRIER. > When this feature is negotiated, driver will use the barriers > suitable for hardware devices. >=20 > Signed-off-by: Tiwei Bie I should have thought of this earlier, but why is a new feature bit necessary? If a hardware virtio device is in use, then the device should already negotiate VIRTIO_F_IOMMU_PLATFORM (i.e. use DMA APIs and IOMMU callbacks). Does disabling weak_barriers when VIRTIO_F_IOMMU_PLATFORM is set solve the problem? --qlTNgmc+xy1dBmNv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJa6tEsAAoJEJykq7OBq3PId/QIALdwBH9xWwEQVvM6d304pF6L xzcV8Swsp88sZDWASg+U4bAHqwEu7GHZV8uL5D7cL0wj/GzosiL8UXg5gRMbCewJ +WqmRO650s3yMrYWkSODwIVA1ecJ4z7ij43NCVFDYn2INVec5PbVxW0lDgtCG0KD +EU5IWUK4JMU25x4f+mQSYQkrsV89msupTw/qdxF634+qHitlj79JOL4ZmcvmOg6 DrSD11OXbpKDi8KEOJb+9KJ1ky69L9xUn29Me5YMK3mYbfte1kZYLSzE4JvQmKHS Rf68rErinhJeAxDU4txxaIb2jOq3dUwqSQLuj5MjtNf4KhJbSB3A+BkZHSY4HM0= =X31/ -----END PGP SIGNATURE----- --qlTNgmc+xy1dBmNv--