From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>,
alsa-devel@alsa-project.org, tiwai@suse.de
Cc: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
amadeuszx.slawinski@linux.intel.com
Subject: Re: [Intel-gfx] [PATCH v2] ALSA: hda/i915 - avoid hung task timeout in i915 wait
Date: Wed, 9 Mar 2022 08:36:54 +0000 [thread overview]
Message-ID: <f9f6f831-a05d-2d20-8ade-ab717f342ba5@linux.intel.com> (raw)
In-Reply-To: <20220308172759.920551-1-kai.vehmanen@linux.intel.com>
On 08/03/2022 17:27, Kai Vehmanen wrote:
> If kernel is built with hung task detection enabled and
> CONFIG_DEFAULT_HUNG_TASK_TIMEOUT set to less than 60 seconds,
> snd_hdac_i915_init() will trigger the hung task timeout in case i915 is
> not available and taint the kernel.
>
> Split the 60sec wait into a loop of smaller waits to avoid this.
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
> Co-developed-by: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> ---
> sound/hda/hdac_i915.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> Changes V1->V2:
> - address local variable naming issue raised by Amadeusz
> and use Takashi's proposal
>
> diff --git a/sound/hda/hdac_i915.c b/sound/hda/hdac_i915.c
> index 454474ac5716..aa48bed7baf7 100644
> --- a/sound/hda/hdac_i915.c
> +++ b/sound/hda/hdac_i915.c
> @@ -143,7 +143,7 @@ static bool i915_gfx_present(void)
> int snd_hdac_i915_init(struct hdac_bus *bus)
> {
> struct drm_audio_component *acomp;
> - int err;
> + int err, i;
>
> if (!i915_gfx_present())
> return -ENODEV;
> @@ -159,9 +159,11 @@ int snd_hdac_i915_init(struct hdac_bus *bus)
> if (!acomp->ops) {
> if (!IS_ENABLED(CONFIG_MODULES) ||
> !request_module("i915")) {
> - /* 60s timeout */
Where does this 60s come from and why is the fix to work around
DEFAULT_HUNG_TASK_TIMEOUT in a hacky way deemed okay? For instance would
limiting the wait here to whatever the kconfig is set to be an option?
Regards,
Tvrtko
> - wait_for_completion_timeout(&acomp->master_bind_complete,
> - msecs_to_jiffies(60 * 1000));
> + /* max 60s timeout */
> + for (i = 0; i < 60; i++)
> + if (wait_for_completion_timeout(&acomp->master_bind_complete,
> + msecs_to_jiffies(1000)))
> + break;
> }
> }
> if (!acomp->ops) {
>
> base-commit: fd7698cf0858f8c5e659b655109cd93c2f15cdd3
next prev parent reply other threads:[~2022-03-09 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 17:27 [PATCH v2] ALSA: hda/i915 - avoid hung task timeout in i915 wait Kai Vehmanen
2022-03-09 8:36 ` Tvrtko Ursulin [this message]
2022-03-09 8:39 ` [Intel-gfx] " Kai Vehmanen
2022-03-09 9:02 ` Tvrtko Ursulin
2022-03-09 9:23 ` Takashi Iwai
2022-03-09 9:48 ` Tvrtko Ursulin
2022-03-09 9:55 ` Takashi Iwai
2022-03-09 13:05 ` Kai Vehmanen
2022-03-09 8:55 ` Takashi Iwai
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=f9f6f831-a05d-2d20-8ade-ab717f342ba5@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=tiwai@suse.de \
/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).