From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Tim Blechmann <tim.blechmann@gmail.com>,
<linux-remoteproc@vger.kernel.org>
Cc: Tim Blechmann <tim@klingt.org>
Subject: Re: [PATCH 1/1] rpmsg: virtio_rpmsg_bus - prevent possible race condition
Date: Mon, 4 Sep 2023 15:52:56 +0200 [thread overview]
Message-ID: <64ecb19a-b3d1-0fa1-b015-b34607aee460@foss.st.com> (raw)
In-Reply-To: <20230904083602.106703-1-tim@klingt.org>
Hello Tim,
On 9/4/23 10:36, Tim Blechmann wrote:
> when we cannot get a tx buffer (`get_a_tx_buf`) `rpmsg_upref_sleepers`
> enables tx-complete interrupt.
> however if the interrupt is executed after `get_a_tx_buf` and before
> `rpmsg_upref_sleepers` we may mis the tx-complete interrupt and sleep
> for the full 15 seconds.
Is there any reason why your co-processor is unable to release the TX RPMSG
buffers for 15 seconds? If not, you should first determine the reason why it is
stalled.
Regards,
Arnaud
>
> in this case, so we re-try once before we really start to sleep
>
> Signed-off-by: Tim Blechmann <tim@klingt.org>
> ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 24 +++++++++++++++---------
> 1 file changed, 15 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
> index 905ac7910c98..2a9d42225e60 100644
> --- a/drivers/rpmsg/virtio_rpmsg_bus.c
> +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
> @@ -587,21 +587,27 @@ static int rpmsg_send_offchannel_raw(struct rpmsg_device *rpdev,
>
> /* no free buffer ? wait for one (but bail after 15 seconds) */
> while (!msg) {
> /* enable "tx-complete" interrupts, if not already enabled */
> rpmsg_upref_sleepers(vrp);
>
> - /*
> - * sleep until a free buffer is available or 15 secs elapse.
> - * the timeout period is not configurable because there's
> - * little point in asking drivers to specify that.
> - * if later this happens to be required, it'd be easy to add.
> - */
> - err = wait_event_interruptible_timeout(vrp->sendq,
> - (msg = get_a_tx_buf(vrp)),
> - msecs_to_jiffies(15000));
> + /* make sure to retry to grab tx buffer before we start waiting */
> + msg = get_a_tx_buf(vrp);
> + if (msg) {
> + err = 0;
> + } else {
> + /*
> + * sleep until a free buffer is available or 15 secs elapse.
> + * the timeout period is not configurable because there's
> + * little point in asking drivers to specify that.
> + * if later this happens to be required, it'd be easy to add.
> + */
> + err = wait_event_interruptible_timeout(vrp->sendq,
> + (msg = get_a_tx_buf(vrp)),
> + msecs_to_jiffies(15000));
> + }
>
> /* disable "tx-complete" interrupts if we're the last sleeper */
> rpmsg_downref_sleepers(vrp);
>
> /* timeout ? */
> if (!err) {
next prev parent reply other threads:[~2023-09-04 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 8:36 [PATCH 1/1] rpmsg: virtio_rpmsg_bus - prevent possible race condition Tim Blechmann
2023-09-04 13:52 ` Arnaud POULIQUEN [this message]
2023-09-04 20:43 ` Mathieu Poirier
2023-09-05 1:33 ` Tim Blechmann
2023-09-05 16:02 ` Mathieu Poirier
2023-09-08 15:04 ` Arnaud POULIQUEN
2023-09-09 6:28 ` Tim Blechmann
2023-09-11 17:20 ` Arnaud POULIQUEN
2023-09-13 1:07 ` Tim Blechmann
2023-09-13 1:11 ` Tim Blechmann
2023-09-13 7:44 ` Arnaud POULIQUEN
2023-09-13 8:47 ` Tim Blechmann
2023-09-13 10:02 ` Arnaud POULIQUEN
[not found] ` <CAG2LOc42AG5H56=tzz8_2WrrBiy9d74qYmgPQaEVGrzWTNqodg@mail.gmail.com>
2023-09-14 17:25 ` Arnaud POULIQUEN
2023-09-16 1:38 ` Tim Blechmann
2023-09-13 10:10 ` Arnaud POULIQUEN
2023-09-13 14:46 ` Mathieu Poirier
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 4:51 Tim Blechmann
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=64ecb19a-b3d1-0fa1-b015-b34607aee460@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=tim.blechmann@gmail.com \
--cc=tim@klingt.org \
/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