From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Christoph Lameter <cl@gentwo.de>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Ingo Molnar <mingo@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <muchun.song@linux.dev>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Mel Gorman <mgorman@techsingularity.net>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH mm-unstable] lib/Kconfig.debug: do not enable DEBUG_PREEMPT by default
Date: Wed, 25 Jan 2023 01:34:23 +0900 [thread overview]
Message-ID: <Y9AIj5OLmPAH8cXF@hyeyoo> (raw)
In-Reply-To: <d23a77b8-e9dd-9fc3-4311-4597e310e7a8@gentwo.de>
On Mon, Jan 23, 2023 at 12:05:00PM +0100, Christoph Lameter wrote:
> On Sat, 21 Jan 2023, Hyeonggon Yoo wrote:
>
> > Whew, I still get confused about who to Cc, thanks for adding them.
> > and I also didn't include the percpu memory allocator maintainers, who may
> > have opinion. let's add them too.
>
> Well looks ok to me.
Thanks for looking at!
> However, I thought most distro kernels disable PREEMPT anyways for
> performance reasons? So DEBUG_PREEMPT should be off as well. I guess that
> is why this has not been an issue so far.
It depends on PREEMPTION, and PREEMPT_DYNAMIC ("Preemption behaviour defined on boot")
selects PREEMPTION even if I end up using PREEMPT_VOLUNTARY.
Not so many distros use DEBUG_PREEMPT, but I am occationally hit by this
because debian and fedora enabled it :)
next prev parent reply other threads:[~2023-01-24 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 3:39 Hyeonggon Yoo
2023-01-21 11:29 ` Vlastimil Babka
2023-01-21 11:54 ` Hyeonggon Yoo
2023-01-23 8:58 ` Michal Hocko
2023-01-25 15:41 ` Hyeonggon Yoo
2023-01-25 9:51 ` Michal Hocko
2023-01-27 11:43 ` Hyeonggon Yoo
2023-01-27 12:33 ` Michal Hocko
2023-01-23 11:05 ` Christoph Lameter
2023-01-24 16:34 ` Hyeonggon Yoo [this message]
2023-01-23 14:01 ` Mel Gorman
2023-01-26 2:02 ` Roman Gushchin
2023-01-27 11:45 ` Hyeonggon Yoo
2023-02-02 3:09 ` 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=Y9AIj5OLmPAH8cXF@hyeyoo \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=cl@gentwo.de \
--cc=dennis@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=muchun.song@linux.dev \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=willy@infradead.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