mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Meng Li <Meng.Li@windriver.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver: firmware: stratix10-svc: schedule thread out when there is no data reveived
Date: Fri, 12 Nov 2021 13:35:13 -0600	[thread overview]
Message-ID: <9ead8789-381d-2358-0c11-95b3350ca63e@kernel.org> (raw)
In-Reply-To: <20211109074613.13994-1-Meng.Li@windriver.com>



On 11/9/21 1:46 AM, Meng Li wrote:
> From: Meng Li <meng.li@windriver.com>
> 
> In thread svc_normal_to_secure_thread(), function kfifo_out_spinlocked()
> always return, so this thread can't release cpu even if there is no data
> received, and cause cpu is under heave load status. System performance

do you mean "heavy"?

> is poor.
> 
> This issue is introduced by commit 7ca5ce896524("firmware: add Intel
> Stratix10 service layer driver")
> 
> Therefore, schedule this thread out when there is no data reveived, and

s/reveived/received

> wake it up after sending data to it.
> 
> Fixes: 7ca5ce896524 ("firmware: add Intel Stratix10 service layer driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Meng Li <Meng.Li@windriver.com>
> ---
>   drivers/firmware/stratix10-svc.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/firmware/stratix10-svc.c b/drivers/firmware/stratix10-svc.c
> index 2a7687911c09..ddb86d441726 100644
> --- a/drivers/firmware/stratix10-svc.c
> +++ b/drivers/firmware/stratix10-svc.c
> @@ -365,8 +365,10 @@ static int svc_normal_to_secure_thread(void *data)
>   						pdata, sizeof(*pdata),
>   						&ctrl->svc_fifo_lock);
>   
> -		if (!ret_fifo)
> +		if (!ret_fifo) {
> +			schedule_timeout_interruptible(MAX_SCHEDULE_TIMEOUT);
>   			continue;
> +		}
>   
>   		pr_debug("get from FIFO pa=0x%016x, command=%u, size=%u\n",
>   			 (unsigned int)pdata->paddr, pdata->command,
> @@ -861,6 +863,7 @@ int stratix10_svc_send(struct stratix10_svc_chan *chan, void *msg)
>   	ret = kfifo_in_spinlocked(&chan->ctrl->svc_fifo, p_data,
>   				  sizeof(*p_data),
>   				  &chan->ctrl->svc_fifo_lock);
> +	wake_up_process(chan->ctrl->task);
>   
>   	kfree(p_data);
>   
> 

I've made above spelling fixes and have applied it.

Thanks,
Dinh

  reply	other threads:[~2021-11-12 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  7:46 Meng Li
2021-11-12 19:35 ` Dinh Nguyen [this message]
2021-11-15  1:45   ` Li, Meng

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=9ead8789-381d-2358-0c11-95b3350ca63e@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=Meng.Li@windriver.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®