mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: <sudeep.holla@kernel.org>, <jassisinghbrar@gmail.com>,
	<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Cc: <linuxarm@huawei.com>, <zhanjie9@hisilicon.com>, <lihuisong@huawei.com>
Subject: Re: [PATCH] mailbox: pcc: Fix probabilistic command execution timeout
Date: Thu, 25 Jun 2026 17:01:24 +0800	[thread overview]
Message-ID: <28cc8e74-617a-4c20-829a-99d0ebaea5f0@huawei.com> (raw)
In-Reply-To: <20260417031429.2509443-1-lihuisong@huawei.com>

Hi Sudeep,

Can you help review this patch?


On 4/17/2026 11:14 AM, Huisong Li wrote:
> In some scenarios, PCC command may experience probabilistic timeout.
> This is primarily caused by the chan_in_use flag being updated after
> ringing the doorbell, coupled with a lack of proper memory barriers
> across CPU cores.
>
> On fast platforms, a race condition occurs: the platform processing
> completes and triggers an interrupt before the local CPU sets
> chan_in_use to true. When the interrupt handler pcc_mbox_irq() runs,
> it reads chan_in_use as false and incorrectly ignores the interrupt.
>
> This patch fixes the race by:
> 1. Moving the chan_in_use update before ringing the doorbell.
> 2. Using smp_store_release() to ensure the flag update is visible
>     to other cores before subsequent hardware or software actions
>     are triggered.
> 3. Using smp_load_acquire() in the interrupt handler to ensure the
>     latest flag value is read before deciding to skip the interrupt.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
>   drivers/mailbox/pcc.c | 20 ++++++++++++++++----
>   1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mailbox/pcc.c b/drivers/mailbox/pcc.c
> index 636879ae1db7..f45fccd635b6 100644
> --- a/drivers/mailbox/pcc.c
> +++ b/drivers/mailbox/pcc.c
> @@ -320,8 +320,13 @@ static irqreturn_t pcc_mbox_irq(int irq, void *p)
>   	if (pcc_chan_reg_read_modify_write(&pchan->plat_irq_ack))
>   		return IRQ_NONE;
>   
> +	/*
> +	 * For Master Subspaces, we must ensure we see the latest chan_in_use
> +	 * value updated by pcc_send_data() on another core. smp_load_acquire
> +	 * provides the necessary barrier to avoid probabilistic IRQ misses.
> +	 */
>   	if (pchan->type == ACPI_PCCT_TYPE_EXT_PCC_MASTER_SUBSPACE &&
> -	    !pchan->chan_in_use)
> +	    !smp_load_acquire(&pchan->chan_in_use))
>   		return IRQ_NONE;
>   
>   	if (!pcc_mbox_cmd_complete_check(pchan))
> @@ -336,7 +341,7 @@ static irqreturn_t pcc_mbox_irq(int irq, void *p)
>   	 * where the flag is set again to start new transfer. This is
>   	 * required to avoid any possible race in updatation of this flag.
>   	 */
> -	pchan->chan_in_use = false;
> +	smp_store_release(&pchan->chan_in_use, false);
>   	mbox_chan_received_data(chan, NULL);
>   	mbox_chan_txdone(chan, 0);
>   
> @@ -438,9 +443,16 @@ static int pcc_send_data(struct mbox_chan *chan, void *data)
>   	if (ret)
>   		return ret;
>   
> +	/*
> +	 * Set chan_in_use before ringing the doorbell. Using smp_store_release
> +	 * ensures the flag is visible to the interrupt handler before the
> +	 * hardware is actually notified.
> +	 */
> +	if (pchan->plat_irq > 0)
> +		smp_store_release(&pchan->chan_in_use, true);
>   	ret = pcc_chan_reg_read_modify_write(&pchan->db);
> -	if (!ret && pchan->plat_irq > 0)
> -		pchan->chan_in_use = true;
> +	if (ret && pchan->plat_irq > 0)
> +		smp_store_release(&pchan->chan_in_use, false);
>   
>   	return ret;
>   }

  parent reply	other threads:[~2026-06-25  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  3:14 Huisong Li
2026-04-21 10:05 ` Sudeep Holla
2026-04-21 11:21   ` lihuisong (C)
2026-04-27 14:28   ` Robbie King
2026-05-26  6:28     ` lihuisong (C)
2026-06-25  9:01 ` lihuisong (C) [this message]
2026-06-27 14:31 ` Sudeep Holla
2026-06-29 13:46   ` lihuisong (C)

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=28cc8e74-617a-4c20-829a-99d0ebaea5f0@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=sudeep.holla@kernel.org \
    --cc=zhanjie9@hisilicon.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®