From: Ingo Molnar <mingo@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Matthew Wilcox <matthew@wil.cx>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] semaphore: use raw_spin_lock_irq instead of raw_spin_lock_irqsave
Date: Thu, 21 Jun 2018 15:50:14 +0200 [thread overview]
Message-ID: <20180621135014.GA31371@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1805301120180.3104@file01.intranet.prod.int.rdu2.redhat.com>
* Mikulas Patocka <mpatocka@redhat.com> wrote:
> The sleeping functions down, down_interruptible, down_killable and
> down_timeout can't be called with interrupts disabled, so we don't have to
> save and restore interrupt flag.
>
> This patch avoids the costly pushf and popf instructions on the semaphore
> path.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
>
> ---
> kernel/locking/semaphore.c | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
I've applied this to the locking tree, I suspect we can do this on the condition
that it doesn't explode in early boot code (which has irqs disabled) and doesn't
generate early boot lockdep splats either.
Thanks,
Ingo
next prev parent reply other threads:[~2018-06-21 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 15:24 [PATCH] semaphore: use raw_spin_lock_irq instead of raw_spin_lock_irqsave Mikulas Patocka
2018-06-21 13:50 ` Ingo Molnar [this message]
2018-06-21 14:02 ` Ingo Molnar
2018-06-21 14:17 ` Ingo Molnar
2018-06-21 14:20 ` Juergen Gross
2018-06-21 14:28 ` Ingo Molnar
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=20180621135014.GA31371@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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