From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935320AbeBMNWT (ORCPT ); Tue, 13 Feb 2018 08:22:19 -0500 Received: from 8bytes.org ([81.169.241.247]:36196 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935174AbeBMNWS (ORCPT ); Tue, 13 Feb 2018 08:22:18 -0500 Date: Tue, 13 Feb 2018 14:22:16 +0100 From: Joerg Roedel To: Gary R Hook Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] iommu/amd - Use dev_err to send events to the system log Message-ID: <20180213132216.gyhndywyu23cdzbv@8bytes.org> References: <151736066756.21649.4739957712713863861.stgit@sosam4> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <151736066756.21649.4739957712713863861.stgit@sosam4> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 30, 2018 at 07:04:27PM -0600, Gary R Hook wrote: > + dev_err(dev, "ILLEGAL_DEV_TABLE_ENTRY device=%02x:%02x.%x " > + "address=0x%016llx flags=0x%04x]\n", > + PCI_BUS_NUM(devid), PCI_SLOT(devid), PCI_FUNC(devid), > + address, flags); That prints the PCI device-name of the IOMMU in front of the message. Is that actually helpful? If at all, we should print the name of the iommu-device in front of the message, not the PCI device that hosts the IOMMU. Thanks, Joerg