From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751174AbeECN5K (ORCPT ); Thu, 3 May 2018 09:57:10 -0400 Received: from 8bytes.org ([81.169.241.247]:55262 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750922AbeECN5J (ORCPT ); Thu, 3 May 2018 09:57:09 -0400 Date: Thu, 3 May 2018 15:57:07 +0200 From: Joerg Roedel To: Gary R Hook Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] iommu/amd - Update the PASID information printed to the system log Message-ID: <20180503135706.nypxlwlt7jhqhhum@8bytes.org> References: <152520429853.30928.9793486018349326103.stgit@taos> <152520437211.30928.8410126837908568791.stgit@taos> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <152520437211.30928.8410126837908568791.stgit@taos> 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, May 01, 2018 at 02:52:52PM -0500, Gary R Hook wrote: > @@ -567,7 +567,7 @@ static void iommu_print_event(struct amd_iommu *iommu, void *__evt) > } > > if (type == EVENT_TYPE_IO_FAULT) { > - amd_iommu_report_page_fault(devid, domid, address, flags); > + amd_iommu_report_page_fault(devid, pasid, address, flags); According to the spec this could be a domid or a pasid, it would be good to make that visible in the error message, depending on the value of the GN flag in the event entry. But that can be done in a separate patch, I applied these two, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 1/2] iommu/amd - Update the PASID information printed to the system log Date: Thu, 3 May 2018 15:57:07 +0200 Message-ID: <20180503135706.nypxlwlt7jhqhhum@8bytes.org> References: <152520429853.30928.9793486018349326103.stgit@taos> <152520437211.30928.8410126837908568791.stgit@taos> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <152520437211.30928.8410126837908568791.stgit@taos> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Gary R Hook Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Tue, May 01, 2018 at 02:52:52PM -0500, Gary R Hook wrote: > @@ -567,7 +567,7 @@ static void iommu_print_event(struct amd_iommu *iommu, void *__evt) > } > > if (type == EVENT_TYPE_IO_FAULT) { > - amd_iommu_report_page_fault(devid, domid, address, flags); > + amd_iommu_report_page_fault(devid, pasid, address, flags); According to the spec this could be a domid or a pasid, it would be good to make that visible in the error message, depending on the value of the GN flag in the event entry. But that can be done in a separate patch, I applied these two, thanks.