Messages in this thread | | | From | Anders Roxell <> | Subject | [RFC PATCH 0/3] Make allmodconfig boot in qemu-arm64 | Date | Thu, 13 Dec 2018 13:29:07 +0100 |
| |
Hi,
With this patch set I've been able to get a allmodconfig kernel to boot under qemu-system-aarch64.
The patch "config: provide a fragment to enable gdb for qemu" I found useful when trying to figure out how it fall over. So when I have to debug a kernel with gdb I just ran this: $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -skj$(getconf _NPROCESSORS_ONLN) O=obj-arm64-next-20181213 allmodconfig kvm_guest.config qemu-gdb.config $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -skj$(getconf _NPROCESSORS_ONLN) O=obj-arm64-next-20181213 Image
Before we do the same job on other architectures we wanted to reach out and ask to see if this seams a reasonable way forward ?
The end goal would be to be able to run test suites on a allmodconfig kernel. We may end up with another fragment that turn off/on a lot of debug options and selftests during boot up since that may cause issues for other test suites like kseftest, LTP and so on.
Cheers, Anders
Anders Roxell (3): config: provide a fragment to enable gdb for qemu lib/ubsan: default UBSAN_ALIGNMENT to not set arm64: add a new config option KTEST_RUNNABLE
arch/arm64/Kconfig | 8 ++++++++ drivers/tty/hvc/Kconfig | 1 + init/Kconfig | 1 + kernel/configs/qemu-gdb.config | 7 +++++++ lib/Kconfig.ubsan | 14 +++++++++----- 5 files changed, 26 insertions(+), 5 deletions(-) create mode 100644 kernel/configs/qemu-gdb.config
-- 2.19.2
| |