From: Andrew Morton <akpm@linux-foundation.org>
To: v.narang@samsung.com
Cc: Dmitry Vyukov <dvyukov@google.com>,
Maninder Singh <maninder1.s@samsung.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michal Hocko <mhocko@suse.com>,
"vinmenon@codeaurora.org" <vinmenon@codeaurora.org>,
"gomonovych@gmail.com" <gomonovych@gmail.com>,
Ayush Mittal <ayush.m@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux-MM <linux-mm@kvack.org>,
AMIT SAHRAWAT <a.sahrawat@samsung.com>,
PANKAJ MISHRA <pankaj.m@samsung.com>
Subject: Re: [PATCH v2] mm/page_owner: ignore everything below the IRQ entry point
Date: Mon, 26 Mar 2018 12:52:28 -0700 [thread overview]
Message-ID: <20180326125228.1f40abb9a52f3674b1491aea@linux-foundation.org> (raw)
In-Reply-To: <20180326141717epcms5p4064a0fd4f594b2ff434f9b05cd1ea5ad@epcms5p4>
On Mon, 26 Mar 2018 19:47:17 +0530 Vaneet Narang <v.narang@samsung.com> wrote:
> Hi Dmitry,
>
> >Every user of stack_depot should filter out irq frames, without that
> >stack_depot will run out of memory sooner or later. so this is a
> >change in the right direction.
> >
> >Do we need to define empty version of in_irqentry_text? Shouldn't only
> >filter_irq_stacks be used by kernel code?
>
> We thought about this but since we were adding both the APIs filter_irq_stacks & in_irqentry_text
> in header file so we thought of defining empty definition for both as both the APIs are accessible
> to the module who is going to include header file.
>
> If you think empty definition of in_irqentry_text() is not requited then we will modify & resend the
> patch.
>
filter_irq_stacks() is too large to be inlined.
The CONFIG_STACKTRACE=n versions should be regular C functions, not
macros. But stacktrace.c decided to do them all as macros,
unfortunately.
in_irqentry_text() is probably too large to be inlined as well, and
should return bool.
Declarations for __irqentry_text_start and friends already exist in
include/asm-generic/sections.h (and, for some reason, also in
arch/arm/include/asm/traps.h) and should not be duplicated in
include/linux/stacktrace.h.
next prev parent reply other threads:[~2018-03-26 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180326100020epcas5p2b50b7541e66dccf4e49db634e5fe6b41@epcas5p2.samsung.com>
2018-03-26 9:58 ` [PATCH v2] mm/page_owner: ignore everything below the IRQ entry point Maninder Singh
2018-03-26 12:14 ` Dmitry Vyukov
[not found] ` <CGME20180326100020epcas5p2b50b7541e66dccf4e49db634e5fe6b41@epcms5p4>
2018-03-26 14:17 ` Vaneet Narang
2018-03-26 19:52 ` Andrew Morton [this message]
2018-03-27 11:40 ` Maninder Singh
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=20180326125228.1f40abb9a52f3674b1491aea@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.sahrawat@samsung.com \
--cc=aryabinin@virtuozzo.com \
--cc=ayush.m@samsung.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gomonovych@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maninder1.s@samsung.com \
--cc=mhocko@suse.com \
--cc=pankaj.m@samsung.com \
--cc=pombredanne@nexb.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=v.narang@samsung.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.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).