[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <372c6dbbda18cccdcf2b053ee87f2ada9640e2b8.camel@gmail.com>
Date: Thu, 04 Feb 2021 15:58:31 +0100
From: Bean Huo <huobean@...il.com>
To: Adrian Hunter <adrian.hunter@...el.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
"James E . J . Bottomley" <jejb@...ux.ibm.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Can Guo <cang@...eaurora.org>,
Stanley Chu <stanley.chu@...iatek.com>
Subject: Re: [PATCH 3/4] scsi: ufs-debugfs: Add user-defined
exception_event_mask
On Wed, 2021-02-03 at 11:56 +0200, Adrian Hunter wrote:
> >
> > Hallo Adrian
>
> Hi Bean
>
> Thanks for the review
>
> >
> > Would you like sharing the advantage of this debugfs node comparing
> > to
> > sysfs node "attributes/exception_event_control(if it is writable)"?
>
> Primarily this is being done as a debug interface, but the user's
> exception
> events also need to be kept separate from the driver's ones.
>
> > what is the value of this?
>
> To be able to determine if the UFS device is being affected by
> exception events.
>
> > Also, now I can disable/enable UFS event over ufs-bsg.
>
> That will be overwritten by the driver when it updates the e.g. bkops
> control, or sometimes also suspend/resume.
Hi Adrian
yes, I saw that, they are not tracked by driver.
I have one question that why "exception_event_mask" cannot represent
the current QUERY_ATTR_IDN_EE_CONTROL value? only after writing it.
thanks,
Bean
Powered by blists - more mailing lists