# git rev-parse -q --verify 8e9ad2720cd1cf55530755362ad899f69e09fb9a^{commit} 8e9ad2720cd1cf55530755362ad899f69e09fb9a already have revision, skipping fetch # git checkout -q -f -B kisskb 8e9ad2720cd1cf55530755362ad899f69e09fb9a # git clean -qxdf # < git log -1 # commit 8e9ad2720cd1cf55530755362ad899f69e09fb9a # Author: Michael Ellerman # Date: Wed Feb 12 22:11:00 2020 +1100 # # powerpc/xmon: Lower limits on nidump and ndump # # In xmon we have two variables that are used by the dump commands. # There's ndump which is the number of bytes to dump using 'd', and # nidump which is the number of instructions to dump using 'di'. # # ndump starts as 64 and nidump starts as 16, but both can be set by the # user. # # It's fairly common to be pasting addresses into xmon when trying to # debug something, and if you inadvertently double paste an address like # so: # # 0:mon> di c000000002101f6c c000000002101f6c # # The second value is interpreted as the number of instructions to dump. # # Luckily it doesn't dump 13 quintrillion instructions, the value is # limited to MAX_DUMP (128K). But as each instruction is dumped on a # single line, that's still a lot of output. If you're on a slow console # that can take multiple minutes to print. If you were "just popping in # and out of xmon quickly before the RCU/hardlockup detector fires" you # are now having a bad day. # # Things are not as bad with 'd' because we print 16 bytes per line, so # it's fewer lines. But it's still quite a lot. # # So shrink the maximum for 'd' to 64K (one page), which is 4096 lines. # For 'di' add a new limit which is the above / 4 - because instructions # are 4 bytes, meaning again we can dump one page. # # Signed-off-by: Michael Ellerman # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 8e9ad2720cd1cf55530755362ad899f69e09fb9a # < make -s -j 48 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- defconfig # make -s -j 48 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:35: LSE atomics not supported by binutils In file included from /kisskb/src/include/linux/rwsem.h:16:0, from /kisskb/src/include/linux/notifier.h:15, from /kisskb/src/include/linux/clk.h:14, from /kisskb/src/drivers/tty/serial/sh-sci.c:20: /kisskb/src/drivers/tty/serial/sh-sci.c: In function 'sci_dma_rx_submit': /kisskb/src/include/linux/spinlock.h:288:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] _raw_spin_unlock_irqrestore(lock, flags); \ ^ /kisskb/src/drivers/tty/serial/sh-sci.c:1348:16: note: 'flags' was declared here unsigned long flags; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr': /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] pd->msg->buf[real_pos] = data; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:372:16: note: 'data' was declared here unsigned char data; ^ Completed OK # rm -rf /kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 # Build took: 0:05:19.314310