From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
joro@8bytes.org, robin.murphy@arm.com, vasant.hegde@amd.com,
kevin.tian@intel.com, jon.grimm@amd.com, santosh.shukla@amd.com,
pandoh@google.com, kumaranand@google.com
Subject: Re: [PATCH v4 2/6] iommu/amd: Introduce helper function to update 256-bit DTE
Date: Thu, 3 Oct 2024 23:15:53 +0700 [thread overview]
Message-ID: <fc5b7217-49b5-4ca0-b4f7-0eab5000a2e4@amd.com> (raw)
In-Reply-To: <20240926194607.GP9417@nvidia.com>
On 9/27/2024 2:46 AM, Jason Gunthorpe wrote:
> On Mon, Sep 16, 2024 at 05:18:01PM +0000, Suravee Suthikulpanit wrote:
>
> ....
>
>> + if (!(ptr->data[0] & DTE_FLAG_V)) {
>> + /* Existing DTE is not valid. */
>> + write_upper(ptr, new);
>> + write_lower(ptr, new);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> + } else if (!(new->data[0] & DTE_FLAG_V)) {
>> + /* Existing DTE is valid. New DTE is not valid. */
>> + write_lower(ptr, new);
>> + write_upper(ptr, new);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> + } else {
>> + /* Existing & new DTEs are valid. */
>> + if (!FIELD_GET(DTE_FLAG_GV, ptr->data[0])) {
>> + /* Existing DTE has no guest page table. */
>> + write_upper(ptr, new);
>> + write_lower(ptr, new);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> + } else if (!FIELD_GET(DTE_FLAG_GV, new->data[0])) {
>> + /*
>> + * Existing DTE has guest page table,
>> + * new DTE has no guest page table,
>> + */
>> + write_lower(ptr, new);
>> + write_upper(ptr, new);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> + } else {
>> + /*
>> + * Existing DTE has guest page table,
>> + * new DTE has guest page table.
>> + */
>> + struct dev_table_entry clear = {};
>> +
>> + /* First disable DTE */
>> + write_lower(ptr, &clear);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> +
>> + /* Then update DTE */
>> + write_upper(ptr, new);
>> + write_lower(ptr, new);
>> + iommu_flush_sync_dte(iommu, dev_data->devid);
>> + }
>
> There is one branch missing where GV is valid in both and the [1]
> doesn't change. Ie atomic replace of a GCR3 table.
Not sure if I follow this.
> And maybe this will need more branches later for the viommu stuff?
I will take care of this later once we introduce the change for vIOMMU
stuff.
> But otherwise yes this captures what is needed just fine.
>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
>
>> @@ -1256,6 +1342,16 @@ static int iommu_flush_dte(struct amd_iommu *iommu, u16 devid)
>> +int iommu_flush_sync_dte(struct amd_iommu *iommu, u16 devid)
>> +{
>> + int ret;
>> +
>> + ret = iommu_flush_dte(iommu, devid);
>> + if (!ret)
>> + iommu_completion_wait(iommu);
>> + return ret;
>> +}
>
> Maybe this doesn't need to return an error since we can't handle
> failure to flush DTE tables..
Okey.
Thanks,
Suravee
next prev parent reply other threads:[~2024-10-03 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:17 [PATCH v4 0/6] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suravee Suthikulpanit
2024-09-16 17:18 ` [PATCH v4 1/6] iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported Suravee Suthikulpanit
2024-09-16 17:18 ` [PATCH v4 2/6] iommu/amd: Introduce helper function to update 256-bit DTE Suravee Suthikulpanit
2024-09-26 19:46 ` Jason Gunthorpe
2024-10-03 16:15 ` Suthikulpanit, Suravee [this message]
2024-10-03 18:54 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 3/6] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers Suravee Suthikulpanit
2024-09-26 19:56 ` Jason Gunthorpe
2024-10-03 16:16 ` Suthikulpanit, Suravee
2024-10-03 18:49 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 4/6] iommu/amd: Introduce helper function get_dte256() Suravee Suthikulpanit
2024-09-26 19:49 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 5/6] iommu/amd: Modify clear_dte_entry() to avoid in-place update Suravee Suthikulpanit
2024-09-26 19:54 ` Jason Gunthorpe
2024-10-03 16:15 ` Suthikulpanit, Suravee
2024-09-16 17:18 ` [PATCH v4 6/6] iommu/amd: Lock DTE before updating the entry with WRITE_ONCE() Suravee Suthikulpanit
2024-09-26 19:58 ` Jason Gunthorpe
2024-09-23 15:03 ` [PATCH v4 0/6] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suthikulpanit, Suravee
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=fc5b7217-49b5-4ca0-b4f7-0eab5000a2e4@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kumaranand@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pandoh@google.com \
--cc=robin.murphy@arm.com \
--cc=santosh.shukla@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
all inboxes | Powered by JetHome®