On Sun, Jan 15, 2017 at 01:12:15PM -0800, Luis R. Rodriguez wrote: > Add a userspace sandbox to allow easy experimentation and > test extensions with linker tables, section ranges and the > new section core definitions. > > The userspace sandbox tries to mimic the Linux kernel development > flow as much as possible, it however relies on and uses libc. Support > is currently only provided to x86_64.
Why is x86_64 a requirement? > > Demo run: > > cd tools/linker-tables > make clean; make; > ./demo > Initializing x86 bare metal world > x86-init: Number of init entries: 8 > Initializing memory ... > Completed initializing memory ! > Initializing pci ... > PCI fixup size: 1 > Demo: Using LINKTABLE_FOR_EACH > foo_fixup > Demo: Using LINKTABLE_RUN_ALL > foo_fixup > Completed initializing pci ! > Number of init entries: 1 > Initializing kprobes ... > == OK: test_kprobe_0001 within range! > == OK: test_kprobe_0002 not in range as expected! > Completed initializing kprobes ! > Initializing kasan ... > Early init for Kasan... > Completed initializing kasan ! > Initializing beta ... > Completed initializing beta ! > Initializing alpha ... > Completed initializing alpha ! > Booting bare metal > Calling start_kernel()... > ACME: Initializing ... > ACME: Finished init ... ! > Synthetics: synth_init_or(2) returns: 0xDEADBEEF > Synthetics: ps_shr(0xDEADBEEF, get_demo_shr) returns: 0x0000DEAD Why isn't this tied into the kernel testing framework? thanks, greg k-h _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
