[OS-BUILD PATCHv3 0/0] [redhat] New configs in drivers/md
by CKI Gitlab (via Email Bridge)
From: CKI Gitlab on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/834
NOTE: Truncated patchset due to missing @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the merge request to
retrigger sending the emails.
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DM_MULTIPATH_IOA:
This path selector selects the path based on the CPU the IO is
executed on and the CPU to path mapping setup at path addition time.
If unsure, say N.
Symbol: DM_MULTIPATH_IOA [=n]
Type : tristate
Defined at drivers/md/Kconfig:466
Prompt: I/O Path Selector based on CPU submission
Depends on: MD [=y] && DM_MULTIPATH [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
-> Multipath target (DM_MULTIPATH [=m])
---
Cc: Nigel Croxon <ncroxon(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of redhat-patchlab
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_GUP_TEST:
Provides /sys/kernel/debug/gup_test, which in turn provides a way
to make ioctl calls that can launch kernel-based unit tests for
the get_user_pages*() and pin_user_pages*() family of API calls.
These tests include benchmark testing of the _fast variants of
get_user_pages*() and pin_user_pages*(), as well as smoke tests of
the non-_fast variants.
There is also a sub-test that allows running dump_page() on any
of up to eight pages (selected by command line args) within the
range of user-space addresses. These pages are either pinned via
pin_user_pages*(), or pinned via get_user_pages*(), as specified
by other command line arguments.
See tools/testing/selftests/vm/gup_test.c
Symbol: GUP_TEST [=n]
Type : bool
Defined at mm/Kconfig:824
Prompt: Enable infrastructure for get_user_pages()-related unit tests
Depends on: DEBUG_FS [=y]
Location:
-> Memory Management options
---
Cc: Rafael Aquini <aquini(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_GUP_TEST | 1 +
.../pending-common/generic/CONFIG_GUP_TEST | 29 -------------------
2 files changed, 1 insertion(+), 29 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_GUP_TEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GUP_TEST
diff --git a/redhat/configs/common/generic/CONFIG_GUP_TEST b/redhat/configs/common/generic/CONFIG_GUP_TEST
new file mode 100644
index 000000000000..5df4896bb447
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_GUP_TEST
@@ -0,0 +1 @@
+# CONFIG_GUP_TEST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST b/redhat/configs/pending-common/generic/CONFIG_GUP_TEST
deleted file mode 100644
index 11570ef11beb..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST
+++ /dev/null
@@ -1,29 +0,0 @@
-# CONFIG_GUP_TEST:
-#
-# Provides /sys/kernel/debug/gup_test, which in turn provides a way
-# to make ioctl calls that can launch kernel-based unit tests for
-# the get_user_pages*() and pin_user_pages*() family of API calls.
-#
-# These tests include benchmark testing of the _fast variants of
-# get_user_pages*() and pin_user_pages*(), as well as smoke tests of
-# the non-_fast variants.
-#
-# There is also a sub-test that allows running dump_page() on any
-# of up to eight pages (selected by command line args) within the
-# range of user-space addresses. These pages are either pinned via
-# pin_user_pages*(), or pinned via get_user_pages*(), as specified
-# by other command line arguments.
-#
-# See tools/testing/selftests/vm/gup_test.c
-#
-# Symbol: GUP_TEST [=n]
-# Type : bool
-# Defined at mm/Kconfig:824
-# Prompt: Enable infrastructure for get_user_pages()-related unit tests
-# Depends on: DEBUG_FS [=y]
-# Location:
-# -> Memory Management options
-#
-#
-#
-# CONFIG_GUP_TEST is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in drivers/input
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_INPUT_IQS269A:
Say Y to enable support for the Azoteq IQS269A capacitive
touch controller.
To compile this driver as a module, choose M here: the
module will be called iqs269a.
Symbol: INPUT_IQS269A [=n]
Type : tristate
Defined at drivers/input/misc/Kconfig:721
Prompt: Azoteq IQS269A capacitive touch controller
Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Miscellaneous devices (INPUT_MISC [=y])
Selects: REGMAP_I2C [=m]
---
CONFIG_TOUCHSCREEN_CY8CTMA140:
Say Y here if you have a Cypress CY8CTMA140 capacitive
touchscreen also just known as "TMA140"
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called cy8ctma140.
Symbol: TOUCHSCREEN_CY8CTMA140 [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:204
Prompt: cy8ctma140 touchscreen
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_INPUT_IQS269A | 1 +
.../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 1 +
.../generic/CONFIG_INPUT_IQS269A | 23 ------------------
.../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 24 -------------------
4 files changed, 2 insertions(+), 47 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_INPUT_IQS269A
create mode 100644 redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
diff --git a/redhat/configs/common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A
new file mode 100644
index 000000000000..8b78e198494a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A
@@ -0,0 +1 @@
+# CONFIG_INPUT_IQS269A is not set
diff --git a/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
new file mode 100644
index 000000000000..fa03c444e54b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
@@ -0,0 +1 @@
+# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
deleted file mode 100644
index 445a42fa0119..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_INPUT_IQS269A:
-#
-# Say Y to enable support for the Azoteq IQS269A capacitive
-# touch controller.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called iqs269a.
-#
-# Symbol: INPUT_IQS269A [=n]
-# Type : tristate
-# Defined at drivers/input/misc/Kconfig:721
-# Prompt: Azoteq IQS269A capacitive touch controller
-# Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Input device support
-# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-# -> Miscellaneous devices (INPUT_MISC [=y])
-# Selects: REGMAP_I2C [=m]
-#
-#
-#
-# CONFIG_INPUT_IQS269A is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
deleted file mode 100644
index bb0283fcabba..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_TOUCHSCREEN_CY8CTMA140:
-#
-# Say Y here if you have a Cypress CY8CTMA140 capacitive
-# touchscreen also just known as "TMA140"
-#
-# If unsure, say N.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called cy8ctma140.
-#
-# Symbol: TOUCHSCREEN_CY8CTMA140 [=n]
-# Type : tristate
-# Defined at drivers/input/touchscreen/Kconfig:204
-# Prompt: cy8ctma140 touchscreen
-# Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Input device support
-# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-# -> Touchscreens (INPUT_TOUCHSCREEN [=y])
-#
-#
-#
-# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
--
2.27.0
3 years, 1 month
[OS-BUILD PATCH] [redhat] Unify crypto CHACHA20 and POLY1305 configs
by Vladis Dronov (via Email Bridge)
From: Vladis Dronov <vdronov(a)redhat.com>
[redhat] Unify crypto CHACHA20 and POLY1305 configs
Currently CRYPTO_CHACHA20* and CRYPTO_*POLY1305* configs are not in order.
Unify them by merging and moving to configs/common/. Also enable CRYPTO_
CHACHA20POLY1305 on PowerPC as it was done in rhbz#1734711.
Detailed actions taken:
Move:
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
to
configs/common/generic/s390x/zfcpdump/
Delete (per rhbz#1734711):
configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305:# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
Delete: configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON:# CONFIG_CRYPTO_POLY1305_NEON is not set
And move:
configs/fedora/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
to:
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
to:
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2
Merge:
configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
to (depends on X86 && 64BIT):
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2
The result:
$ git grep -e CRYPTO_CHACHA20 -e CRYPTO_POLY1305 -e CRYPTO_NHPOLY1305
configs/common/generic/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=m
configs/common/generic/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=m
configs/common/generic/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=m
configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON:CONFIG_CRYPTO_CHACHA20_NEON=m
configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON:CONFIG_CRYPTO_NHPOLY1305_NEON=m
configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON:CONFIG_CRYPTO_POLY1305_NEON=m
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20:CONFIG_CRYPTO_CHACHA20=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305:CONFIG_CRYPTO_CHACHA20POLY1305=y
configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305:CONFIG_CRYPTO_POLY1305=y
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_CHACHA20_X86_64:CONFIG_CRYPTO_CHACHA20_X86_64=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2:CONFIG_CRYPTO_NHPOLY1305_AVX2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2:CONFIG_CRYPTO_NHPOLY1305_SSE2=m
configs/common/generic/x86/x86_64/CONFIG_CRYPTO_POLY1305_X86_64:CONFIG_CRYPTO_POLY1305_X86_64=m
configs/fedora/generic/arm/armv7/CONFIG_CRYPTO_POLY1305_ARM:CONFIG_CRYPTO_POLY1305_ARM=m
Signed-off-by: Vladis Dronov <vdronov(a)redhat.com>
diff a/redhat/configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305 b/redhat/configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305
--- a/redhat/configs/ark/generic/powerpc/CONFIG_CRYPTO_CHACHA20POLY1305
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_CHACHA20_NEON b/redhat/configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_CHACHA20_NEON
+++ b/redhat/configs/common/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_NEON b/redhat/configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_NEON
+++ b/redhat/configs/common/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
diff a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON b/redhat/configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON
--- a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON
+++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_CRYPTO_POLY1305_NEON
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20 b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
--- a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
+++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305 b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
--- a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
+++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_CHACHA20POLY1305
diff a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305 b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
--- a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
+++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_CRYPTO_POLY1305
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_AVX2 b/redhat/configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_AVX2
+++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_AVX2
diff a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_SSE2 b/redhat/configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2
--- a/redhat/configs/ark/generic/CONFIG_CRYPTO_NHPOLY1305_SSE2
+++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_CRYPTO_NHPOLY1305_SSE2
diff a/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON b/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
--- a/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_CHACHA20_NEON
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_CHACHA20_NEON=m
diff a/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON b/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
--- a/redhat/configs/fedora/generic/arm/CONFIG_CRYPTO_NHPOLY1305_NEON
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_NHPOLY1305_NEON=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2 b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_AVX2
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_NHPOLY1305_AVX2=m
diff a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2 b/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2
--- a/redhat/configs/fedora/generic/x86/CONFIG_CRYPTO_NHPOLY1305_SSE2
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_CRYPTO_NHPOLY1305_SSE2=m
diff a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON b/redhat/configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON
--- a/redhat/configs/pending-common/generic/CONFIG_CRYPTO_POLY1305_NEON
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_CRYPTO_POLY1305_NEON is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/951
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_ZSMALLOC_PGTABLE_MAPPING:
By default, zsmalloc uses a copy-based object mapping method to
access allocations that span two pages. However, if a particular
architecture (ex, ARM) performs VM mapping faster than copying,
then you should select this. This causes zsmalloc to use page table
mapping rather than copying for object mapping.
You can check speed with zsmalloc benchmark:
https://github.com/spartacus06/zsmapbench
Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
Type : bool
Defined at mm/Kconfig:708
Prompt: Use page table mapping to access object in zsmalloc
Depends on: ZSMALLOC [=y]=y
Location:
-> Memory Management options
-> Memory allocator for compressed pages (ZSMALLOC [=y])
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 1 +
.../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
diff --git a/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
new file mode 100644
index 000000000000..502c3e374887
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
@@ -0,0 +1 @@
+# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
deleted file mode 100644
index 2f3d89cf6004..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_ZSMALLOC_PGTABLE_MAPPING:
-#
-# By default, zsmalloc uses a copy-based object mapping method to
-# access allocations that span two pages. However, if a particular
-# architecture (ex, ARM) performs VM mapping faster than copying,
-# then you should select this. This causes zsmalloc to use page table
-# mapping rather than copying for object mapping.
-#
-# You can check speed with zsmalloc benchmark:
-# https://github.com/spartacus06/zsmapbench
-#
-# Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
-# Type : bool
-# Defined at mm/Kconfig:708
-# Prompt: Use page table mapping to access object in zsmalloc
-# Depends on: ZSMALLOC [=y]=y
-# Location:
-# -> Memory Management options
-# -> Memory allocator for compressed pages (ZSMALLOC [=y])
-#
-#
-#
-# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set
--
2.26.2
3 years, 1 month
[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_PMU_SYSFS:
This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.
Symbol: PMU_SYSFS [=n]
Type : bool
Defined at arch/powerpc/platforms/Kconfig.cputype:428
Prompt: Create PMU SPRs sysfs file
Location:
-> Processor support
Cc: kernel-patches(a)redhat.com
---
redhat/configs/common/generic/CONFIG_PMU_SYSFS | 1 +
.../pending-common/generic/CONFIG_PMU_SYSFS | 14 --------------
2 files changed, 1 insertion(+), 14 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PMU_SYSFS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
diff --git a/redhat/configs/common/generic/CONFIG_PMU_SYSFS b/redhat/configs/common/generic/CONFIG_PMU_SYSFS
new file mode 100644
index 000000000000..d192b509fed0
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PMU_SYSFS
@@ -0,0 +1 @@
+# CONFIG_PMU_SYSFS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS b/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
deleted file mode 100644
index 1f1a0f6cec8a..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
+++ /dev/null
@@ -1,14 +0,0 @@
-# CONFIG_PMU_SYSFS:
-#
-# This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.
-#
-# Symbol: PMU_SYSFS [=n]
-# Type : bool
-# Defined at arch/powerpc/platforms/Kconfig.cputype:428
-# Prompt: Create PMU SPRs sysfs file
-# Location:
-# -> Processor support
-#
-#
-#
-# CONFIG_PMU_SYSFS is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_COMPAT:
Enable support for 32bit binaries
Symbol: COMPAT [=n]
Type : bool
Defined at arch/powerpc/Kconfig:268
Depends on: PPC64
Default: y if !CPU_LITTLE_ENDIAN
Selects: COMPAT_BINFMT_ELF
ARCH_WANT_OLD_COMPAT_IPC
COMPAT_OLD_SIGACTION
Cc: kernel-patches(a)redhat.com
---
redhat/configs/common/generic/powerpc/CONFIG_COMPAT | 1 +
.../pending-common/generic/powerpc/CONFIG_COMPAT | 12 ------------
2 files changed, 1 insertion(+), 12 deletions(-)
create mode 100644 redhat/configs/common/generic/powerpc/CONFIG_COMPAT
delete mode 100644 redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
diff --git a/redhat/configs/common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT
new file mode 100644
index 000000000000..3e041f1b653b
--- /dev/null
+++ b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT
@@ -0,0 +1 @@
+# CONFIG_COMPAT is not set
diff --git a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
deleted file mode 100644
index f59088da33db..000000000000
--- a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
+++ /dev/null
@@ -1,12 +0,0 @@
-# CONFIG_COMPAT:
-#
-# Enable support for 32bit binaries
-#
-# Symbol: COMPAT [=n]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:268
-# Depends on: PPC64
-# Default: y if !CPU_LITTLE_ENDIAN
-# Selects: COMPAT_BINFMT_ELF, ARCH_WANT_OLD_COMPAT_IPC, COMPAT_OLD_SIGACTION
-#
-# CONFIG_COMPAT is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in fs/xfs
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_XFS_SUPPORT_V4:
The V4 filesystem format lacks certain features that are supported
by the V5 format, such as metadata checksumming, strengthened
metadata verification, and the ability to store timestamps past the
year 2038. Because of this, the V4 format is deprecated. All users
should upgrade by backing up their files, reformatting, and restoring
from the backup.
Administrators and users can detect a V4 filesystem by running
xfs_info against a filesystem mountpoint and checking for a string
beginning with "crc=". If the string "crc=0" is found, the
filesystem is a V4 filesystem. If no such string is found, please
upgrade xfsprogs to the latest version and try again.
This option will become default N in September 2025. Support for the
V4 format will be removed entirely in September 2030. Distributors
can say N here to withdraw support earlier.
To continue supporting the old V4 format (crc=0), say Y.
To close off an attack surface, say N.
Symbol: XFS_SUPPORT_V4 [=y]
Type : bool
Defined at fs/xfs/Kconfig:25
Prompt: Support deprecated V4 (crc=0) format
Depends on: BLOCK [=y] && XFS_FS [=m]
Location:
-> File systems
-> XFS filesystem support (XFS_FS [=m])
---
Cc: Brian Foster <bfoster(a)redhat.com>
Cc: Carlos Maiolino <cmaiolin(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_XFS_SUPPORT_V4 | 1 +
.../generic/CONFIG_XFS_SUPPORT_V4 | 34 -------------------
2 files changed, 1 insertion(+), 34 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4
diff --git a/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4 b/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4
new file mode 100644
index 000000000000..12315e1fff2b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_XFS_SUPPORT_V4
@@ -0,0 +1 @@
+CONFIG_XFS_SUPPORT_V4=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4 b/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4
deleted file mode 100644
index aeb9b39ac5da..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_XFS_SUPPORT_V4
+++ /dev/null
@@ -1,34 +0,0 @@
-# CONFIG_XFS_SUPPORT_V4:
-#
-# The V4 filesystem format lacks certain features that are supported
-# by the V5 format, such as metadata checksumming, strengthened
-# metadata verification, and the ability to store timestamps past the
-# year 2038. Because of this, the V4 format is deprecated. All users
-# should upgrade by backing up their files, reformatting, and restoring
-# from the backup.
-#
-# Administrators and users can detect a V4 filesystem by running
-# xfs_info against a filesystem mountpoint and checking for a string
-# beginning with "crc=". If the string "crc=0" is found, the
-# filesystem is a V4 filesystem. If no such string is found, please
-# upgrade xfsprogs to the latest version and try again.
-#
-# This option will become default N in September 2025. Support for the
-# V4 format will be removed entirely in September 2030. Distributors
-# can say N here to withdraw support earlier.
-#
-# To continue supporting the old V4 format (crc=0), say Y.
-# To close off an attack surface, say N.
-#
-# Symbol: XFS_SUPPORT_V4 [=y]
-# Type : bool
-# Defined at fs/xfs/Kconfig:25
-# Prompt: Support deprecated V4 (crc=0) format
-# Depends on: BLOCK [=y] && XFS_FS [=m]
-# Location:
-# -> File systems
-# -> XFS filesystem support (XFS_FS [=m])
-#
-#
-#
-CONFIG_XFS_SUPPORT_V4=y
--
GitLab
3 years, 1 month
[OS-BUILD PATCHv4] redhat: add initial support for centos stream
dist-git sync
on Makefiles
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
redhat: add initial support for centos stream dist-git sync on Makefiles
This change introduces some initial centos stream support, mainly what's
needed for a dist-git sync. The dist-git sync is initially proposed to
be a fork + merge request model, and thus we need some changes for the
Makefiles. I also dropped IS_FEDORA variable, and replace it with
DISTRO, which can have either "fedora" or "centos" (and could be set
later to "rhel" or anything else if needed through the code).
While at it, I also fixed the default RHPKG_BIN to rhpkg instead of
rhpkg-sha512 in the default RHEL case, the former was a wrapper for
the sha512 transition on dist-git at RHEL 8 time and is not needed
anymore, it is now deprecated and will be removed from rhpkg.
Example of a dist-git sync with new centos dist-git:
make DIST=".el9" GL_DISTGIT_USER=<gitlab user> BUILDID="" RHDISTGIT_BRANCH=c9s dist-git
v2: use PACKAGE_NAME in Makefile.rhpkg as suggested by Jan Stancek
v3: make the default DISTRO rhel in case DIST is not fc*, to not break
folks building kernel-ark on rhel which are used to not have to
specify an extra variable, as reported by Don Zickus
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/redhat/Makefile b/redhat/Makefile
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -404,6 +404,12 @@ dist-git: dist-srpm $(KABI_TARBALL) $(KABIDW_TARBALL)
ifeq ("$(RHDISTGIT_BRANCH)", "")
$(error RHDISTGIT_BRANCH unset)
endif
+ if [ "$(DISTRO)" == "centos" ]; then \
+ if [ -z "$(GL_DISTGIT_USER)" ]; then \
+ echo "Error: please Please provide your gitlab username with GL_DISTGIT_USER"; \
+ exit 1; \
+ fi; \
+ fi
$(REDHAT)/scripts/rh-dist-git.sh "$(RHDISTGIT_BRANCH)" "$(RHDISTGIT_CACHE)" "$(RHDISTGIT_TMP)" "$(RHDISTGIT)" "$(TARBALL)" "$(KABI_TARBALL)" "$(KABIDW_TARBALL)" "$(__ZSTREAM)" "$(PACKAGE_NAME)" "$(RHEL_MAJOR)" "$(RHPKG_BIN)" "$(SRPMS)/$(PACKAGE_NAME)-$(KVERSION)-$(PKGRELEASE)$(DIST).src.rpm"
dist-rtg: dist-release
diff a/redhat/Makefile.common b/redhat/Makefile.common
--- a/redhat/Makefile.common
+++ b/redhat/Makefile.common
@@ -29,14 +29,19 @@ else
PREBUILD:=
endif
-DIST ?=.fc33
-IS_FEDORA:=$(shell ! echo $(DIST) | grep -q fc; echo $$?)
+DIST ?= .fc33
+ifeq ("$(shell ! echo $(DIST) | grep -q fc; echo $$?)", "1")
+ DISTRO := fedora
+else
+ DISTRO ?= rhel
+endif
+
# If VERSION_ON_UPSTREAM is set, the versioning of the rpm package is based
# on a branch tracking upstream. This allows for generating rpms
# based on untagged releases.
ifeq ("$(DIST)", ".elrdy")
VERSION_ON_UPSTREAM:=1
-else ifeq ("$(IS_FEDORA)", "1")
+else ifeq ("$(DISTRO)", "fedora")
VERSION_ON_UPSTREAM:=1
else
VERSION_ON_UPSTREAM:=0
@@ -90,7 +95,7 @@ ARCH_LIST=aarch64 ppc64le s390x x86_64
# a diff in the spec file
ifeq ("$(DIST)", ".elrdy")
SINGLE_TARBALL:=0
-else ifeq ("$(IS_FEDORA)", "1")
+else ifeq ("$(DISTRO)", "fedora")
SINGLE_TARBALL:=0
else
SINGLE_TARBALL:=1
@@ -139,16 +144,20 @@ CHANGELOG_PREV:=$(PACKAGE_NAME).changelog-$(RHEL_MAJOR).$(shell expr $(RHEL_MINO
ifeq ("$(DIST)", ".elrdy")
RHPRODUCT:=rhel-ready
-else ifeq ("$(IS_FEDORA)", "1")
+else ifeq ("$(DISTRO)", "fedora")
RHPRODUCT:=rawhide
+else ifeq ("$(DISTRO)", "centos")
+ RHPRODUCT:=c$(RHEL_MAJOR)s
else
RHPRODUCT:=rhel-$(RHEL_MAJOR).$(RHEL_MINOR).0
endif
ifeq ("$(DIST)", ".elrdy")
BUILD_SCRATCH_TARGET ?= temp-ark-rhel-8-test
-else ifeq ("$(IS_FEDORA)", "1")
+else ifeq ("$(DISTRO)", "fedora")
BUILD_SCRATCH_TARGET ?= temp-ark-rhel-8-test
+else ifeq ("$(DISTRO)", "centos")
+ BUILD_SCRATCH_TARGET ?= c$(RHEL_MAJOR)s-candidate
else
BUILD_SCRATCH_TARGET ?= rhel-$(RHEL_MAJOR).$(RHEL_MINOR).0-test-pesign
endif
diff a/redhat/Makefile.rhpkg b/redhat/Makefile.rhpkg
--- a/redhat/Makefile.rhpkg
+++ b/redhat/Makefile.rhpkg
@@ -2,10 +2,12 @@
#
# Command to invoke rhpkg
-ifeq ("$(IS_FEDORA)", "1")
+ifeq ("$(DISTRO)", "fedora")
RHPKG_BIN:=fedpkg
+else ifeq ("$(DISTRO)", "centos")
+ RHPKG_BIN:=centpkg
else
- RHPKG_BIN:=rhpkg-sha512
+ RHPKG_BIN:=rhpkg
endif
# Kerberos username for pkgs.devel.redhat.com
RHDISTGIT_USER:="$(shell whoami)"
@@ -27,4 +29,13 @@ ifeq ("$(RHDISTGIT_CACHE)", "")
endif
endif
-RHDISTGIT:="ssh://$(RHDISTGIT_USER)@pkgs.devel.redhat.com/rpms/$(PACKAGE_NAME)"
+ifneq ("$(DISTRO)", "centos")
+ RHDISTGIT:="ssh://$(RHDISTGIT_USER)@pkgs.devel.redhat.com/rpms/$(PACKAGE_NAME)"
+else
+ # CentOS uses a fork + merge request based workflow with dist-git to
+ # handle changes, so you need to provide the gitlab username and we by
+ # default set the default user's fork path. The dist-git target in
+ # redhat/Makefile has a check to see if the variable is not set.
+ GL_FORK_PATH?=$(PACKAGE_NAME).git
+ RHDISTGIT:=git@gitlab.com:$(GL_DISTGIT_USER)/$(GL_FORK_PATH)
+endif
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/977
3 years, 1 month