From: Joerg Roedel <joro@8bytes.org>
To: Tom Murphy <tmurphy@arista.com>
Cc: iommu@lists.linux-foundation.org, murphyt7@tcd.ie,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] iommu/amd: flush not present cache in iommu_map_page
Date: Fri, 26 Apr 2019 16:04:29 +0200 [thread overview]
Message-ID: <20190426140429.GG24576@8bytes.org> (raw)
In-Reply-To: <20190424165051.13614-1-tmurphy@arista.com>
On Wed, Apr 24, 2019 at 05:50:51PM +0100, Tom Murphy wrote:
> check if there is a not-present cache present and flush it if there is.
>
> Signed-off-by: Tom Murphy <tmurphy@arista.com>
> ---
> drivers/iommu/amd_iommu.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> index f7cdd2ab7f11..91fe5cb10f50 100644
> --- a/drivers/iommu/amd_iommu.c
> +++ b/drivers/iommu/amd_iommu.c
> @@ -1637,6 +1637,11 @@ static int iommu_map_page(struct protection_domain *dom,
>
> update_domain(dom);
>
> + if (unlikely(amd_iommu_np_cache && !dom->updated)) {
> + domain_flush_pages(dom, bus_addr, page_size);
> + domain_flush_complete(dom);
> + }
> +
The iommu_map_page function is called once per physical page that is
mapped, so in the worst case for every 4k mapping established. So it is
not the right place to put this check in.
From a quick glance this check belongs into the map_sg() and the
amd_iommu_map() function, but without the dom->updated check.
Besides, to really support systems with np-cache in a way that doesn't
destroy all performance, the driver also needs range-flushes for IOTLBs.
Currently it can only flush a 4k page of the full address space of a
domain. But that doesn't mean we shouldn't fix the missing flushes now.
So please re-send the patch with the check at the two places I pointed
out above.
Thanks,
Joerg
next prev parent reply other threads:[~2019-04-26 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:50 [PATCH v1] iommu/amd: flush not present cache in iommu_map_page Tom Murphy
2019-04-26 14:04 ` Joerg Roedel [this message]
2019-04-27 14:20 ` Tom Murphy
2019-04-29 11:59 ` Christoph Hellwig
2019-04-29 12:17 ` Tom Murphy
2019-04-29 12:29 ` Christoph Hellwig
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=20190426140429.GG24576@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=murphyt7@tcd.ie \
--cc=tmurphy@arista.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