From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
DanielWagnerwagi@monom.org, Boqun Feng <boqun.feng@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Ming Lei <ming.lei@redhat.com>, "Li, Yi" <yi1.li@linux.intel.com>,
"AKASHI, Takahiro" <takahiro.akashi@linaro.org>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Petr Mladek <pmladek@suse.com>,
Andrew Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@linux.intel.com>, "Theodore Ts'o" <tytso@mit.edu>,
oss-drivers@netronome.com
Subject: Re: [PATCH] firmware: wake all waiters
Date: Wed, 12 Jul 2017 20:45:19 +0200 [thread overview]
Message-ID: <20170712184519.GV21846@wotan.suse.de> (raw)
In-Reply-To: <CA+55aFwwyx61OdiZA0KF4Hs68D6SKO5m7vdru_z=Qh3pPnr6Dw@mail.gmail.com>
On Wed, Jul 05, 2017 at 09:33:38AM -0700, Linus Torvalds wrote:
> On Wed, Jul 5, 2017 at 9:18 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > In any case, I'm not seeing why you call it idiotic.
>
> Have you read the problems?
>
> There were originally three users:
>
> - one of them is firmware loading, and it was actively *buggy* due to
> using hat shit interface, and it's going away
To be fair the issue with the firmware loading was due to a regression on the
port from using swait/completion to swait. swake_up() was used instead of
swake_up_all(). Before the port complate_all() was used instead of just
complete().
So I would personally not add the firmware API to the list of reasons why swait
would be crap.
The more *general* semantics issue you pointed out with swake_up() though seem
more reasonable to be attacking the swait API and those are best followed on
the other thread [0].
I should also point out that there are *other* issues with the firmware API on
this whole wait stuff, but that have been present since even before when we
were using the regular wait / completion API -- a wake was never issued upon an
error in some situations on some kernel builds. I have a fix for that now along
with a test case for it which I'll post soon. After all these fixes the code
works as expected with either the swait API or the good 'ol wait/completion
API. But given swait is still out by you as only specialized I did already post
patches to revert the firmware API to switch back to the wait/completion API.
[0] https://lkml.kernel.org/r/CA+55aFykNULx-b6M6FmUYdK2cn-OJKKfjaPwLN5xZGK+bioGaA@mail.gmail.com
Luis
prev parent reply other threads:[~2017-07-12 18:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 23:37 [PATCH] firmware: wake all waiters Jakub Kicinski
2017-06-26 21:20 ` Luis R. Rodriguez
2017-06-26 21:23 ` [PATCH v2] firmware: fix batched requests - " Luis R. Rodriguez
2017-06-29 15:16 ` Greg KH
2017-06-29 15:17 ` Greg KH
2017-06-29 17:36 ` Luis R. Rodriguez
2017-06-26 23:41 ` [PATCH] firmware: " Luis R. Rodriguez
2017-06-27 2:10 ` Jakub Kicinski
2017-06-27 16:39 ` Luis R. Rodriguez
2017-06-27 21:25 ` Jakub Kicinski
2017-06-27 22:24 ` Luis R. Rodriguez
2017-06-27 22:39 ` Jakub Kicinski
2017-06-27 23:50 ` Luis R. Rodriguez
2017-06-28 7:06 ` [systemd-devel] " Lennart Poettering
2017-06-28 16:06 ` Luis R. Rodriguez
2017-06-28 16:21 ` Lennart Poettering
2017-06-28 17:57 ` Luis R. Rodriguez
2017-06-29 19:56 ` Daniel Wagner
2017-06-27 17:48 ` Bjorn Andersson
2017-06-27 18:03 ` Luis R. Rodriguez
2017-06-27 18:59 ` Bjorn Andersson
2017-06-27 19:08 ` Luis R. Rodriguez
2017-06-27 19:52 ` Bjorn Andersson
2017-06-27 20:24 ` Luis R. Rodriguez
2017-06-26 21:44 ` Linus Torvalds
2017-06-26 23:30 ` Luis R. Rodriguez
2017-06-26 23:43 ` Linus Torvalds
2017-06-27 0:15 ` Luis R. Rodriguez
2017-06-28 13:45 ` Davidlohr Bueso
2017-06-28 15:58 ` Luis R. Rodriguez
2017-06-28 19:03 ` Davidlohr Bueso
2017-06-29 19:08 ` Davidlohr Bueso
2017-06-29 19:48 ` Luis R. Rodriguez
2017-06-30 16:32 ` Davidlohr Bueso
2017-07-05 16:18 ` Peter Zijlstra
2017-07-05 16:33 ` Linus Torvalds
2017-07-12 18:45 ` Luis R. Rodriguez [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=20170712184519.GV21846@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=DanielWagnerwagi@monom.org \
--cc=alan@linux.intel.com \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jakub.kicinski@netronome.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ming.lei@redhat.com \
--cc=mtosatti@redhat.com \
--cc=oss-drivers@netronome.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=yi1.li@linux.intel.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;
as well as URLs for NNTP newsgroup(s).