Received: by 2002:a05:6a10:c7c6:0:0:0:0 with SMTP id h6csp1677672pxy; Mon, 2 Aug 2021 07:41:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/53hU96cvKcUcdTKiykpX3RCGNKfpWlw9Hunn5drZuxe08kWUVY8odRSkZwnxkOZcgsQq X-Received: by 2002:a5d:4392:: with SMTP id i18mr17687059wrq.231.1627915298701; Mon, 02 Aug 2021 07:41:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627915298; cv=none; d=google.com; s=arc-20160816; b=ebHnUgUhPdBvoyxExQJDjMh2kLW620OSL8VEe/S/0sjhV7rlt+0TaSQAPNFhGonU2g 9918NkcqmHBI/Z7kCu4wIIw9N9G5kltj3Uw7k885fR036fMbrk4A42FaFrcYlI9rAYVi KxZAd/uG5yhjMYb20DaAqpx7i1rqEC4XNGEnXAdIqFKZ8L6Kp8eJ7Vb4XWR/fq/awCI2 JxWK++CNBYnMB1HAbrZ8yRmVkZgS4Gjcqo4JufIlKwfVDXAQiSyEMnn6h3CgF4R6EDoR FC1uUUzisz2ODJbpTlVfi88iDM9JA7GnQg3B5WSe0ppHH7+lJ5Ocmh0k8VLyaS0yOkqm NUyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=Dw47TbeZYa3oPwXruz07cEMsTJUeWxY4Fp31K/fyTJs=; b=xZi60nVvTbsoTp5C2+NavCtB9Bv5aO8z7FpxAvmjBOm+ER/kVIrSFno0bxb8AVshXH /lv7/uJBMmuNhlgpprnahcAEh/S6WjNUCN5OaQHUv2TYm0Eg0J3QmM2sPYP5CI+N9or4 aDKg4rJ/zsvkE0XLxRM6CdLN42MVObL9jsjrqa09uwySW7qSQMjyyGvqMfSd/KrCt9LB Ys4eQY/eqd3epwcYoZ7fTGWeNui4Pf4qCO1sqnPIoYtRmIoPiVQdCWLFfrIa8MiPAgdr d442CY2EklKQ1rfGzEBgQDwJPl7hdWdLYTnwi6D5QSA9C7tTTFJmNNMI5BX7+dY/a3e9 kL5A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k1si11021271wrx.132.2021.08.02.07.41.15; Mon, 02 Aug 2021 07:41:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234343AbhHBOjR (ORCPT + 99 others); Mon, 2 Aug 2021 10:39:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50452 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233940AbhHBOjQ (ORCPT ); Mon, 2 Aug 2021 10:39:16 -0400 Received: from theia.8bytes.org (8bytes.org [IPv6:2a01:238:4383:600:38bc:a715:4b6d:a889]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29A6DC06175F for ; Mon, 2 Aug 2021 07:39:07 -0700 (PDT) Received: by theia.8bytes.org (Postfix, from userid 1000) id 358D5806; Mon, 2 Aug 2021 16:39:05 +0200 (CEST) Date: Mon, 2 Aug 2021 16:38:52 +0200 From: Joerg Roedel To: Luigi Rizzo Cc: Will Deacon , linux-kernel , David Rientjes , Luigi Rizzo , Suravee Suthikulpanit Subject: Re: [PATCH] amd/iommu: fix logic bug in amd_iommu_report_page_fault() Message-ID: References: <20210731192637.3653796-1-lrizzo@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 02, 2021 at 04:30:50PM +0200, Luigi Rizzo wrote: > Ah didn't realize that. Thank you! > > Two questions on the topic: > 1. how comes only the AMD driver is so verbose in reporting io page faults? > Neither intel nor other iommu drivers seem to log anything What do you mean by 'verbose'? It is only a line per fault, and at least the Intel driver also logs DMAR faults with one line per fault :) > 2. Would it make sense to have a control to disable such logging, > either per-device or globally? Eg something like this (negative > logic so it must be set explicitly to disable logging). Yes, we can talk about that. But only after the trace-event for it landed in the code. There must be some way to report the faults and if userspace prefers to catch them via trace-events than we can disable printing them to the kernel log. Regards, Joerg