Skip to contentSkip to conversation

ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build

PATCH In review Mike Rapoport 3 participants 15 messages May 21, 2020 – Jun 2, 2020 Arm (32-bit)

lore
Share & tools
lore
#0 lore raw

cover ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

For example, below is the diffs of the configurations generated with 'make rpc_defconfig' and 'make defconfig':

$ diff -s old/rpc_defconfig new/rpc_defconfig
Files old/rpc_defconfig and new/rpc_defconfig are identical
$ diff -u old/defconfig new/defconfig
--- old/defconfig	2020-05-20 17:51:01.832649705 +0300
+++ new/defconfig	2020-05-20 18:15:21.084385880 +0300
@@ -674,6 +674,9 @@
 CONFIG_AEABI=y
 # CONFIG_OABI_COMPAT is not set
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_HAVE_ARCH_PFN_VALID=y
 CONFIG_HIGHMEM=y
 CONFIG_HIGHPTE=y
@@ -1061,6 +1064,9 @@
 #
 # Memory Management options
 #
+CONFIG_SELECT_MEMORY_MODEL=y
+CONFIG_FLATMEM_MANUAL=y
+# CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_ARCH_KEEP_MEMBLOCK=y

[1] https://lore.kernel.org/linux-arm-kernel/[email protected]

Gregory Fong (1):
ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build

Kevin Cernekee (1):
ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting

 arch/arm/Kconfig | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)
Signature · 7 lines
2.26.2


_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#1 lore raw

PATCH 1/2 ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting

From: Kevin Cernekee <[email protected]>

If ARCH_SPARSEMEM_ENABLE=y and ARCH_{FLATMEM,DISCONTIGMEM}_ENABLE=n, then the logic in mm/Kconfig already makes CONFIG_SPARSEMEM the only choice. This is true for all of the existing ARM users of ARCH_SPARSEMEM_ENABLE.

Forcing ARCH_SPARSEMEM_DEFAULT=y if ARCH_SPARSEMEM_ENABLE=y prevents us from ever defaulting to FLATMEM, so we should remove this setting.

---
 arch/arm/Kconfig | 3 ---
 1 file changed, 3 deletions(-)
arch/arm/Kconfig +0 -3
index c88a48d622fc..604caf652e2a 100644
@@ -1519,9 +1519,6 @@ config ARCH_SPARSEMEM_ENABLE
 	bool
 	select SPARSEMEM_STATIC
 
-config ARCH_SPARSEMEM_DEFAULT
-	def_bool ARCH_SPARSEMEM_ENABLE
-
 config HAVE_ARCH_PFN_VALID
 	def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
 
Signature · 7 lines
2.26.2


_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#2 lore raw

PATCH 2/2 ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build

In reply to Mike Rapoport

From: Gregory Fong <[email protected]>

ARMv7 chips with LPAE can often benefit from SPARSEMEM, as portions of system memory can be located deep in the 36-bit address space. Allow FLATMEM or SPARSEMEM to be selectable at compile time; FLATMEM remains the default.

This is based on Kevin's "[PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multi-v7 build" from [1] and shamelessly rips off his commit message text above. As Arnd pointed out at [2] there doesn't seem to be any reason to tie this specifically to ARMv7, so this has been changed to apply to all multiplatform kernels.

The addition of this option does not change the defaults and a build with any defconfig will behave the same way as previously.

The only effect this change has is to enable user to change "Memory model" selection in interactive kernel configuration (menuconfig, xconfig etc).

[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286837.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/298950.html

[ rppt: added ARCH_SELECT_MEMORY_MODEL and update the changelog ]

---
 arch/arm/Kconfig | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)
arch/arm/Kconfig +10 -1
index 604caf652e2a..34b93e0903df 100644
@@ -312,6 +312,9 @@ choice
 config ARCH_MULTIPLATFORM
 	bool "Allow multiple platforms to be selected"
 	depends on MMU
+	select ARCH_FLATMEM_ENABLE
+	select ARCH_SPARSEMEM_ENABLE
+	select ARCH_SELECT_MEMORY_MODEL
 	select ARM_HAS_SG_CHAIN
 	select ARM_PATCH_PHYS_VIRT
 	select AUTO_ZRELADDR
@@ -1515,9 +1518,15 @@ config OABI_COMPAT
 config ARCH_HAS_HOLES_MEMORYMODEL
 	bool
 
+config ARCH_SELECT_MEMORY_MODEL
+	bool
+
+config ARCH_FLATMEM_ENABLE
+	bool
+
 config ARCH_SPARSEMEM_ENABLE
 	bool
-	select SPARSEMEM_STATIC
+	select SPARSEMEM_STATIC if SPARSEMEM
 
 config HAVE_ARCH_PFN_VALID
 	def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
Signature · 7 lines
2.26.2


_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#3 lore raw
In reply to Mike Rapoport
Quoted 40 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

For example, below is the diffs of the configurations generated with 'make rpc_defconfig' and 'make defconfig':

$ diff -s old/rpc_defconfig new/rpc_defconfig
Files old/rpc_defconfig and new/rpc_defconfig are identical
$ diff -u old/defconfig new/defconfig
defconfig +3 -0
@@ -674,6 +674,9 @@
 CONFIG_AEABI=y
 # CONFIG_OABI_COMPAT is not set
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_HAVE_ARCH_PFN_VALID=y
 CONFIG_HIGHMEM=y
 CONFIG_HIGHPTE=y

defconfig line 1072

Quoted 9 lines
defconfig +3 -0
@@ -1061,6 +1064,9 @@
 #
 # Memory Management options
 #
+CONFIG_SELECT_MEMORY_MODEL=y
+CONFIG_FLATMEM_MANUAL=y
+# CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_ARCH_KEEP_MEMBLOCK=y

Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make.

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#4 lore raw
Quoted 46 lines · Russell King - ARM Linux admin
Quoted 45 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

For example, below is the diffs of the configurations generated with 'make rpc_defconfig' and 'make defconfig':

$ diff -s old/rpc_defconfig new/rpc_defconfig
Files old/rpc_defconfig and new/rpc_defconfig are identical
$ diff -u old/defconfig new/defconfig
defconfig +5 -0
@@ -674,6 +674,9 @@
 CONFIG_AEABI=y
 # CONFIG_OABI_COMPAT is not set
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_HAVE_ARCH_PFN_VALID=y
 CONFIG_HIGHMEM=y
 CONFIG_HIGHPTE=y
@@ -1061,6 +1064,9 @@
 #
 # Memory Management options
 #
+CONFIG_SELECT_MEMORY_MODEL=y
+CONFIG_FLATMEM_MANUAL=y
Quoted 8 lines

defconfig line 1072

Quoted 4 lines
defconfig +1 -0
+# CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_ARCH_KEEP_MEMBLOCK=y

Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make.

With ARCH_RPC=y (or ARCH_SA1100 or ARCH_EP93XX for that matter) ARCH_MULTIPLATFORM=n which prevents ARCH_SELECT_MEMORY_MODEL from being enabled and since any of these machines explicitly selects ARCH_SPARSEMEM_ENABLE, the only available memory model would be SPARSEMEM.

I played a bit with menuconfig and if any of the platforms requiring sparsemem is selected, the menu allowing the user to choose the memory model disappears.

Quoted 3 lines
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up
Signature · 7 lines
Sincerely yours,
Mike.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#5 lore raw
Quoted 62 lines · Mike Rapoport
Quoted 46 lines · Russell King - ARM Linux admin
Quoted 45 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

For example, below is the diffs of the configurations generated with 'make rpc_defconfig' and 'make defconfig':

$ diff -s old/rpc_defconfig new/rpc_defconfig
Files old/rpc_defconfig and new/rpc_defconfig are identical
$ diff -u old/defconfig new/defconfig
defconfig +5 -0
@@ -674,6 +674,9 @@
 CONFIG_AEABI=y
 # CONFIG_OABI_COMPAT is not set
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_HAVE_ARCH_PFN_VALID=y
 CONFIG_HIGHMEM=y
 CONFIG_HIGHPTE=y
@@ -1061,6 +1064,9 @@
 #
 # Memory Management options
 #
+CONFIG_SELECT_MEMORY_MODEL=y
+CONFIG_FLATMEM_MANUAL=y
Quoted 8 lines

defconfig line 1072

Quoted 4 lines
defconfig +1 -0
+# CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_ARCH_KEEP_MEMBLOCK=y

Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make.

With ARCH_RPC=y (or ARCH_SA1100 or ARCH_EP93XX for that matter) ARCH_MULTIPLATFORM=n which prevents ARCH_SELECT_MEMORY_MODEL from being enabled and since any of these machines explicitly selects ARCH_SPARSEMEM_ENABLE, the only available memory model would be SPARSEMEM.

Quoted 3 lines

I played a bit with menuconfig and if any of the platforms requiring sparsemem is selected, the menu allowing the user to choose the memory model disappears.

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Quoted 3 lines
Quoted 3 lines
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up
Signature · 7 lines
Sincerely yours,
Mike.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#6 lore raw
Quoted 67 lines · Mike Rapoport
Quoted 62 lines · Mike Rapoport
Quoted 46 lines · Russell King - ARM Linux admin
Quoted 45 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

For example, below is the diffs of the configurations generated with 'make rpc_defconfig' and 'make defconfig':

$ diff -s old/rpc_defconfig new/rpc_defconfig
Files old/rpc_defconfig and new/rpc_defconfig are identical
$ diff -u old/defconfig new/defconfig
defconfig +5 -0
@@ -674,6 +674,9 @@
 CONFIG_AEABI=y
 # CONFIG_OABI_COMPAT is not set
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y
+CONFIG_ARCH_SELECT_MEMORY_MODEL=y
+CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_HAVE_ARCH_PFN_VALID=y
 CONFIG_HIGHMEM=y
 CONFIG_HIGHPTE=y
@@ -1061,6 +1064,9 @@
 #
 # Memory Management options
 #
+CONFIG_SELECT_MEMORY_MODEL=y
+CONFIG_FLATMEM_MANUAL=y
Quoted 8 lines

defconfig line 1072

Quoted 4 lines
defconfig +1 -0
+# CONFIG_SPARSEMEM_MANUAL is not set
 CONFIG_FLATMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
 CONFIG_ARCH_KEEP_MEMBLOCK=y

Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make.

With ARCH_RPC=y (or ARCH_SA1100 or ARCH_EP93XX for that matter) ARCH_MULTIPLATFORM=n which prevents ARCH_SELECT_MEMORY_MODEL from being enabled and since any of these machines explicitly selects ARCH_SPARSEMEM_ENABLE, the only available memory model would be SPARSEMEM.

Quoted 3 lines

I played a bit with menuconfig and if any of the platforms requiring sparsemem is selected, the menu allowing the user to choose the memory model disappears.

Quoted 5 lines

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#7 lore raw
Quoted 48 lines · Russell King - ARM Linux admin
Quoted 37 lines · Mike Rapoport
Quoted 32 lines · Mike Rapoport
Quoted 17 lines · Russell King - ARM Linux admin
Quoted 16 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

Hi,

Following the discussion at [1], I'm resending the patches that enable memory model selection in menuconfig and such.

These patches do not change the way the configuration is generated from the defconfigs and they do not change explicit selection of SPARSEMEM for platforms that have "select ARCH_ENABLE_SPARSEMEM".

The mere change is that when a user runs an interactive configuration they will be allowed to select between FLATMEM and SPARSMEM, which is not the case today.

Quoted 7 lines
Quoted 4 lines

There is indeed some awkwardness in, e.g. removal of ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in mm/Kconfig imposes.

Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make.

With ARCH_RPC=y (or ARCH_SA1100 or ARCH_EP93XX for that matter) ARCH_MULTIPLATFORM=n which prevents ARCH_SELECT_MEMORY_MODEL from being enabled and since any of these machines explicitly selects ARCH_SPARSEMEM_ENABLE, the only available memory model would be SPARSEMEM.

Quoted 3 lines

I played a bit with menuconfig and if any of the platforms requiring sparsemem is selected, the menu allowing the user to choose the memory model disappears.

Quoted 5 lines

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

Quoted 7 lines

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

I honestly don't know, it was Arnd who was talking about adding ep93xx to multiplat.

So, probably better phrasing would have been "if either of these patforms will become a part of the multiplatform build...".

Anyway, benchmarking sparsemem vs flatmem on a platform that is already a part of multiplat might be useful to understand whether we need both of them or we can simply make everything use sparsemem.

Quoted 3 lines
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up
Signature · 7 lines
Sincerely yours,
Mike.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#8 lore raw
In reply to Russell King - ARM Linux admin

Hi Russell,

Quoted 11 lines · Russell King - ARM Linux admin
Quoted 5 lines · Mike Rapoport

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

Quoted 7 lines

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

The fallacy of "multi-platform", again?

Isn't it a requirement for any new ARM v7-A platforms to be part of ARCH_MULTI_V7, even if it's a low-end machine?

Gr{oetje,eeting}s,

Geert

Signature · 10 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#9 lore raw
Quoted 19 lines · Geert Uytterhoeven

Hi Russell,

Quoted 15 lines · Russell King - ARM Linux admin
Quoted 5 lines · Mike Rapoport

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

Quoted 8 lines
Quoted 3 lines

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

The fallacy of "multi-platform", again?

Isn't it a requirement for any new ARM v7-A platforms to be part of ARCH_MULTI_V7, even if it's a low-end machine?

What does ARMv7 have to do with this thread, that is discussing the older ARMv4 platforms? I find your comments above irrelevent to this discussion, and seems to be worded to provoke a reaction.

Not playing.

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#10 lore raw

Hi Russell,

Quoted 22 lines · Russell King - ARM Linux admin
Quoted 21 lines · Geert Uytterhoeven
Quoted 18 lines · Russell King - ARM Linux admin
Quoted 5 lines · Mike Rapoport

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

Quoted 8 lines
Quoted 4 lines

The fallacy of "multi-platform", again?

Isn't it a requirement for any new ARM v7-A platforms to be part of ARCH_MULTI_V7, even if it's a low-end machine?

What does ARMv7 have to do with this thread, that is discussing the older ARMv4 platforms? I find your comments above irrelevent to this discussion, and seems to be worded to provoke a reaction.

Sorry, I used ARMv7 as an example, as it's rare for any new ARMv4 platforms to show up. But the recently introduced sam9x60 (ARMv5) is part of ARCH_MULTI_V5, and I expect it will be used with less than the 256 MiB provided on the dev board.

Nevertheless, there's a movement to convert everything to ARCH_MULTI_V* where possible. So it matters for all variants.

Gr{oetje,eeting}s,

Geert

Signature · 10 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#11 lore raw
Quoted 35 lines · Geert Uytterhoeven

Hi Russell,

Quoted 22 lines · Russell King - ARM Linux admin
Quoted 21 lines · Geert Uytterhoeven
Quoted 18 lines · Russell King - ARM Linux admin
Quoted 5 lines · Mike Rapoport

Ah, when either of these patforms will become a part of the multiplatform build, the only option for multiplatform build will be sparsemem.
So it would be nice if somebody could check the cost of using sparsemem vs flatmem, espessially on low end machines.

Do you think they will become part of multiplatform?

If they're low-end machines, then adding:

(a) the additional memory overhead of a multiplatform kernel
(b) the additional runtime overhead of the complexities of multiplatform kernels

is surely an odd thing to do, especially when few really care about these platforms becoming part of a multiplatform kernel, except those who like the idea of multiplat.

Quoted 8 lines
Quoted 4 lines

The fallacy of "multi-platform", again?

Isn't it a requirement for any new ARM v7-A platforms to be part of ARCH_MULTI_V7, even if it's a low-end machine?

What does ARMv7 have to do with this thread, that is discussing the older ARMv4 platforms? I find your comments above irrelevent to this discussion, and seems to be worded to provoke a reaction.

Quoted 7 lines

Sorry, I used ARMv7 as an example, as it's rare for any new ARMv4 platforms to show up. But the recently introduced sam9x60 (ARMv5) is part of ARCH_MULTI_V5, and I expect it will be used with less than the 256 MiB provided on the dev board.

Nevertheless, there's a movement to convert everything to ARCH_MULTI_V* where possible. So it matters for all variants.

First, please understand that I have nothing against multiplatform.

What I do have problems with is the "lets move everything to multiplatform" without fully reasoning it out, especially when it comes to older platforms that have limited attraction for the whole motivation behind multiplatform, which is the convenience of distributions.

multiplatform is the current fad-de-jour, and everyone is in a "you MUST convert EVERYTHING to it, because it's the best thing since sliced bread".

multiplatform comes with it a load of forced-enabled options that are force-enabled. Should RiscPC be forced to have the common clock support built into the kernel, when it doesn't' have _any_ controllable clocks, when it's likely that the machines have limited memory available? Yes, I have recently booted the RiscPC with a 5.x kernel, and no, it didn't need very much fixing, the code is quite *stable* (oh, I blaspheme, we can't have stable code in Linux, we must change it every five minutes.)

I think, maybe, you should leave these decisions to people who actually have the platforms, know them inside out, and can assess whether conversion really makes sense or not, rather than blindly joining the zombie march repeating "multiplatform is great, everything must be multiplatform".

What is patently obvious is that in Linux, there is no tolerance of someone who has a differing view, and they end up receiving reaction provoking comments designed to inflame the situation. Difference of opinion must be suppressed at all costs!

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#12 lore raw
In reply to Mike Rapoport
Quoted 2 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

There are two patches in the patch system, submitted within minutes of each other, with the same summary "Allow either FLATMEM or SPARSEMEM on the multiplatform build" but the patch and commit messages are different. I guess the summary for one of the patches is wrong?

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#13 lore raw
Quoted 8 lines · Russell King - ARM Linux admin
Quoted 2 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

There are two patches in the patch system, submitted within minutes of each other, with the same summary "Allow either FLATMEM or SPARSEMEM on the multiplatform build" but the patch and commit messages are different. I guess the summary for one of the patches is wrong?

Oops, my mistake.

The patch 8979/1 should have "ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting" in its subject.

Sorry.

Quoted 3 lines
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up
Signature · 7 lines
Sincerely yours,
Mike.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
#14 lore raw
Quoted 10 lines · Mike Rapoport
Quoted 8 lines · Russell King - ARM Linux admin
Quoted 2 lines · Mike Rapoport

(resendig for the correct address and with mailing list cc'ed, sorry for the noise)

There are two patches in the patch system, submitted within minutes of each other, with the same summary "Allow either FLATMEM or SPARSEMEM on the multiplatform build" but the patch and commit messages are different. I guess the summary for one of the patches is wrong?

Quoted 4 lines

Oops, my mistake.

The patch 8979/1 should have "ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting" in its subject.

Thanks; updated the database with that.

Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel