linux-kernel - Re: [PATCH] ARM64: Enable multi-core scheduler support by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 Oct 2015 14:01:21 +0000
From:	Punit Agrawal <punit.agrawal@....com>
To:	Will Deacon <will.deacon@....com>,
	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	dietmar.eggemann@....com
Subject: Re: [PATCH] ARM64: Enable multi-core scheduler support by default

Hi Catalin, Will,

Dietmar Eggemann <dietmar.eggemann@....com> writes:

> Make sure that the task scheduler domain hierarchy is set-up correctly
> on systems with single or multi-cluster topology.
>
> Signed-off-by: Dietmar Eggemann <dietmar.eggemann@....com>

FWIW,
        Acked-by: Punit Agrawal <punit.agrawal@....com>

I am not sure how we update the defconfig. Can you pick this up for 4.4?
Or will this be picked up after the merge window?

Thanks,
Punit

> ---
>  arch/arm64/configs/defconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 34d71dd86781..dc70d715bc38 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -51,6 +51,7 @@ CONFIG_PCI=y
>  CONFIG_PCI_MSI=y
>  CONFIG_PCI_XGENE=y
>  CONFIG_SMP=y
> +CONFIG_SCHED_MC=y
>  CONFIG_PREEMPT=y
>  CONFIG_KSM=y
>  CONFIG_TRANSPARENT_HUGEPAGE=y
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/