# git rev-parse -q --verify cc725cb44569f990c9aa4fd2ee08fa3f95237b02^{commit}
# git fetch -q -n -f git://gitlab.ozlabs.ibm.com/linuxppc/linux.git fixes-test
warning: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

# git rev-parse -q --verify cc725cb44569f990c9aa4fd2ee08fa3f95237b02^{commit}
cc725cb44569f990c9aa4fd2ee08fa3f95237b02
# git checkout -q -f -B kisskb cc725cb44569f990c9aa4fd2ee08fa3f95237b02
# git clean -qxdf
# < git log -1
# commit cc725cb44569f990c9aa4fd2ee08fa3f95237b02
# Author: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
# Date:   Wed Jul 10 15:20:18 2019 +1000
# 
#     powerpc: mm: Limit rma_size to 1TB when running without HV mode
#     
#     The virtual real mode addressing (VRMA) mechanism is used when a
#     partition is using HPT (Hash Page Table) translation and performs
#     real mode accesses (MSR[IR|DR] = 0) in non-hypervisor mode. In this
#     mode effective address bits 0:23 are treated as zero (i.e. the access
#     is aliased to 0) and the access is performed using an implicit 1TB SLB
#     entry.
#     
#     The size of the RMA (Real Memory Area) is communicated to the guest as
#     the size of the first memory region in the device tree. And because of
#     the mechanism described above can be expected to not exceed 1TB. In the
#     event that the host erroneously represents the RMA as being larger than
#     1TB, guest accesses in real mode to memory addresses above 1TB will be
#     aliased down to below 1TB. This means that a memory access performed in
#     real mode may differ to one performed in virtual mode for the same memory
#     address, which would likely have unintended consequences.
#     
#     To avoid this outcome have the guest explicitly limit the size of the
#     RMA to the current maximum, which is 1TB. This means that even if the
#     first memory block is larger than 1TB, only the first 1TB should be
#     accessed in real mode.
#     
#     Fixes: c3ab300ea555 ("powerpc: Add POWER9 cputable entry")
#     Cc: stable@vger.kernel.org # v4.6+
#     Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
#     Tested-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
#     Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
#     Link: https://lore.kernel.org/r/20190710052018.14628-1-sjitindarsingh@gmail.com
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux-gcc --version
# < /opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux-ld --version
# < git log --format=%s --max-count=1 cc725cb44569f990c9aa4fd2ee08fa3f95237b02
# < make -s -j 80 ARCH=x86_64 O=/kisskb/build/powerpc-fixes_x86_64-allnoconfig_x86_64-gcc4.6 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux-  allnoconfig
# make -s -j 80 ARCH=x86_64 O=/kisskb/build/powerpc-fixes_x86_64-allnoconfig_x86_64-gcc4.6 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/x86_64-linux/bin/x86_64-linux-  
/kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl':
/kisskb/src/kernel/printk/printk.c:194:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/arch/x86/kernel/apic/io_apic.c: In function 'mp_map_pin_to_irq':
/kisskb/src/arch/x86/kernel/apic/io_apic.c:1037:6: warning: 'irq' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/arch/x86/kernel/e820.c: In function 'e820__setup_pci_gap':
/kisskb/src/arch/x86/kernel/e820.c:664:16: warning: 'gapstart' may be used uninitialized in this function [-Wuninitialized]
Completed OK
# rm -rf /kisskb/build/powerpc-fixes_x86_64-allnoconfig_x86_64-gcc4.6
# Build took: 0:00:49.464641