From: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
To: Christophe Lombard <clombard@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, fbarrat@linux.vnet.ibm.com,
andrew.donnellan@au1.ibm.com
Subject: Re: [PATCH] cxl: Fix is_page_fault() for POWER9
Date: Thu, 06 Jul 2017 16:38:11 +0530 [thread overview]
Message-ID: <87efttrffo.fsf@vajain21.in.ibm.com> (raw)
In-Reply-To: <1499182912-26730-1-git-send-email-clombard@linux.vnet.ibm.com>
Christophe Lombard <clombard@linux.vnet.ibm.com> writes:
> This patches removes this restriction and all page faults, whatever the
> reason, will be handled. In this case, the interruption is always
> acknowledged.
This can also be done with adding call to cxl_ack_ae(ctx) at the end of
cxl_handle_fault().
> static bool cxl_is_page_fault(struct cxl_context *ctx, u64 dsisr)
> {
> - u64 crs; /* Translation Checkout Response Status */
> -
> if ((cxl_is_power8()) && (dsisr & CXL_PSL_DSISR_An_DM))
> return true;
>
> - if (cxl_is_power9()) {
> - crs = (dsisr & CXL_PSL9_DSISR_An_CO_MASK);
> - if ((crs == CXL_PSL9_DSISR_An_PF_SLR) ||
> - (crs == CXL_PSL9_DSISR_An_PF_RGC) ||
> - (crs == CXL_PSL9_DSISR_An_PF_RGP) ||
> - (crs == CXL_PSL9_DSISR_An_PF_HRH) ||
> - (crs == CXL_PSL9_DSISR_An_PF_STEG) ||
> - (crs == CXL_PSL9_DSISR_An_URTCH)) {
> - return true;
> - }
> - }
Removing this check will force call to copro_handle_mm_fault even for
nmmu reported errors that only need to be communicated to the AFU and
not handled by mm subsystem as such.
> + if (cxl_is_power9())
> + return true;
Optional: With this change the function has become a good candidate for
being inlined or even converting to a macro.
--
Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
Linux Technology Center, IBM India Pvt. Ltd.
prev parent reply other threads:[~2017-07-06 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 15:41 [PATCH] cxl: Fix is_page_fault() for POWER9 Christophe Lombard
2017-07-06 11:08 ` Vaibhav Jain [this message]
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=87efttrffo.fsf@vajain21.in.ibm.com \
--to=vaibhav@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=clombard@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).