From: Catalin Marinas <catalin.marinas@arm.com>
To: Anand Moon <linux.amoon@gmail.com>
Cc: Will Deacon <will@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: defconfig: Enable CONFIG_EXPERT
Date: Thu, 26 Sep 2024 18:04:10 +0100 [thread overview]
Message-ID: <ZvWUCtkOXKfnIr-m@arm.com> (raw)
In-Reply-To: <20240926145817.1124-1-linux.amoon@gmail.com>
On Thu, Sep 26, 2024 at 08:28:16PM +0530, Anand Moon wrote:
> Enable CONFIG_EXPERT to allow the configuration of PREEMPT_RT.
>
> PREEMPT_RT depends on the following configuration:
>
> CONFIG_PREEMPT_RT
> bool “Fully Preemptible Kernel (Real-Time)”
> depends on CONFIG_EXPERT && ARCH_SUPPORTS_RT
> select PREEMPTION
>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Signed-off-by: Anand Moon <linux.amoon@gmail.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 5fdbfea7a5b2..3d9d29eb0c13 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -28,6 +28,7 @@ CONFIG_CGROUP_BPF=y
> CONFIG_USER_NS=y
> CONFIG_SCHED_AUTOGROUP=y
> CONFIG_BLK_DEV_INITRD=y
> +CONFIG_EXPERT=y
> CONFIG_KALLSYMS_ALL=y
> CONFIG_PROFILING=y
> CONFIG_KEXEC=y
EXPERT is not really for defconfig (at least not for the arm64 one).
Distros can (and do) enable it if they want. Also PREEMPT_RT is default
off, so you'd have to enable it in your config anyway, not sure what
this patch helps with.
--
Catalin
next prev parent reply other threads:[~2024-09-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 14:58 [PATCH v1] arm64: defconfig: Enable CONFIG_EXPERT Anand Moon
2024-09-26 17:04 ` Catalin Marinas [this message]
2024-09-27 3:40 ` Anand Moon
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=ZvWUCtkOXKfnIr-m@arm.com \
--to=catalin.marinas@arm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=will@kernel.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 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.