Re: [PATCH v1] armv8: MMU: Fix the memory map for RAM

rrect not to cause any confusion. > > > Signed-off-by: Marek Bykowski > > > --- > > > Changes in PATCH v1: > > > - now it re-maps the whole RAM to the proper attributes, > > > - took account of other images, eg. PSCI, EFI that need a separate > > >

Re: [PATCH v1] armv8: MMU: Fix the memory map for RAM

abs.org/project/uboot/list/?series=199486 > > If there is another (better) solution I'm in for it as we *should really* fix it this or that way. The link copied doesn't work with me. Can you resend? Marek > > Signed-off-by: Marek Bykowski > > --- > > Chang

[PATCH v1] armv8: MMU: Fix the memory map for RAM

From: Marek Bykowski The objective of this patch is to impose the correct attributes to the RAM memory for the ARM CPU, as shown in the diagram below: -- Non-Cached || Read-Write Ordered | Peripherals |Not

Re: [PATCHv2] armv8: MMU: Mark code memory Executable, any other Non-Executable

> I think this will have to wait for you to return from holidays and > investigate more. All I know is that the QEMU models are working as > expected prior to the patch and fail with it. > > -- > Tom >From the esr (Exception Syndrome Register) = 0x964F: - EC (Exception Class) -> it is an exce

Re: [PATCHv2] armv8: MMU: Mark code memory Executable, any other Non-Executable

On Fri, Jun 19, 2020 at 02:53:32PM +0200, Marek Bykowski wrote: > From: Marek Bykowski > > However if we fail programming so and the instruction fetch logic goes > mispredict to non-instruction memory it may eventually perturb it, eg. > corrupt the FIFO, or the control regi

[PATCHv2] armv8: MMU: Mark code memory Executable, any other Non-Executable

From: Marek Bykowski If the location the ARM CPU is accessing is executable (translation table descriptor Execute-Never attribute bit cleared) then the ARM CPU fetches a number of instructions from that location all at the same time. For example, Cortex-A57 can source up to 128 bits per fetch

[PATCH] armv8: MMU: Mark code memory Executable, any other Non-Executable

From: Marek Bykowski If the location the ARM CPU is accessing is executable (translation table descriptor Execute-Never attribute bit cleared) then the ARM CPU fetches a number of instructions from that location all at the same time. For example, Cortex-A57 can source up to 128 bits per fetch

[PATCH v3] malloc: dlmalloc: add an ability for the malloc to be re-init/init multiple times

From: Marek Bykowski Malloc gets initialized with a call to mem_malloc_init() with the address the allocation starts to and its size. Currently it is not possible to move the malloc from one memory area to another as the malloc would eventually fail. This patch adds in the ability to re-init

[PATCH v2] malloc: dlmalloc: add an ability for the malloc to be re-init/init multiple times

From: Marek Bykowski Malloc gets initialized with a call to mem_malloc_init() with the address the allocation starts to and its size. Currently it is not possible to move the malloc from one memory area to another as the malloc would eventually fail. This patch adds in the ability to re-init

[PATCH] malloc: dlmalloc: add an ability for the malloc to be re-init/init multiple times

From: Marek Bykowski Malloc gets initialized with a call to mem_malloc_init() with the address the allocation starts to and its size. Currently it is not possible to move the malloc from one memory area to another as the malloc would eventually fail. This patch adds in the ability to re-init

Re: [PATCH] dlmalloc: Add an option to default malloc to init

> > OK, thanks. Can you please re-send and include the above re-phrased to > make sense in a commit message, in the body of the commit as well so > it's documented more in-tree when this would be helpful? Thanks again! > > -- > Tom Sure Tom. Will do that Monday/Tuesday. Thanks, Marek

[PATCH] dlmalloc: Add an option to default malloc to init

From: Marek Bykowski If a system wants the malloc to get moved around from one to another memory range it should call mem_malloc_init() with the updated memory ranges. However setting aside the new memory alone isn't enough. It should also bring the bins and static bookkeeping data to init.

[PATCH] Kconfig: update LOGLEVEL range

From: Marek Bykowski As LOGLEVEL ranges form 0 to 9 set the limit to 10. Signed-off-by: Marek Bykowski --- common/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/Kconfig b/common/Kconfig index 28d5e9a0cc..d1c9dd47cf 100644 --- a/common/Kconfig +++ b/common