Hi Yasir, You don’t need to alter your disk images to use a new kernel (in fact, you don’t even need a disk image to start the kernel). The bootstrapping process in gem5 works roughly along these lines:
Before time starts (this all happens within gem5): 1. Instantiate all components in the system 2. Load the kernel and DTB into memory 3. Load a minimal boot loader (see system/arm/) into the boot ROM (this is actually implemented as a normal memory) starting at address 0. 4. CPU0: Setup registers to pass information about the kernel and the DTB to the boot loader. At start of time: 5. All CPUs: Start executing from address 0 This means that the kernel is loaded by gem5. The disk image isn’t used until the kernel starts its block drivers (e.g., IDE or VirtIO). If you use configs/examples/fs.py, you tell gem5 to use a new kernel by passing the --kernel argument. Cheers, Andreas On 25/07/2016, 16:43, "gem5-dev on behalf of Qureshi Yasir Mahmood" <[email protected]<mailto:[email protected]> on behalf of [email protected]<mailto:[email protected]>> wrote: Hi, I have compiled a linux kernel as instructed on the wiki http://www.m5sim.org/ARM_Linux_Kernel. Can anyone let me know as to how to create a disk image from this compiled kernel, or how to install the kernel on to a disk image ? Regards Yasir _______________________________________________ gem5-dev mailing list [email protected]<mailto:[email protected]> http://m5sim.org/mailman/listinfo/gem5-dev IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
