From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Damian Muszynski <damian.muszynski@intel.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
qat-linux@intel.com,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Subject: Re: [PATCH v3 0/5] crypto: qat - add heartbeat feature
Date: Thu, 22 Jun 2023 21:27:36 +0300 [thread overview]
Message-ID: <ZJSSmE9nDZXKwPd0@smile.fi.intel.com> (raw)
In-Reply-To: <20230622180405.133298-1-damian.muszynski@intel.com>
On Thu, Jun 22, 2023 at 08:04:01PM +0200, Damian Muszynski wrote:
> This set introduces support for the QAT heartbeat feature. It allows
> detection whenever device firmware or acceleration unit will hang.
> We're adding this feature to allow our clients having a tool with
> they could verify if all of the Quick Assist hardware resources are
> healthy and operational.
>
> QAT device firmware periodically writes counters to a specified physical
> memory location. A pair of counters per thread is incremented at
> the start and end of the main processing loop within the firmware.
> Checking for Heartbeat consists of checking the validity of the pair
> of counter values for each thread. Stagnant counters indicate
> a firmware hang.
>
> The first patch adds timestamp synchronization to the firmware.
> The second patch removes historical and never used HB definitions.
> Patch no. 3 is implementing the hardware clock frequency measuring
> interface.
> The fourth introduces the main heartbeat implementation with the debugfs
> interface.
> The last patch implements an algorithm that allows the code to detect
> which version of heartbeat API is used at the currently loaded firmware.
I made a few last minute nit-picks, feel free to ignore them if it's okay
with the maintainers.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-22 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 18:04 [PATCH v3 0/5] crypto: qat - add heartbeat feature Damian Muszynski
2023-06-22 18:04 ` [PATCH v3 1/5] crypto: qat - add internal timer for qat 4xxx Damian Muszynski
2023-06-22 18:04 ` [PATCH v3 2/5] crypto: qat - drop obsolete heartbeat interface Damian Muszynski
2023-06-22 18:04 ` [PATCH v3 3/5] crypto: qat - add measure clock frequency Damian Muszynski
2023-06-22 18:26 ` Andy Shevchenko
2023-06-22 18:04 ` [PATCH v3 4/5] crypto: qat - add heartbeat feature Damian Muszynski
2023-06-22 18:04 ` [PATCH v3 5/5] crypto: qat - add heartbeat counters check Damian Muszynski
2023-06-22 18:21 ` [PATCH v3 0/5] crypto: qat - add heartbeat feature Andy Shevchenko
2023-06-22 18:27 ` Andy Shevchenko [this message]
2023-06-26 11:22 ` Damian Muszynski
2023-06-26 11:31 ` Giovanni Cabiddu
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=ZJSSmE9nDZXKwPd0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=damian.muszynski@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@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).