From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Qiang Yu <quic_qianyu@quicinc.com>, <mani@kernel.org>,
<loic.poulain@linaro.org>
Cc: <mhi@lists.linux.dev>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_cang@quicinc.com>,
<mrana@quicinc.com>
Subject: Re: [PATCH v2] bus: mhi: host: Disable preemption while processing data events
Date: Mon, 14 Nov 2022 07:53:28 -0700 [thread overview]
Message-ID: <8aae17cf-7c2b-85bb-d0f5-a5f71e792d16@quicinc.com> (raw)
In-Reply-To: <1668419923-20292-1-git-send-email-quic_qianyu@quicinc.com>
On 11/14/2022 2:58 AM, Qiang Yu wrote:
> If data processing of an event is scheduled out because core
> is busy handling multiple irqs, this can starve the processing
> of MHI M0 state change event on another core. Fix this issue by
> disabling irq on the core processing data events.
>
> Signed-off-by: Qiang Yu <quic_qianyu@quicinc.com>
> ---
> v1->v2: add comments about why we disable local irq
>
> drivers/bus/mhi/host/main.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bus/mhi/host/main.c b/drivers/bus/mhi/host/main.c
> index f3aef77a..fcb2586 100644
> --- a/drivers/bus/mhi/host/main.c
> +++ b/drivers/bus/mhi/host/main.c
> @@ -1027,13 +1027,20 @@ int mhi_process_data_event_ring(struct mhi_controller *mhi_cntrl,
>
> void mhi_ev_task(unsigned long data)
> {
> + unsigned long flags;
> struct mhi_event *mhi_event = (struct mhi_event *)data;
> struct mhi_controller *mhi_cntrl = mhi_event->mhi_cntrl;
>
> /* process all pending events */
> - spin_lock_bh(&mhi_event->lock);
> + spin_lock_irqsave(&mhi_event->lock, flags);
> + /*
> + * When muiltiple IRQs come, the tasklet will be scheduled out with event ring lock
multiple
> + * remaining acquired, causing M0 event process on another core gets stuck when it
> + * tries to acquire the same event ring lock. Thus let's disable local IRQs here.
> + */
> +
> mhi_event->process_event(mhi_cntrl, mhi_event, U32_MAX);
> - spin_unlock_bh(&mhi_event->lock);
> + spin_unlock_irqrestore(&mhi_event->lock, flags);
> }
>
> void mhi_ctrl_ev_task(unsigned long data)
prev parent reply other threads:[~2022-11-14 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:58 Qiang Yu
2022-11-14 14:53 ` Jeffrey Hugo [this message]
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=8aae17cf-7c2b-85bb-d0f5-a5f71e792d16@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=mrana@quicinc.com \
--cc=quic_cang@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
all inboxes | Powered by JetHome®