From: Sam Bobroff <sbobroff@linux.ibm.com>
To: Oliver <oohall@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
aik@ozlabs.ru,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: eeh_event: convert semaphore to completion
Date: Tue, 11 Dec 2018 10:33:01 +1100 [thread overview]
Message-ID: <20181210233300.GA14707@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <CAOSf1CHqxaGdz_F0EifqHmD+0ZgKVno7aRZEXUG1880C5YvHGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]
On Tue, Dec 11, 2018 at 10:18:31AM +1100, Oliver wrote:
> On Tue, Dec 11, 2018 at 8:52 AM Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > For this use case, completions and semaphores are equivalent,
> > but semaphores are an awkward interface that should generally
> > be avoided, so use the completion instead.
>
> IIRC Sam has been reworking the locking used inside of EEH so this is
> probably going to clash with his changes. Converting to a completion
> is probably a good idea, but we might want to do it as a part of his
> series since it's going to collide with this anyway.
>
> Sam, what do you think?
It's such a small change, I don't think it will cause any problems for
the rework. Anyway it seems like a good change, so I'd prefer to see it
go in :-)
Cheers,
Sam.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > arch/powerpc/kernel/eeh_event.c | 9 +++------
> > 1 file changed, 3 insertions(+), 6 deletions(-)
> >
> > diff --git a/arch/powerpc/kernel/eeh_event.c b/arch/powerpc/kernel/eeh_event.c
> > index 61c9356bf9c9..227e57f980df 100644
> > --- a/arch/powerpc/kernel/eeh_event.c
> > +++ b/arch/powerpc/kernel/eeh_event.c
> > @@ -35,7 +35,7 @@
> > */
> >
> > static DEFINE_SPINLOCK(eeh_eventlist_lock);
> > -static struct semaphore eeh_eventlist_sem;
> > +static DECLARE_COMPLETION(eeh_eventlist_event);
> > static LIST_HEAD(eeh_eventlist);
> >
> > /**
> > @@ -55,7 +55,7 @@ static int eeh_event_handler(void * dummy)
> > struct eeh_pe *pe;
> >
> > while (!kthread_should_stop()) {
> > - if (down_interruptible(&eeh_eventlist_sem))
> > + if (wait_for_completion_interruptible(&eeh_eventlist_event))
> > break;
> >
> > /* Fetch EEH event from the queue */
> > @@ -102,9 +102,6 @@ int eeh_event_init(void)
> > struct task_struct *t;
> > int ret = 0;
> >
> > - /* Initialize semaphore */
> > - sema_init(&eeh_eventlist_sem, 0);
> > -
> > t = kthread_run(eeh_event_handler, NULL, "eehd");
> > if (IS_ERR(t)) {
> > ret = PTR_ERR(t);
> > @@ -142,7 +139,7 @@ int eeh_send_failure_event(struct eeh_pe *pe)
> > spin_unlock_irqrestore(&eeh_eventlist_lock, flags);
> >
> > /* For EEH deamon to knick in */
> > - up(&eeh_eventlist_sem);
> > + complete(&eeh_eventlist_event);
> >
> > return 0;
> > }
> > --
> > 2.20.0
> >
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-10 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:51 [PATCH] powerpc: eeh_event: convert semaphore to completion Arnd Bergmann
2018-12-10 23:18 ` Oliver
2018-12-10 23:33 ` Sam Bobroff [this message]
2018-12-22 9:54 ` Michael Ellerman
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=20181210233300.GA14707@tungsten.ozlabs.ibm.com \
--to=sbobroff@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=paulus@samba.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).