linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
To: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
	imunsie@au1.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] cxl: Flush PSL cache before resetting the adapter
Date: Tue, 4 Oct 2016 10:35:36 +0200	[thread overview]
Message-ID: <b743c589-85a9-621b-eb6a-9acb4495514b@linux.vnet.ibm.com> (raw)
In-Reply-To: <87wphowtnu.fsf@vajain21.in.ibm.com>

Hi Vaibhav,


Le 04/10/2016 à 07:49, Vaibhav Jain a écrit :
> Hi Fred,
>
> Frederic Barrat <fbarrat@linux.vnet.ibm.com> writes:
>
>>
>> +	/* the adapter is about to be reset, so ignore errors */
>> +	cxl_data_cache_flush(adapter);
>> +
> Will be a good idea if we return error and not let the reset to proceed,
> if cxl_data_cache_flush returns EBUSY as continuing again may cause the
> UE error.

I'm going to change cxl_data_cache_flush() to return ETIMEOUT instead of 
EBUSY, as it is misleading. With the current patch, EBUSY is not 
returned because there are active contexts running on the card. It is 
returned when the hardware/psl doesn't reply within 5 seconds to the 
flush request. It's not supposed to happen and would show an issue with 
the hardware/psl. In which case the adapter is close to useless, so we 
might as well try resetting it.

On a related note, we've talked with the folks from cxlflash, and we'll 
test a separate (complementary) patch to deny resetting the adapter if 
there are any active contexts, since, as you say, the likelihood of 
hitting a UE would be pretty high.

   Fred

  reply	other threads:[~2016-10-04  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 19:36 [PATCH] cxl: Flush PSL cache before resetting the adapter Frederic Barrat
2016-10-04  3:45 ` Andrew Donnellan
2016-10-04  4:31 ` Ian Munsie
2016-10-04  5:49 ` Vaibhav Jain
2016-10-04  8:35   ` Frederic Barrat [this message]
2016-10-05  2:36 ` 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=b743c589-85a9-621b-eb6a-9acb4495514b@linux.vnet.ibm.com \
    --to=fbarrat@linux.vnet.ibm.com \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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).