linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Weight <russell.h.weight@intel.com>
To: "Wu, Hao" <hao.wu@intel.com>, "mdf@kernel.org" <mdf@kernel.org>,
	"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "trix@redhat.com" <trix@redhat.com>,
	"lgoncalv@redhat.com" <lgoncalv@redhat.com>,
	"Xu, Yilun" <yilun.xu@intel.com>,
	"Gerlach, Matthew" <matthew.gerlach@intel.com>
Subject: Re: [PATCH v1 0/2] fpga: dfl: Log and clear errors on driver init
Date: Wed, 20 Oct 2021 17:05:52 -0700	[thread overview]
Message-ID: <f64249d2-1d48-c191-bce8-5e9e4a5e4643@intel.com> (raw)
In-Reply-To: <DM6PR11MB3819F29DF7B20FDED6DC814685BE9@DM6PR11MB3819.namprd11.prod.outlook.com>



On 10/19/21 9:44 PM, Wu, Hao wrote:
>> Subject: [PATCH v1 0/2] fpga: dfl: Log and clear errors on driver init
>>
>> These patches address a request to log and clear any prexisting errors on
>> FPGA cards when the drivers load. Any existing errors will result in print
>> statements to the kernel error log before the errors are cleared. These
>> changes specifically affect the fme and port error registers.
> Could you please explain more about why we need this change? 
> As we have user interface to log and clear errors already, is it a better choice
> to let userspace log and clear them during AFU initialization?
In the new architecture we are offering more flexibility to customers
for adding functions. With these designs it becomes nearly impossible
to design the AFU interface handler to recover from errors and resume
operation afterwards. The proposed solution is to flag the source of
the error and then capture it in sticky registers so that they can be
read out from SW in the event of a crash/warm boot. To ensure that we
capture these errors, the proposal is to log them in the kernel log and
clear them at driver initialization.

- Russ

> Hao
>
>> Russ Weight (2):
>>   fpga: dfl: afu: Clear port errors in afu init
>>   fpga: dfl: fme: Clear fme global errors at driver init
>>
>>  drivers/fpga/dfl-afu-error.c |  26 ++++---
>>  drivers/fpga/dfl-fme-error.c | 128 +++++++++++++++++++++++------------
>>  2 files changed, 100 insertions(+), 54 deletions(-)
>>
>> --
>> 2.25.1


  reply	other threads:[~2021-10-21  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 23:15 [PATCH v1 0/2] fpga: dfl: Log and clear errors on driver init Russ Weight
2021-10-19 23:15 ` [PATCH v1 1/2] fpga: dfl: afu: Clear port errors in afu init Russ Weight
2021-10-20  4:15   ` Xu Yilun
2021-10-20 12:18   ` Tom Rix
2021-10-20 16:02     ` Russ Weight
2021-10-19 23:15 ` [PATCH v1 2/2] fpga: dfl: fme: Clear fme global errors at driver init Russ Weight
2021-10-20 12:59   ` Tom Rix
2021-10-20  4:44 ` [PATCH v1 0/2] fpga: dfl: Log and clear errors on " Wu, Hao
2021-10-21  0:05   ` Russ Weight [this message]
2021-10-21  0:43     ` Wu, Hao

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=f64249d2-1d48-c191-bce8-5e9e4a5e4643@intel.com \
    --to=russell.h.weight@intel.com \
    --cc=hao.wu@intel.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@intel.com \
    --cc=mdf@kernel.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.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).