From: Joerg Roedel <joro@8bytes.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org, Joerg Roedel <jroedel@suse.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] iommu/amd: Don't use atomic64_t for domain->pt_root
Date: Fri, 26 Jun 2020 10:05:45 +0200 [thread overview]
Message-ID: <20200626080547.24865-1-joro@8bytes.org> (raw)
From: Joerg Roedel <jroedel@suse.de>
Hi,
a previous discussion pointed out that using atomic64_t for that
purpose is a bit of overkill. This patch-set replaces it with unsigned
long and introduces some helpers first to make the change more easy.
Qian, can you please test these patches in your environment? You can
trigger any race-condition there pretty reliably :)
Other than that, please review and test.
Regards,
Joerg
Changed to v1:
- Addressed review comments from Qian.
Joerg Roedel (2):
iommu/amd: Add helper functions to update domain->pt_root
iommu/amd: Use 'unsigned long' for domain->pt_root
drivers/iommu/amd/amd_iommu_types.h | 2 +-
drivers/iommu/amd/iommu.c | 44 +++++++++++++++++++++--------
2 files changed, 33 insertions(+), 13 deletions(-)
--
2.27.0
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-06-26 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 8:05 Joerg Roedel [this message]
2020-06-26 8:05 ` [PATCH v2 1/2] iommu/amd: Add helper functions to update domain->pt_root Joerg Roedel
2020-06-26 8:05 ` [PATCH v2 2/2] iommu/amd: Use 'unsigned long' for domain->pt_root Joerg Roedel
2020-06-26 12:30 ` [PATCH v2 0/2] iommu/amd: Don't use atomic64_t " Qian Cai
2020-06-30 9:57 ` Joerg Roedel
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=20200626080547.24865-1-joro@8bytes.org \
--to=joro@8bytes.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).