From: Suravee Suthikulpanit via iommu <iommu@lists.linux-foundation.org>
To: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Cc: jon.grimm@amd.com, vasant.hegde@amd.com
Subject: Re: [PATCH] iommu/amd: Set translation valid bit only when IO page tables are in used
Date: Fri, 29 Apr 2022 00:16:24 +0700 [thread overview]
Message-ID: <015d68dc-aa38-1823-68ab-f66d78124d13@amd.com> (raw)
In-Reply-To: <20220420112920.18091-1-suravee.suthikulpanit@amd.com>
On 4/20/22 6:29 PM, Suravee Suthikulpanit wrote:
> On AMD system with SNP enabled, IOMMU hardware checks the host translation
> valid (TV) and guest translation valid (GV) bits in the device
> table entry (DTE) before accessing the corresponded page tables.
>
> However, current IOMMU driver sets the TV bit for all devices
> regardless of whether the host page table is in used.
> This results in ILLEGAL_DEV_TABLE_ENTRY event for devices, which
> do not the host page table root pointer set up.
>
> Thefore, only set TV bit when host or guest page tables are in used.
>
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>
I found a bug in this patch. I will send out v2 with the fix.
Regards,
Suravee
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2022-04-28 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:29 [PATCH] iommu/amd: Set translation valid bit only when IO page tables are in used Suravee Suthikulpanit via iommu
2022-04-28 7:34 ` Vasant Hegde via iommu
2022-04-28 17:16 ` Suravee Suthikulpanit via iommu [this message]
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=015d68dc-aa38-1823-68ab-f66d78124d13@amd.com \
--to=iommu@lists.linux-foundation.org \
--cc=jon.grimm@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox