From: "Jörn Engel" <joern@purestorage.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Uday Shankar <ushankar@purestorage.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Borislav Petkov <bp@alien8.de>, Len Brown <len.brown@intel.com>,
linux-hardening@vger.kernel.org, linux-acpi@vger.kernel.org,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH] Revert "ACPI, APEI, use raw spinlock in ERST"
Date: Wed, 23 Aug 2023 14:09:06 -0700 [thread overview]
Message-ID: <ZOZ1cmqF3G0XO0ZH@cork> (raw)
In-Reply-To: <ZOV1sM8xZ6+P48Z1@cork>
On Tue, Aug 22, 2023 at 07:57:52PM -0700, Jörn Engel wrote:
>
> You are right. I'm actually quite surprised how we turn a trylock into
> a spinning lock. Now I know, thank you!
On that subject, why do we turn a trylock into a spinning lock? Thomas,
is there a good argument against a patch like the one below?
If the question was ever considered, it seems to have happened outside
of mainline. At least I cannot find it in git history.
Jörn
--
If you cannot make a function run 100x faster, maybe you can
call it 100x less often.
-- Unknown
diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
index fcd9ad3f7f2e..5bda84d5879a 100644
--- a/kernel/locking/rtmutex.c
+++ b/kernel/locking/rtmutex.c
@@ -1255,11 +1255,13 @@ static int __sched rt_mutex_slowtrylock(struct rt_mutex_base *lock)
/*
* The mutex has currently no owner. Lock the wait lock and try to
* acquire the lock. We use irqsave here to support early boot calls.
*/
- raw_spin_lock_irqsave(&lock->wait_lock, flags);
+ ret = raw_spin_trylock_irqsave(&lock->wait_lock, flags);
+ if (!ret)
+ return 0;
ret = __rt_mutex_slowtrylock(lock);
raw_spin_unlock_irqrestore(&lock->wait_lock, flags);
next prev parent reply other threads:[~2023-08-23 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 1:09 [PATCH] Revert "ACPI, APEI, use raw spinlock in ERST" Uday Shankar
2023-08-22 1:56 ` Huang, Ying
2023-08-22 3:16 ` Jörn Engel
2023-08-22 23:45 ` Uday Shankar
2023-08-23 2:38 ` Huang, Ying
2023-08-23 2:57 ` Jörn Engel
2023-08-23 21:09 ` Jörn Engel [this message]
2023-08-23 2:28 ` Huang, Ying
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=ZOZ1cmqF3G0XO0ZH@cork \
--to=joern@purestorage.com \
--cc=bp@alien8.de \
--cc=gpiccoli@igalia.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=ushankar@purestorage.com \
--cc=ying.huang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.