From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: devel@driverdev.osuosl.org, phil@raspberrypi.org,
linux-kernel@vger.kernel.org, eric@anholt.net,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] staging: vchiq: use interruptible waits
Date: Fri, 5 Apr 2019 14:40:27 +0200 [thread overview]
Message-ID: <762bb0f7-b9d1-3182-524b-6cdec87a08f8@i2se.com> (raw)
In-Reply-To: <20190405113423.14495-1-nsaenzjulienne@suse.de>
Hi Nicolas,
Am 05.04.19 um 13:34 schrieb Nicolas Saenz Julienne:
> Hi,
> this series tries to address an issue that came up in Raspbian's kernel
> tree [1]. After pulling from upstream some changes that moved wait calls
> from a custom implementation to the more standard killable family some
> users complained that all the VCHIQ threads showed up in D state (which
> is the expected behaviour).
this issue has already been noticed in mainline distributions [1],[2].
> The custom implementation we deleted tried to mimic the killable family
> of functions, yet accepted more signals than the later. SIGKILL |
> SIGINT | SIGQUIT | SIGTRAP | SIGSTOP | SIGCONT for the custom
> implementation as opposed to plain old SIGKILL.
>
> Raspbian maintainers decided roll back some of those changes and leave
> the wait functions as interruptible. Hence creating some divergence
> between both trees.
>
> One could argue that not liking having the threads stuck in D state is
> not really a software issue. It's more a cosmetic thing that can scare
> people when they look at "uptime". On the other hand, if we are ever to
> unstage this driver, we'd really need a proper justification for using
> the killable family of functions. Which I think it's not really clear at
> the moment.
I like to see this decision as a short comment in the code to prevent
other for doing this mistake again.
Thanks
Stefan
>
> As Raspbian's kernel has been working for a while with interruptible
> waits I propose we follow through. If needed we can always go back to
> killable. But at least we'll have a proper understanding on the actual
> needs. In the end the driver is in staging, and the potential for errors
> small.
>
> Regards,
> Nicolas
>
> [1] https://github.com/raspberrypi/linux/issues/2881
>
[1] - https://archlinuxarm.org/forum/viewtopic.php?f=65&t=13485
[2] -
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/GBXGJ7DOV5CQQXFPOZCXTRD6W4BEPT4Q/
prev parent reply other threads:[~2019-04-05 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 11:34 Nicolas Saenz Julienne
2019-04-05 11:34 ` [PATCH 1/3] Revert "staging: vchiq_2835_arm: quit using custom down_interruptible()" Nicolas Saenz Julienne
2019-04-05 12:02 ` Dan Carpenter
2019-04-05 12:22 ` Nicolas Saenz Julienne
2019-04-05 11:34 ` [PATCH 2/3] Revert "staging: vchiq: switch to wait_for_completion_killable" Nicolas Saenz Julienne
2019-04-05 11:34 ` [PATCH 3/3] staging: vchiq: make wait events interruptible Nicolas Saenz Julienne
2019-04-05 12:46 ` Stefan Wahren
2019-04-05 12:40 ` Stefan Wahren [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=762bb0f7-b9d1-3182-524b-6cdec87a08f8@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=phil@raspberrypi.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
all inboxes | Powered by JetHome®