Re: [PATCH v3 03/13] mm/execmem, arch: convert simple overrides of module_alloc to execmem
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Date: 2023-10-05 18:12:42
Also in:
bpf, linux-arm-kernel, linux-mips, linux-mm, linux-modules, linux-riscv, linux-s390, linux-trace-kernel, linuxppc-dev, lkml, loongarch, sparclinux
On Mon, 2023-09-18 at 10:29 +0300, Mike Rapoport wrote:
+/**
+ * struct execmem_range - definition of a memory range suitable for
code and
+ * related data allocations
+ * @start: address space start
+ * @end: address space end (inclusive)
+ * @pgprot: permissions for memory in this address space
+ * @alignment: alignment required for text allocations
+ */
+struct execmem_range {
+ unsigned long start;
+ unsigned long end;
+ pgprot_t pgprot;
+ unsigned int alignment;
+};Not a strong opinion, but range doesn't seem an appropriate name. It *has* a range, but also other allocation configuration. It gets especially confusing when multiple "ranges" have the same range. Maybe execmem_alloc_params?