From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: jeyu@kernel.org, jikos@kernel.org, pmladek@suse.com,
lpechacek@suse.cz, pavel@ucw.cz, live-patching@vger.kernel.org,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org
Subject: Re: [PATCH v3 1/2] livepatch: send a fake signal to all blocking tasks
Date: Fri, 3 Nov 2017 07:57:08 -0500 [thread overview]
Message-ID: <20171103125708.tzgn45iabb5sl36i@treble> (raw)
In-Reply-To: <alpine.LSU.2.21.1711030902250.31648@pobox.suse.cz>
On Fri, Nov 03, 2017 at 09:02:50AM +0100, Miroslav Benes wrote:
> On Thu, 2 Nov 2017, Josh Poimboeuf wrote:
>
> > On Tue, Oct 31, 2017 at 12:48:52PM +0100, Miroslav Benes wrote:
> > > +
> > > +/*
> > > + * Sends a fake signal to all non-kthread tasks with TIF_PATCH_PENDING set.
> > > + * Kthreads with TIF_PATCH_PENDING set are woken up. Only admin can request this
> > > + * action currently.
> > > + */
> > > +void klp_force_signals(void)
> >
> > Since "force" now has a separate meaning, it's a little confusing to
> > have it in the name of this function. How about klp_send_signals() or
> > klp_signal()?
>
> or klp_send_signal()?
It can send more than one signal, so I'd prefer the plural form:
klp_send_signals().
--
Josh
next prev parent reply other threads:[~2017-11-03 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 11:48 [PATCH v3 0/2] livepatch: Introduce signal and force sysfs attributes Miroslav Benes
2017-10-31 11:48 ` [PATCH v3 1/2] livepatch: send a fake signal to all blocking tasks Miroslav Benes
2017-11-01 15:06 ` Miroslav Benes
2017-11-01 15:13 ` Petr Mladek
2017-11-01 16:43 ` Oleg Nesterov
2017-11-02 10:36 ` Miroslav Benes
2017-11-02 14:08 ` Oleg Nesterov
2017-11-02 13:09 ` Josh Poimboeuf
2017-11-03 8:02 ` Miroslav Benes
2017-11-03 12:57 ` Josh Poimboeuf [this message]
2017-11-02 13:32 ` Josh Poimboeuf
2017-11-03 8:06 ` Miroslav Benes
2017-11-06 11:08 ` Pavel Machek
2017-10-31 11:48 ` [PATCH v3 2/2] livepatch: force transition process to finish Miroslav Benes
2017-11-01 15:32 ` Petr Mladek
2017-11-02 13:13 ` Josh Poimboeuf
2017-11-03 8:07 ` Miroslav Benes
2017-11-06 11:11 ` Pavel Machek
2017-11-06 12:03 ` Jiri Kosina
2017-11-09 11:14 ` Pavel Machek
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=20171103125708.tzgn45iabb5sl36i@treble \
--to=jpoimboe@redhat.com \
--cc=hpa@zytor.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=lpechacek@suse.cz \
--cc=luto@kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).