public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <avri.altman@wdc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] scsi: ufs: critical health condition
Date: Tue, 11 Feb 2025 09:41:40 -0800	[thread overview]
Message-ID: <527e89a3-0994-4da3-a474-e4bd1e6569f0@acm.org> (raw)
In-Reply-To: <20250211065813.58091-1-avri.altman@wdc.com>

On 2/10/25 10:58 PM, Avri Altman wrote:
> The UFS4.1 standard, released on January 8, 2025, added a new exception
> event: HEALTH_CRITICAL, which notifies the host of a device's critical
> health condition. This notification implies that the device is
> approaching the end of its lifetime based on the amount of performed
> program/erase cycles.
> 
> Once an EOL (End-of-Life) exception event is received, we increment a
> designated member, which is exposed via a `sysfs` entry. This new entry,
> will report the number of times a critical health event has been
> reported by a UFS device.
> 
> To handle this new `sysfs` entry, userspace applications can use
> `select()`, `poll()`, or `epoll()` to monitor changes in the
> `critical_health` attribute. The kernel will call `sysfs_notify()` to
> signal changes, allowing the userspace application to detect and respond
> to these changes efficiently.
> 
> The host can gain further insight into the specific issue by reading one
> of the following attributes: bPreEOLInfo, bDeviceLifeTimeEstA,
> bDeviceLifeTimeEstB, bWriteBoosterBufferLifeTimeEst, and
> bRPMBLifeTimeEst. All those are available for reading via the driver's
> sysfs entries or through an applicable utility. It is up to user-space
> to read these attributes if needed.

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

  reply	other threads:[~2025-02-11 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  6:58 [PATCH v4] scsi: ufs: critical health condition Avri Altman
2025-02-11 17:41 ` Bart Van Assche [this message]
2025-02-13  3:17 ` Martin K. Petersen
2025-02-19  1:06 ` Martin K. Petersen
2025-03-13 18:13 ` Bart Van Assche

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=527e89a3-0994-4da3-a474-e4bd1e6569f0@acm.org \
    --to=bvanassche@acm.org \
    --cc=avri.altman@wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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