From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbecker@suse.de>,
LKML <linux-kernel@vger.kernel.org>, Mel Gorman <mgorman@suse.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC PATCH] kernel: allow to configure PREEMPT_NONE, PREEMPT_VOLUNTARY on kernel command line
Date: Fri, 9 Oct 2020 11:42:45 +0200 [thread overview]
Message-ID: <20201009094245.GG2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201009091218.GF4967@dhcp22.suse.cz>
On Fri, Oct 09, 2020 at 11:12:18AM +0200, Michal Hocko wrote:
> Is there any additional feedback? Should I split up the patch and repost
> for inclusion?
Maybe remove PREEMPT_NONE after that? Since that's then equivalent to
building with VOLUNTARY and booting with preempt=none.
next prev parent reply other threads:[~2020-10-09 9:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 12:04 [RFC PATCH] kernel: allow to configure PREEMPT_NONE, PREEMPT_VOLUNTARY on kernel command line Michal Hocko
2020-10-07 12:19 ` Peter Zijlstra
2020-10-07 12:29 ` Michal Hocko
2020-10-07 13:01 ` Mel Gorman
2020-10-07 12:21 ` Peter Zijlstra
2020-10-07 12:35 ` Michal Hocko
2020-10-09 9:47 ` Peter Zijlstra
2020-10-09 10:14 ` Michal Hocko
2020-10-09 10:20 ` Peter Zijlstra
2020-10-09 10:48 ` Michal Hocko
2020-10-09 11:17 ` Michal Hocko
2020-10-09 11:26 ` Michal Hocko
2020-10-09 11:39 ` Peter Zijlstra
2020-10-07 15:41 ` kernel test robot
2020-10-07 15:53 ` Michal Hocko
2020-10-09 9:12 ` Michal Hocko
2020-10-09 9:42 ` Peter Zijlstra [this message]
2020-10-09 10:10 ` Michal Hocko
2020-10-09 10:14 ` Peter Zijlstra
2020-10-09 10:37 ` Michal Hocko
2020-10-09 11:42 ` Peter Zijlstra
2020-10-09 12:29 ` [RFC PATCH v2 0/5] allow overriding default preempt mode from " Michal Hocko
2020-10-09 12:29 ` [RFC PATCH v2 1/5] jump_label: split out declaration parts into its own headers Michal Hocko
2020-10-09 12:29 ` [RFC PATCH v2 2/5] kernel: allow to configure PREEMPT_NONE, PREEMPT_VOLUNTARY on kernel command line Michal Hocko
2020-10-15 16:32 ` kernel test robot
2020-10-09 12:29 ` [RFC PATCH v2 3/5] kernel: ARCH_NO_PREEMPT shouldn't exclude PREEMPT_VOLUNTARY Michal Hocko
2020-10-09 12:29 ` [RFC PATCH v2 4/5] kernel: introduce CONFIG_PREEMPT_DYNAMIC Michal Hocko
2020-10-09 12:29 ` [RFC PATCH v2 5/5] kernel: drop PREEMPT_NONE compile time option Michal Hocko
2020-10-09 12:50 ` [RFC PATCH v2 0/5] allow overriding default preempt mode from command line Peter Zijlstra
2020-10-09 13:03 ` Michal Hocko
2020-10-09 13:22 ` Peter Zijlstra
2020-10-09 17:45 ` Peter Zijlstra
2020-10-27 12:22 ` Frederic Weisbecker
2020-10-27 12:28 ` Peter Zijlstra
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=20201009094245.GG2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweisbecker@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--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 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.