From: christophe lombard <clombard@linux.vnet.ibm.com>
To: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Cc: Philippe Bergheaud <philippe.bergheaud@fr.ibm.com>,
"Alastair D'Silva" <alastair@au1.ibm.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Christophe Lombard <christophe_lombard@fr.ibm.com>
Subject: Re: [PATCH] cxl: Set the valid bit in PE for dedicated mode
Date: Mon, 28 Aug 2017 10:58:08 +0200 [thread overview]
Message-ID: <e937daa7-9671-c700-edf9-9a890c9af7fd@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170828041522.32188-1-vaibhav@linux.vnet.ibm.com>
Le 28/08/2017 à 06:15, Vaibhav Jain a écrit :
> Make sure to set the valid-bit in software-state field of the
> populated PE. This was earlier missing for dedicated mode AFUs, hence
> was causing a PSL freeze when the AFU was activated.
Acked-by: Christophe Lombard <clombard@linux.vnet.ibm.com>
> Signed-off-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
> ---
> drivers/misc/cxl/native.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/misc/cxl/native.c b/drivers/misc/cxl/native.c
> index 4a82c313cf71..0e748c682ee9 100644
> --- a/drivers/misc/cxl/native.c
> +++ b/drivers/misc/cxl/native.c
> @@ -897,6 +897,10 @@ int cxl_attach_dedicated_process_psl9(struct cxl_context *ctx, u64 wed, u64 amr)
> if (ctx->afu->adapter->native->sl_ops->update_dedicated_ivtes)
> afu->adapter->native->sl_ops->update_dedicated_ivtes(ctx);
>
> + ctx->elem->software_state = cpu_to_be32(CXL_PE_SOFTWARE_STATE_V);
> + /* Make sure the changes to the PE are visible to the card */
> + smp_wmb();
> +
> result = cxl_ops->afu_reset(afu);
> if (result)
> return result;
next prev parent reply other threads:[~2017-08-28 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 4:15 [PATCH] cxl: Set the valid bit in PE for dedicated mode Vaibhav Jain
2017-08-28 4:25 ` Andrew Donnellan
2017-08-28 8:58 ` christophe lombard [this message]
2017-08-28 9:42 ` Frederic Barrat
2017-08-29 6:53 ` Michael Ellerman
2017-08-30 12:04 ` Vaibhav Jain
2017-08-30 12:28 ` Michael Ellerman
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=e937daa7-9671-c700-edf9-9a890c9af7fd@linux.vnet.ibm.com \
--to=clombard@linux.vnet.ibm.com \
--cc=alastair@au1.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=christophe_lombard@fr.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=philippe.bergheaud@fr.ibm.com \
--cc=vaibhav@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).