From: Christoph Hellwig <hch@infradead.org>
To: Tom Murphy <tmurphy@arista.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
murphyt7@tcd.ie
Subject: Re: [PATCH] iommu/amd: flush not present cache in iommu_map_page
Date: Wed, 24 Apr 2019 07:32:46 -0700 [thread overview]
Message-ID: <20190424143246.GA24079@infradead.org> (raw)
In-Reply-To: <20190424141900.8883-1-tmurphy@arista.com>
On Wed, Apr 24, 2019 at 03:18:59PM +0100, Tom Murphy via iommu 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 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> index f7cdd2ab7f11..8ef43224aae0 100644
> --- a/drivers/iommu/amd_iommu.c
> +++ b/drivers/iommu/amd_iommu.c
> @@ -1636,6 +1636,12 @@ static int iommu_map_page(struct protection_domain *dom,
> pte[i] = __pte;
>
> update_domain(dom);
> + if (!dom->updated) {
> + if (unlikely(amd_iommu_np_cache)) {
> + domain_flush_pages(dom, bus_addr, page_size);
> + domain_flush_complete(dom);
> + }
> + }
The two conditions can go into one if statement to make this a little
more clear.
And I'd really like to understand the unlikely - amd_iommu_np_cache
is set based on a hardware capability, so it seems rather odd to mark
it unlikely. Dynamic branch prediction really should do the right thing
here usually.
next prev parent reply other threads:[~2019-04-24 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 14:18 [PATCH] iommu/amd: flush not present cache in iommu_map_page Tom Murphy
2019-04-24 14:32 ` Christoph Hellwig [this message]
2019-04-24 14:47 ` Tom Murphy
2019-04-24 14:58 ` Christoph Hellwig
2019-04-24 15:55 ` Joerg Roedel
2019-04-24 16:25 ` Tom Murphy
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=20190424143246.GA24079@infradead.org \
--to=hch@infradead.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