From nobody Sat May 4 19:40:04 2024 Delivered-To: importer@patchew.org Received-SPF: temperror (zoho.com: Error in retrieving data from DNS) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=temperror (zoho.com: Error in retrieving data from DNS) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 155364165433378.26506868467345; Tue, 26 Mar 2019 16:07:34 -0700 (PDT) Received: from localhost ([127.0.0.1]:39168 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8vAC-0002zz-8p for importer@patchew.org; Tue, 26 Mar 2019 19:07:24 -0400 Received: from eggs.gnu.org ([209.51.188.92]:47535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8v8f-0002N7-EK for qemu-devel@nongnu.org; Tue, 26 Mar 2019 19:05:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8v8e-0004h4-Ih for qemu-devel@nongnu.org; Tue, 26 Mar 2019 19:05:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55688) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h8v8e-0004g8-9w; Tue, 26 Mar 2019 19:05:48 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9C8663007C28; Tue, 26 Mar 2019 23:05:47 +0000 (UTC) Received: from gimli.home (ovpn-116-99.phx2.redhat.com [10.3.116.99]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4751E4DC56; Tue, 26 Mar 2019 23:05:39 +0000 (UTC) From: Alex Williamson To: qemu-devel@nongnu.org Date: Tue, 26 Mar 2019 17:05:38 -0600 Message-ID: <155364147432.16467.15898335025013220939.stgit@gimli.home> User-Agent: StGit/0.19-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Tue, 26 Mar 2019 23:05:47 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH] intel_iommu: Correct caching-mode error message X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: ehabkost@redhat.com, mst@redhat.com, qemu-trivial@nongnu.org, peterx@redhat.com, pbonzini@redhat.com, rth@twiddle.net Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" If we try to use the intel-iommu device with vfio-pci devices without caching mode enabled, we're told: qemu-system-x86_64: We need to set caching-mode=3D1 for intel-iommu to en= able device assignment with IOMMU protection. But to enable caching mode, the option is actually "caching-mode=3Don". Signed-off-by: Alex Williamson Reviewed-by: Eric Auger Reviewed-by: Laurent Vivier Reviewed-by: Peter Xu Reviewed-by: Philippe Mathieu-Daud=C3=A9 --- hw/i386/intel_iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c index b90de6c66461..b62badd4f08d 100644 --- a/hw/i386/intel_iommu.c +++ b/hw/i386/intel_iommu.c @@ -2919,7 +2919,7 @@ static void vtd_iommu_notify_flag_changed(IOMMUMemory= Region *iommu, IntelIOMMUState *s =3D vtd_as->iommu_state; =20 if (!s->caching_mode && new & IOMMU_NOTIFIER_MAP) { - error_report("We need to set caching-mode=3D1 for intel-iommu to e= nable " + error_report("We need to set caching-mode=3Don for intel-iommu to = enable " "device assignment with IOMMU protection."); exit(1); }