From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: mpe@ellerman.id.au, aneesh.kumar@linux.vnet.ibm.com,
bsingharora@gmail.com, linuxppc-dev@lists.ozlabs.org
Cc: clombard@linux.vnet.ibm.com
Subject: [RFC v2 2/3] cxl: Mark context requiring global TLBIs
Date: Thu, 22 Jun 2017 12:06:48 +0200 [thread overview]
Message-ID: <20170622100649.3846-3-fbarrat@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170622100649.3846-1-fbarrat@linux.vnet.ibm.com>
The PSL needs to see all TLBIs pertinent to the memory contexts used
on the cxl adapter. For the hash memory model, it was done by making
all TLBIs global as soon as the cxl driver is in use. For radix, we
need something similar, but we can refine and only convert to global
the invalidations for contexts actually used by the device.
So mark the contexts being attached to the cxl adapter as requiring
global TLBIs.
Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
---
drivers/misc/cxl/api.c | 12 ++++++++++--
drivers/misc/cxl/file.c | 12 ++++++++++--
2 files changed, 20 insertions(+), 4 deletions(-)
diff --git a/drivers/misc/cxl/api.c b/drivers/misc/cxl/api.c
index 1a138c83f877..2cebe214195e 100644
--- a/drivers/misc/cxl/api.c
+++ b/drivers/misc/cxl/api.c
@@ -332,8 +332,17 @@ int cxl_start_context(struct cxl_context *ctx, u64 wed,
cxl_context_mm_count_get(ctx);
/* decrement the use count */
- if (ctx->mm)
+ if (ctx->mm) {
mmput(ctx->mm);
+#ifdef CONFIG_PPC_BOOK3S_64
+ mm_context_set_global_tlbi(&ctx->mm->context);
+ /*
+ * Barrier guarantees that the device will
+ * receive all TLBIs from that point on
+ */
+ smp_wmb();
+#endif
+ }
}
cxl_ctx_get();
@@ -347,7 +356,6 @@ int cxl_start_context(struct cxl_context *ctx, u64 wed,
cxl_context_mm_count_put(ctx);
goto out;
}
-
ctx->status = STARTED;
out:
mutex_unlock(&ctx->status_mutex);
diff --git a/drivers/misc/cxl/file.c b/drivers/misc/cxl/file.c
index 0761271d68c5..3ba6a60e0a6d 100644
--- a/drivers/misc/cxl/file.c
+++ b/drivers/misc/cxl/file.c
@@ -222,8 +222,17 @@ static long afu_ioctl_start_work(struct cxl_context *ctx,
cxl_context_mm_count_get(ctx);
/* decrement the use count */
- if (ctx->mm)
+ if (ctx->mm) {
mmput(ctx->mm);
+#ifdef CONFIG_PPC_BOOK3S_64
+ mm_context_set_global_tlbi(&ctx->mm->context);
+ /*
+ * Barrier guarantees that the device will receive all
+ * TLBIs from that point on
+ */
+ smp_wmb();
+#endif
+ }
trace_cxl_attach(ctx, work.work_element_descriptor, work.num_interrupts, amr);
@@ -236,7 +245,6 @@ static long afu_ioctl_start_work(struct cxl_context *ctx,
cxl_context_mm_count_put(ctx);
goto out;
}
-
ctx->status = STARTED;
rc = 0;
out:
--
2.11.0
next prev parent reply other threads:[~2017-06-22 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 10:06 [RFC v2 0/3] powerpc/mm: Mark memory contexts requiring global TLBIs Frederic Barrat
2017-06-22 10:06 ` [RFC v2 1/3] powerpc/mm: Add marker for contexts requiring global TLB invalidations Frederic Barrat
2017-06-22 10:06 ` Frederic Barrat [this message]
2017-06-22 10:06 ` [RFC v2 3/3] cxl: Add memory barrier to guarantee TLBI scope Frederic Barrat
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=20170622100649.3846-3-fbarrat@linux.vnet.ibm.com \
--to=fbarrat@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=clombard@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).