From: Jakub Kicinski <kuba@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Alexander Lobakin" <aleksander.lobakin@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Helge Deller" <deller@gmx.de>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Borislav Petkov" <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Jiri Kosina" <jikos@kernel.org>,
"Miroslav Benes" <mbenes@suse.cz>,
"Petr Mladek" <pmladek@suse.com>,
"Joe Lawrence" <joe.lawrence@redhat.com>,
"Colin Ian King" <colin.king@canonical.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
linux-csky@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
live-patching@vger.kernel.org, 王贇 <yun.wang@linux.alibaba.com>,
"Guo Ren" <guoren@kernel.org>
Subject: Re: [PATCH] tracing: Have all levels of checks prevent recursion
Date: Fri, 21 Jul 2023 18:22:35 -0700 [thread overview]
Message-ID: <20230721182235.6617a466@kernel.org> (raw)
In-Reply-To: <20230721122632.56b4df6c@gandalf.local.home>
On Fri, 21 Jul 2023 12:26:32 -0400 Steven Rostedt wrote:
> > if (!(in_hardirq() || irqs_disabled()))
> >
>
> Yeah, probably.
>
> > , nothing more elegant / already existing / ...?
>
> It's not a common check. What would you call that?
Looks like Olek started the weekend already so let me answer.
He's trying to check if we can use a fast path cache which takes
a _bh spin lock.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Alexander Lobakin" <aleksander.lobakin@intel.com>,
"Peter Zijlstra" <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Helge Deller" <deller@gmx.de>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Borislav Petkov" <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Jiri Kosina" <jikos@kernel.org>,
"Miroslav Benes" <mbenes@suse.cz>,
"Petr Mladek" <pmladek@suse.com>,
"Joe Lawrence" <joe.lawrence@redhat.com>,
"Colin Ian King" <colin.king@canonical.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Jisheng Zhang" <jszhang@kernel.org>,
linux-csky@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
live-patching@vger.kernel.org, 王贇 <yun.wang@linux.alibaba.com>,
"Guo Ren" <guoren@kernel.org>
Subject: Re: [PATCH] tracing: Have all levels of checks prevent recursion
Date: Fri, 21 Jul 2023 18:22:35 -0700 [thread overview]
Message-ID: <20230721182235.6617a466@kernel.org> (raw)
In-Reply-To: <20230721122632.56b4df6c@gandalf.local.home>
On Fri, 21 Jul 2023 12:26:32 -0400 Steven Rostedt wrote:
> > if (!(in_hardirq() || irqs_disabled()))
> >
>
> Yeah, probably.
>
> > , nothing more elegant / already existing / ...?
>
> It's not a common check. What would you call that?
Looks like Olek started the weekend already so let me answer.
He's trying to check if we can use a fast path cache which takes
a _bh spin lock.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 王贇 <yun.wang@linux.alibaba.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Paul Mackerras" <paulus@samba.org>,
"Jisheng Zhang" <jszhang@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
live-patching@vger.kernel.org, linux-riscv@lists.infradead.org,
"Miroslav Benes" <mbenes@suse.cz>,
"Joe Lawrence" <joe.lawrence@redhat.com>,
"Helge Deller" <deller@gmx.de>,
x86@kernel.org, linux-csky@vger.kernel.org,
"Ingo Molnar" <mingo@redhat.com>,
"Petr Mladek" <pmladek@suse.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Jiri Kosina" <jikos@kernel.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Borislav Petkov" <bp@alien8.de>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-parisc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Alexander Lobakin" <aleksander.lobakin@intel.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>
Subject: Re: [PATCH] tracing: Have all levels of checks prevent recursion
Date: Fri, 21 Jul 2023 18:22:35 -0700 [thread overview]
Message-ID: <20230721182235.6617a466@kernel.org> (raw)
In-Reply-To: <20230721122632.56b4df6c@gandalf.local.home>
On Fri, 21 Jul 2023 12:26:32 -0400 Steven Rostedt wrote:
> > if (!(in_hardirq() || irqs_disabled()))
> >
>
> Yeah, probably.
>
> > , nothing more elegant / already existing / ...?
>
> It's not a common check. What would you call that?
Looks like Olek started the weekend already so let me answer.
He's trying to check if we can use a fast path cache which takes
a _bh spin lock.
next prev parent reply other threads:[~2023-07-22 1:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 15:00 [PATCH] tracing: Have all levels of checks prevent recursion Steven Rostedt
2021-10-15 15:00 ` Steven Rostedt
2021-10-15 15:00 ` Steven Rostedt
2021-10-15 16:17 ` Peter Zijlstra
2021-10-15 16:17 ` Peter Zijlstra
2021-10-15 16:17 ` Peter Zijlstra
2021-10-15 17:35 ` Steven Rostedt
2021-10-15 17:35 ` Steven Rostedt
2021-10-15 17:35 ` Steven Rostedt
2021-10-15 17:58 ` Steven Rostedt
2021-10-15 17:58 ` Steven Rostedt
2021-10-15 17:58 ` Steven Rostedt
2021-10-15 18:04 ` Peter Zijlstra
2021-10-15 18:04 ` Peter Zijlstra
2021-10-15 18:04 ` Peter Zijlstra
2021-10-15 18:20 ` Steven Rostedt
2021-10-15 18:20 ` Steven Rostedt
2021-10-15 18:20 ` Steven Rostedt
2021-10-15 18:24 ` Peter Zijlstra
2021-10-15 18:24 ` Peter Zijlstra
2021-10-15 18:24 ` Peter Zijlstra
2021-10-15 19:00 ` Steven Rostedt
2021-10-15 19:00 ` Steven Rostedt
2021-10-15 19:00 ` Steven Rostedt
2021-10-15 18:25 ` Steven Rostedt
2021-10-15 18:25 ` Steven Rostedt
2021-10-15 18:25 ` Steven Rostedt
2023-07-21 15:34 ` Alexander Lobakin
2023-07-21 15:34 ` Alexander Lobakin
2023-07-21 15:34 ` Alexander Lobakin
2023-07-21 16:00 ` Steven Rostedt
2023-07-21 16:00 ` Steven Rostedt
2023-07-21 16:00 ` Steven Rostedt
2023-07-21 16:06 ` Alexander Lobakin
2023-07-21 16:06 ` Alexander Lobakin
2023-07-21 16:06 ` Alexander Lobakin
2023-07-21 16:26 ` Steven Rostedt
2023-07-21 16:26 ` Steven Rostedt
2023-07-21 16:26 ` Steven Rostedt
2023-07-22 1:22 ` Jakub Kicinski [this message]
2023-07-22 1:22 ` Jakub Kicinski
2023-07-22 1:22 ` Jakub Kicinski
2021-10-18 10:19 ` Petr Mladek
2021-10-18 10:19 ` Petr Mladek
2021-10-18 10:19 ` Petr Mladek
2021-10-18 13:50 ` Steven Rostedt
2021-10-18 13:50 ` Steven Rostedt
2021-10-18 13:50 ` Steven Rostedt
2021-10-18 15:09 ` Petr Mladek
2021-10-18 15:09 ` Petr Mladek
2021-10-18 15:09 ` Petr Mladek
2021-10-19 2:02 ` Steven Rostedt
2021-10-19 2:02 ` Steven Rostedt
2021-10-19 2:02 ` Steven Rostedt
2021-10-19 6:41 ` Petr Mladek
2021-10-19 6:41 ` Petr Mladek
2021-10-19 6:41 ` Petr Mladek
2021-10-19 13:00 ` Steven Rostedt
2021-10-19 13:00 ` Steven Rostedt
2021-10-19 13:00 ` Steven Rostedt
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=20230721182235.6617a466@kernel.org \
--to=kuba@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aleksander.lobakin@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=colin.king@canonical.com \
--cc=deller@gmx.de \
--cc=guoren@kernel.org \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=jszhang@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yun.wang@linux.alibaba.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.