From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Boyd <swboyd@chromium.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Mark Gross <markgross@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
platform-driver-x86@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Prashant Malani <pmalani@chromium.org>
Subject: Re: [PATCH v4 0/4] platform/x86: intel_scu_ipc: Timeout fixes
Date: Mon, 18 Sep 2023 15:15:47 +0200 [thread overview]
Message-ID: <25f3c9e1-0b67-5a83-e69b-9a7e0225c267@redhat.com> (raw)
In-Reply-To: <20230913212723.3055315-1-swboyd@chromium.org>
Hi,
On 9/13/23 23:27, Stephen Boyd wrote:
> I recently looked at some crash reports on ChromeOS devices that call
> into this intel_scu_ipc driver. They were hitting timeouts, and it
> certainly looks possible for those timeouts to be triggering because of
> scheduling issues. Once things started going south, the timeouts kept
> coming. Maybe that's because the other side got seriously confused? I
> don't know.
>
> I added some sleeps to these paths to trigger the timeout behavior to
> make sure the code works. Simply sleeping for a long time in busy_loop()
> hits the timeout, which could happen if the system is scheduling lots of
> other things at the time.
>
> I couldn't really test the last patch because forcing a timeout or
> returning immediately wasn't fast enough to trigger the second
> transaction to run into the first one being processed.
Thank you for your patch, I've applied this patch to my fixes
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=fixes
Note it will show up in my fixes branch once I've pushed my
local branch there, which might take a while.
I will include this patch in my next fixes pull-req to Linus
for the current kernel development cycle.
Regards,
Hans
> Changes from v3 (https://lore.kernel.org/r/20230911193937.302552-1-swboyd@chromium.org):
> * Use readx_poll_timeout() to shorten a line
>
> Changes from v2 (https://lore.kernel.org/r/20230906180944.2197111-1-swboyd@chromium.org):
> * Use read_poll_timeout() helper in patch #1 (again)
> * New patch #3 to fix bug pointed out by Andy
> * Consolidate more code into busy check in patch #4
>
> Changes from v1 (https://lore.kernel.org/r/20230831011405.3246849-1-swboyd@chromium.org):
> * Don't use read_poll_timeout() helper in patch 1, just add code
> * Rewrite patch 2 to be simpler
> * Make intel_scu_ipc_busy() return -EBUSY when busy
> * Downgrade dev_err() to dev_dbg() in intel_scu_ipc_busy()
>
> Stephen Boyd (4):
> platform/x86: intel_scu_ipc: Check status after timeout in busy_loop()
> platform/x86: intel_scu_ipc: Check status upon timeout in
> ipc_wait_for_interrupt()
> platform/x86: intel_scu_ipc: Don't override scu in
> intel_scu_ipc_dev_simple_command()
> platform/x86: intel_scu_ipc: Fail IPC send if still busy
>
> drivers/platform/x86/intel_scu_ipc.c | 66 +++++++++++++++++-----------
> 1 file changed, 40 insertions(+), 26 deletions(-)
>
> Cc: Prashant Malani <pmalani@chromium.org>
>
> base-commit: 2dde18cd1d8fac735875f2e4987f11817cc0bc2c
prev parent reply other threads:[~2023-09-18 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 21:27 [PATCH v4 0/4] platform/x86: intel_scu_ipc: Timeout fixes Stephen Boyd
2023-09-13 21:27 ` [PATCH v4 1/4] platform/x86: intel_scu_ipc: Check status after timeout in busy_loop() Stephen Boyd
2023-09-15 13:42 ` Ilpo Järvinen
2023-09-13 21:27 ` [PATCH v4 2/4] platform/x86: intel_scu_ipc: Check status upon timeout in ipc_wait_for_interrupt() Stephen Boyd
2023-09-15 13:49 ` Ilpo Järvinen
2023-09-18 13:10 ` Hans de Goede
2023-09-18 13:26 ` Ilpo Järvinen
2023-09-13 21:27 ` [PATCH v4 3/4] platform/x86: intel_scu_ipc: Don't override scu in intel_scu_ipc_dev_simple_command() Stephen Boyd
2023-09-15 14:45 ` Ilpo Järvinen
2023-09-16 11:14 ` Andy Shevchenko
2023-09-13 21:27 ` [PATCH v4 4/4] platform/x86: intel_scu_ipc: Fail IPC send if still busy Stephen Boyd
2023-09-15 14:49 ` Ilpo Järvinen
2023-09-18 13:15 ` Hans de Goede [this message]
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=25f3c9e1-0b67-5a83-e69b-9a7e0225c267@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).