From: Manivannan Sadhasivam <mani@kernel.org>
To: Qiang Yu <quic_qianyu@quicinc.com>
Cc: quic_jhugo@quicinc.com, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_cang@quicinc.com, quic_mrana@quicinc.com,
Hemant Kumar <quic_hemantk@quicinc.com>,
Lazarus Motha <quic_lmotha@quicinc.com>
Subject: Re: [PATCH v4 4/4] bus: mhi: host: Take irqsave lock after TRE is generated
Date: Fri, 24 Nov 2023 15:39:16 +0530 [thread overview]
Message-ID: <20231124100916.GB4536@thinkpad> (raw)
In-Reply-To: <1699939661-7385-5-git-send-email-quic_qianyu@quicinc.com>
On Tue, Nov 14, 2023 at 01:27:41PM +0800, Qiang Yu wrote:
> From: Hemant Kumar <quic_hemantk@quicinc.com>
>
> If CONFIG_TRACE_IRQFLAGS is enabled, irq will be enabled once __local_bh_
> enable_ip is called as part of write_unlock_bh. Hence, let's take irqsave
"__local_bh_enable_ip" is a function name, so you should not break it.
> lock after TRE is generated to avoid running write_unlock_bh when irqsave
> lock is held.
>
I still don't understand this commit message. Where is the write_unlock_bh()
being called?
- Mani
> Signed-off-by: Hemant Kumar <quic_hemantk@quicinc.com>
> Signed-off-by: Lazarus Motha <quic_lmotha@quicinc.com>
> Signed-off-by: Qiang Yu <quic_qianyu@quicinc.com>
> ---
> drivers/bus/mhi/host/main.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/bus/mhi/host/main.c b/drivers/bus/mhi/host/main.c
> index 33f27e2..d7abd0b 100644
> --- a/drivers/bus/mhi/host/main.c
> +++ b/drivers/bus/mhi/host/main.c
> @@ -1128,17 +1128,15 @@ static int mhi_queue(struct mhi_device *mhi_dev, struct mhi_buf_info *buf_info,
> if (unlikely(MHI_PM_IN_ERROR_STATE(mhi_cntrl->pm_state)))
> return -EIO;
>
> - read_lock_irqsave(&mhi_cntrl->pm_lock, flags);
> -
> ret = mhi_is_ring_full(mhi_cntrl, tre_ring);
> - if (unlikely(ret)) {
> - ret = -EAGAIN;
> - goto exit_unlock;
> - }
> + if (unlikely(ret))
> + return -EAGAIN;
>
> ret = mhi_gen_tre(mhi_cntrl, mhi_chan, buf_info, mflags);
> if (unlikely(ret))
> - goto exit_unlock;
> + return ret;
> +
> + read_lock_irqsave(&mhi_cntrl->pm_lock, flags);
>
> /* Packet is queued, take a usage ref to exit M3 if necessary
> * for host->device buffer, balanced put is done on buffer completion
> @@ -1158,7 +1156,6 @@ static int mhi_queue(struct mhi_device *mhi_dev, struct mhi_buf_info *buf_info,
> if (dir == DMA_FROM_DEVICE)
> mhi_cntrl->runtime_put(mhi_cntrl);
>
> -exit_unlock:
> read_unlock_irqrestore(&mhi_cntrl->pm_lock, flags);
>
> return ret;
> --
> 2.7.4
>
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-11-24 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:27 [PATCH v4 0/4] bus: mhi: host: Add lock to avoid race when ringing channel DB Qiang Yu
2023-11-14 5:27 ` [PATCH v4 1/4] bus: mhi: host: Add spinlock to protect WP access when queueing TREs Qiang Yu
2023-11-14 5:27 ` [PATCH v4 2/4] bus: mhi: host: Drop chan lock before queuing buffers Qiang Yu
2023-11-24 10:04 ` Manivannan Sadhasivam
2023-11-27 7:12 ` Qiang Yu
2023-11-27 7:13 ` Qiang Yu
2023-11-28 13:32 ` Manivannan Sadhasivam
2023-11-29 3:29 ` Qiang Yu
2023-11-30 5:31 ` Manivannan Sadhasivam
2023-12-06 2:25 ` Qiang Yu
2023-12-06 13:48 ` Manivannan Sadhasivam
2023-12-07 5:25 ` Qiang Yu
2023-12-07 5:27 ` Qiang Yu
2023-12-07 6:43 ` Manivannan Sadhasivam
2023-12-07 9:50 ` Qiang Yu
2023-11-14 5:27 ` [PATCH v4 3/4] bus: mhi: host: Avoid processing buffer and event of a disable channel Qiang Yu
2023-11-14 5:27 ` [PATCH v4 4/4] bus: mhi: host: Take irqsave lock after TRE is generated Qiang Yu
2023-11-24 10:09 ` Manivannan Sadhasivam [this message]
2023-11-27 7:19 ` Qiang Yu
2023-12-07 6:38 ` Manivannan Sadhasivam
2023-12-07 9:20 ` Qiang Yu
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=20231124100916.GB4536@thinkpad \
--to=mani@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_cang@quicinc.com \
--cc=quic_hemantk@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_lmotha@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_qianyu@quicinc.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