Buildresult: powerpc-next/mmu_defconfig/microblaze-gcc5 built on Oct 14 2018, 00:41

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Oct 14 2018, 00:41
Duration:	0:00:49.580804
Builder:	ka3
Revision:	powerpc/mm: Increase the max addressable memory to 2PB (`8f0c636b05429d3a83993074c35fce62eb9856ef)`
Target:	powerpc-next/mmu_defconfig/microblaze-gcc5
Branch:	powerpc-next
Compiler:	microblaze-gcc5 (microblazeel-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0)
Config:	mmu_defconfig (download)
Log:	Download original Possible warnings (1) drivers/i2c/i2c-core-base.c:235:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] Full Log # git rev-parse -q --verify 8f0c636b05429d3a83993074c35fce62eb9856ef^{commit} 8f0c636b05429d3a83993074c35fce62eb9856ef already have revision, skipping fetch # git checkout -q -f -B kisskb 8f0c636b05429d3a83993074c35fce62eb9856ef # git clean -qxdf # < git log -1 # commit 8f0c636b05429d3a83993074c35fce62eb9856ef # Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> # Date: Thu Sep 20 14:03:58 2018 +0530 # # powerpc/mm: Increase the max addressable memory to 2PB # # Currently we limit the max addressable memory to 128TB. This patch increase the # limit to 2PB. We can have devices like nvdimm which adds memory above 512TB # limit. # # We still don't support regular system ram above 512TB. One of the challenge with # that is the percpu allocator, that allocates per node memory and use the max # distance between them as the percpu offsets. This means with large gap in # address space ( system ram above 1PB) we will run out of vmalloc space to map # the percpu allocation. # # In order to support addressable memory above 512TB, kernel should be able to # linear map this range. To do that with hash translation we now add 4 context # to kernel linear map region. Our per context addressable range is 512TB. We # still keep VMALLOC and VMEMMAP region to old size. SLB miss handlers is updated # to validate these limit. # # We also limit this update to SPARSEMEM_VMEMMAP and SPARSEMEM_EXTREME # # Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # < /opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-gcc --version # < git log --format=%s --max-count=1 8f0c636b05429d3a83993074c35fce62eb9856ef # < make -s -j 80 ARCH=microblaze O=/kisskb/build/powerpc-next_mmu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- mmu_defconfig # make -s -j 80 ARCH=microblaze O=/kisskb/build/powerpc-next_mmu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- /kisskb/src/drivers/i2c/i2c-core-base.c: In function 'i2c_generic_scl_recovery': /kisskb/src/drivers/i2c/i2c-core-base.c:235:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] if (ret == -EOPNOTSUPP) ^ Kernel: arch/microblaze/boot/linux.bin is ready (#1) Completed OK # rm -rf /kisskb/build/powerpc-next_mmu_defconfig_microblaze # Build took: 0:00:49.580804

© Michael Ellerman 2006-2018.