From: "joro@8bytes.org" <joro@8bytes.org>
To: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Joerg Roedel <jroedel@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iommu: amd: Fix incorrect PASID decoding from event log
Date: Tue, 15 Oct 2019 14:14:24 +0200 [thread overview]
Message-ID: <20191015121424.GM14518@8bytes.org> (raw)
In-Reply-To: <1571083556-105953-1-git-send-email-suravee.suthikulpanit@amd.com>
On Mon, Oct 14, 2019 at 08:06:05PM +0000, Suthikulpanit, Suravee wrote:
> IOMMU Event Log encodes 20-bit PASID for events:
> ILLEGAL_DEV_TABLE_ENTRY
> IO_PAGE_FAULT
> PAGE_TAB_HARDWARE_ERROR
> INVALID_DEVICE_REQUEST
> as:
> PASID[15:0] = bit 47:32
> PASID[19:16] = bit 19:16
>
> Note that INVALID_PPR_REQUEST event has different encoding
> from the rest of the events as the following:
> PASID[15:0] = bit 31:16
> PASID[19:16] = bit 45:42
>
> So, fixes the decoding logic.
>
> Fixes: d64c0486ed50 ("iommu/amd: Update the PASID information printed to the system log")
> Cc: Joerg Roedel <jroedel@suse.de>
> Cc: Gary R Hook <gary.hook@amd.com>
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> ---
> drivers/iommu/amd_iommu.c | 5 +++--
> drivers/iommu/amd_iommu_types.h | 4 ++--
> 2 files changed, 5 insertions(+), 4 deletions(-)
Applied for v5.4, thanks Suravee.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: "joro@8bytes.org" <joro@8bytes.org>
To: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
Joerg Roedel <jroedel@suse.de>, "Hook, Gary" <Gary.Hook@amd.com>
Subject: Re: iommu: amd: Fix incorrect PASID decoding from event log
Date: Tue, 15 Oct 2019 14:14:24 +0200 [thread overview]
Message-ID: <20191015121424.GM14518@8bytes.org> (raw)
In-Reply-To: <1571083556-105953-1-git-send-email-suravee.suthikulpanit@amd.com>
On Mon, Oct 14, 2019 at 08:06:05PM +0000, Suthikulpanit, Suravee wrote:
> IOMMU Event Log encodes 20-bit PASID for events:
> ILLEGAL_DEV_TABLE_ENTRY
> IO_PAGE_FAULT
> PAGE_TAB_HARDWARE_ERROR
> INVALID_DEVICE_REQUEST
> as:
> PASID[15:0] = bit 47:32
> PASID[19:16] = bit 19:16
>
> Note that INVALID_PPR_REQUEST event has different encoding
> from the rest of the events as the following:
> PASID[15:0] = bit 31:16
> PASID[19:16] = bit 45:42
>
> So, fixes the decoding logic.
>
> Fixes: d64c0486ed50 ("iommu/amd: Update the PASID information printed to the system log")
> Cc: Joerg Roedel <jroedel@suse.de>
> Cc: Gary R Hook <gary.hook@amd.com>
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> ---
> drivers/iommu/amd_iommu.c | 5 +++--
> drivers/iommu/amd_iommu_types.h | 4 ++--
> 2 files changed, 5 insertions(+), 4 deletions(-)
Applied for v5.4, thanks Suravee.
next prev parent reply other threads:[~2019-10-15 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 20:06 iommu: amd: Fix incorrect PASID decoding from event log Suthikulpanit, Suravee
2019-10-14 20:06 ` Suthikulpanit, Suravee
2019-10-15 12:14 ` joro [this message]
2019-10-15 12:14 ` joro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191015121424.GM14518@8bytes.org \
--to=joro@8bytes.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.