From: Justin M. Forbes jforbes@fedoraproject.org

Remove CONFIG_ARCH_FORCE_MAX_ORDER for aarch64

Upstream commit f3c3762178fad5cf5dc108fb061ba010818323b4 took away the prompt so this is no longer configurable. The default is 10. While this is different from what we have been running, it was determined that the older ThunderX platform was the only reason that this value should be higher.

Signed-off-by: Justin M. Forbes jforbes@fedoraproject.org

diff --git a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER +++ /dev/null @@ -1 +0,0 @@ -CONFIG_ARCH_FORCE_MAX_ORDER=13 diff --git a/redhat/configs/pending-fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER b/redhat/configs/pending-fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/pending-fedora/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER +++ /dev/null @@ -1 +0,0 @@ -CONFIG_ARCH_FORCE_MAX_ORDER=10 diff --git a/redhat/configs/pending-rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER b/redhat/configs/pending-rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/pending-rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER +++ /dev/null @@ -1 +0,0 @@ -CONFIG_ARCH_FORCE_MAX_ORDER=10 diff --git a/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER b/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/rhel/generic/arm/aarch64/CONFIG_ARCH_FORCE_MAX_ORDER +++ /dev/null @@ -1 +0,0 @@ -CONFIG_ARCH_FORCE_MAX_ORDER=13

-- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2508