All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "James E . J . Bottomley" <jejb@linux.ibm.com>,
	Bean Huo <huobean@gmail.com>, Avri Altman <avri.altman@wdc.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Can Guo <cang@codeaurora.org>,
	Asutosh Das <asutoshd@codeaurora.org>,
	Bart Van Assche <bvanassche@acm.org>,
	linux-scsi@vger.kernel.org
Subject: [PATCH V4 0/2] scsi: ufs: Fix runtime PM messages never-ending cycle
Date: Mon, 28 Feb 2022 13:36:50 +0200	[thread overview]
Message-ID: <20220228113652.970857-1-adrian.hunter@intel.com> (raw)

Hi

Here is V4 to address comments by Martin.  See patches for version history.

Summary:

Kernel messages produced during runtime PM can cause a never-ending
cycle because user space utilities (e.g. journald or rsyslog) write the
messages back to storage, causing runtime resume, more messages, and so
on.

Messages that tell of things that are expected to happen, are arguably
unnecessary, so make changes to suppress them for the UFS driver.


Adrian Hunter (2):
      scsi: Add quiet_suspend flag for SCSI devices to suppress some PM messages
      scsi: ufs: Fix runtime PM messages never-ending cycle

 drivers/scsi/scsi_error.c  |  9 +++++++--
 drivers/scsi/sd.c          |  6 ++++--
 drivers/scsi/ufs/ufshcd.c  | 21 +++++++++++++++++++--
 include/scsi/scsi_device.h |  6 ++++++
 4 files changed, 36 insertions(+), 6 deletions(-)


Regards
Adrian

             reply	other threads:[~2022-02-28 11:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 11:36 Adrian Hunter [this message]
2022-02-28 11:36 ` [PATCH V4 1/2] scsi: Add quiet_suspend flag for SCSI devices to suppress some PM messages Adrian Hunter
2022-02-28 11:36 ` [PATCH V4 2/2] scsi: ufs: Fix runtime PM messages never-ending cycle Adrian Hunter
2022-03-02  4:54 ` [PATCH V4 0/2] " Martin K. Petersen
2022-03-09  4:15 ` Martin K. Petersen

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=20220228113652.970857-1-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=cang@codeaurora.org \
    --cc=huobean@gmail.com \
    --cc=jejb@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.