From: Davidlohr Bueso <dave@stgolabs.net>
To: akpm@linux-foundation.org
Cc: dave@stgolabs.net, linux-kernel@vger.kernel.org
Subject: [PATCH -next 0/6] treewide: Remove redundant branch predictions around signal_pending family
Date: Thu, 15 Nov 2018 16:27:07 -0800 [thread overview]
Message-ID: <20181116002713.8474-1-dave@stgolabs.net> (raw)
Hi,
This series trivially gets rid of users of signal_pending (and family) explicitly
wrapping the call around an unlikely(). It is redundant as internally this is
already done for us via signal_pending() and [__]fatal_signal_pending().
All patches are independent, so I split it up in case folks want to pick up bits
separately.
Compile tested only. Please consider for v4.21.
Thanks!
Davidlohr Bueso (6):
locking/mutex: Remove caller signal_pending branch predictions
kernel/sched: Remove caller signal_pending branch predictions
arch/arc: Remove caller signal_pending_branch predictions
mm: Remove caller signal_pending branch predictions
drivers/i2c: Remove caller signal_pending branch predictions
fs: Remove caller signal_pending branch predictions
arch/arc/mm/fault.c | 2 +-
drivers/i2c/busses/i2c-ibm_iic.c | 2 +-
fs/afs/fs_probe.c | 2 +-
fs/afs/vl_probe.c | 2 +-
fs/buffer.c | 2 +-
fs/exec.c | 4 ++--
fs/orangefs/orangefs-bufmap.c | 2 +-
kernel/locking/mutex.c | 2 +-
kernel/sched/core.c | 2 +-
kernel/sched/swait.c | 2 +-
kernel/sched/wait.c | 2 +-
mm/filemap.c | 2 +-
mm/gup.c | 2 +-
mm/hugetlb.c | 2 +-
14 files changed, 15 insertions(+), 15 deletions(-)
--
2.16.4
next reply other threads:[~2018-11-16 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 0:27 Davidlohr Bueso [this message]
2018-11-16 0:27 ` [PATCH 1/6] locking/mutex: Remove caller signal_pending branch predictions Davidlohr Bueso
2018-11-16 0:27 ` [PATCH 2/6] kernel/sched: " Davidlohr Bueso
2018-11-16 0:27 ` [PATCH 3/6] arch/arc: Remove caller signal_pending_branch predictions Davidlohr Bueso
2018-11-16 0:27 ` [PATCH 4/6] mm: Remove caller signal_pending branch predictions Davidlohr Bueso
2018-11-16 0:27 ` [PATCH 5/6] drivers/i2c: " Davidlohr Bueso
2018-11-27 12:01 ` [5/6] " Wolfram Sang
2018-11-16 0:27 ` [PATCH 6/6] fs: " Davidlohr Bueso
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=20181116002713.8474-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.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).