From: "lihuisong (C)" <lihuisong@huawei.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rafael@kernel.org>, <rafael.j.wysocki@intel.com>,
<wanghuiqiang@huawei.com>, <huangdaode@huawei.com>
Subject: Re: [PATCH 1/2] ACPI: PCC: replace wait_for_completion()
Date: Thu, 22 Sep 2022 10:29:06 +0800 [thread overview]
Message-ID: <cb2f3c9c-ab45-357d-8a56-1c64b535633c@huawei.com> (raw)
In-Reply-To: <20220921154737.az3d4ndxs3u3zwbl@bogus>
在 2022/9/21 23:47, Sudeep Holla 写道:
> On Tue, Sep 20, 2022 at 05:44:59PM +0800, Huisong Li wrote:
>> Currently, the function waiting for completion of mailbox operation is
>> 'wait_for_completion()'. The PCC method will be permanently blocked if
>> this mailbox message fails to execute. So this patch replaces it with
>> 'wait_for_completion_timeout()'. And set the timeout interval to an
>> arbitrary retries on top of nominal to prevent the remote processor is
>> slow to respond to PCC commands.
>>
> Sounds good to me. The only concern(may be not serious) is what happens
> if we receive response from the platform after the timeout. I have tested
If OS still cann't receive response in noramal latency(must be filled
accurately
as protocol said) + retries, there is a high probability that an
exception occurs.
Even if we receive response after the timeout, I think there may be no
impact,
but the response data in PCC share memory is ignored.
> for that in non ACPI non PCC context. I don't have a setup to trigger that
> with ACPI PCC + this patch to test. Other than that, I am fine with this:
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>
next prev parent reply other threads:[~2022-09-22 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 9:44 [PATCH 0/2] ACPI: PCC: add waiting timeout and fix Tx done interface Huisong Li
2022-09-20 9:44 ` [PATCH 1/2] ACPI: PCC: replace wait_for_completion() Huisong Li
2022-09-21 15:47 ` Sudeep Holla
2022-09-22 2:29 ` lihuisong (C) [this message]
2022-09-20 9:45 ` [PATCH 2/2] ACPI: PCC: fix Tx done interface in handler Huisong Li
2022-09-21 15:43 ` Sudeep Holla
2022-09-22 2:30 ` lihuisong (C)
2022-09-22 19:10 ` Rafael J. Wysocki
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=cb2f3c9c-ab45-357d-8a56-1c64b535633c@huawei.com \
--to=lihuisong@huawei.com \
--cc=huangdaode@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=wanghuiqiang@huawei.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®