From: "lihuisong (C)" <lihuisong@huawei.com>
To: Robbie King <robbiek@xsightlabs.com>,
Sudeep Holla <sudeep.holla@kernel.org>
Cc: <jassisinghbrar@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <linuxarm@huawei.com>,
<zhanjie9@hisilicon.com>, <lihuisong@huawei.com>
Subject: Re: [PATCH] mailbox: pcc: Fix probabilistic command execution timeout
Date: Tue, 26 May 2026 14:28:21 +0800 [thread overview]
Message-ID: <72499009-892c-42b9-93b2-5729ddd5cc71@huawei.com> (raw)
In-Reply-To: <27794f6b-cd8f-4b38-a5c0-eed30858f8e2@xsightlabs.com>
On 4/27/2026 10:28 PM, Robbie King wrote:
> On 4/21/2026 6:05 AM, Sudeep Holla wrote:
>> On Fri, Apr 17, 2026 at 11:14:29AM +0800, 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.
>>>
>> Are you seeing the issue on real platforms or you are just reviewing the
>> code. I would like to test it on the platform I use but I don't have it
>> handy, so may take some time.
>>
>> I have added Robbie King who also has helped in testing this PCC driver
>> in the past.
>>
> I was unable to apply the patch to our current kernel version. We are in the
> process of updating our kernel modules to support 7.0, once that effort is
> finished I can run a few of our current regressions against the patch.
Hi Robbie King,
Can you help test this patch now?
Or we can fix the conflict to test it on your current kernel.
next prev parent reply other threads:[~2026-05-26 6:28 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) [this message]
2026-06-25 9:01 ` lihuisong (C)
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=72499009-892c-42b9-93b2-5729ddd5cc71@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=robbiek@xsightlabs.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®