2f7d03e051
Memory addtion and removal by count and indexed-count methods
temporarily mark the LMBs that are being added/removed by a special
flag value DRMEM_LMB_RESERVED. Accessing flags value directly at a few
places without proper accessor method is causing two unexpected
side-effects:
- DRMEM_LMB_RESERVED bit is becoming part of the flags word of
drconf_cell_v2 entries in ibm,dynamic-memory-v2 DT property.
- This results in extra drconf_cell entries in ibm,dynamic-memory-v2.
For example if 1G memory is added, it leads to one entry for 3 LMBs
and 1 separate entry for the last LMB. All the 4 LMBs should be
defined by one entry here.
Fix this by always accessing the flags by its accessor method
drmem_lmb_flags().
Fixes:
|
||
---|---|---|
.. | ||
8xx_mmu.c | ||
40x_mmu.c | ||
44x_mmu.c | ||
copro_fault.c | ||
dma-noncoherent.c | ||
drmem.c | ||
dump_hashpagetable.c | ||
dump_linuxpagetables.c | ||
fault.c | ||
fsl_booke_mmu.c | ||
hash64_4k.c | ||
hash64_64k.c | ||
hash_low_32.S | ||
hash_native_64.c | ||
hash_utils_64.c | ||
highmem.c | ||
hugepage-hash64.c | ||
hugetlbpage-book3e.c | ||
hugetlbpage-hash64.c | ||
hugetlbpage-radix.c | ||
hugetlbpage.c | ||
init_32.c | ||
init_64.c | ||
init-common.c | ||
Makefile | ||
mem.c | ||
mmap.c | ||
mmu_context_book3s64.c | ||
mmu_context_hash32.c | ||
mmu_context_iommu.c | ||
mmu_context_nohash.c | ||
mmu_context.c | ||
mmu_decl.h | ||
numa.c | ||
pgtable_32.c | ||
pgtable_64.c | ||
pgtable-book3e.c | ||
pgtable-book3s64.c | ||
pgtable-hash64.c | ||
pgtable-radix.c | ||
pgtable.c | ||
pkeys.c | ||
ppc_mmu_32.c | ||
slb_low.S | ||
slb.c | ||
slice.c | ||
subpage-prot.c | ||
tlb_hash32.c | ||
tlb_hash64.c | ||
tlb_low_64e.S | ||
tlb_nohash_low.S | ||
tlb_nohash.c | ||
tlb-radix.c | ||
vphn.c | ||
vphn.h |