Yes. They're both on zizzer. The kernel is in /dist/m5/system/binaries/x86_64-vmlinux-2.6.22.9 and the disk image is in /dist/m5/system/disks/x86root.img. The head is up to the point where you'll get the very first page fault for user code and it'll die.
Gabe nathan binkert wrote: > Can you put the images and kernels that you're working with somewhere > so people can play if they want? > > Nate > > On Sun, Feb 1, 2009 at 5:18 PM, Gabe Black <[email protected]> wrote: > >> changeset 08c65e29e57e in /z/repo/m5 >> details: http://repo.m5sim.org/m5?cmd=changeset;node=08c65e29e57e >> description: >> X86: Hook in a hard drive image. >> >> diffstat: >> >> 1 file changed, 8 insertions(+) >> configs/common/FSConfig.py | 8 ++++++++ >> >> diffs (25 lines): >> >> diff -r 6481e40d21eb -r 08c65e29e57e configs/common/FSConfig.py >> --- a/configs/common/FSConfig.py Sun Feb 01 00:20:44 2009 -0800 >> +++ b/configs/common/FSConfig.py Sun Feb 01 00:24:26 2009 -0800 >> @@ -166,6 +166,7 @@ >> if not mdesc: >> # generic system >> mdesc = SysConfig() >> + mdesc.diskname = 'x86root.img' >> self.readfile = mdesc.script() >> >> # Physical memory >> @@ -185,6 +186,13 @@ >> >> self.intrctrl = IntrControl() >> >> + # Disks >> + disk0 = CowIdeDisk(driveID='master') >> + disk2 = CowIdeDisk(driveID='master') >> + disk0.childImage(mdesc.disk()) >> + disk2.childImage(disk('linux-bigswap2.img')) >> + self.pc.south_bridge.ide.disks = [disk0, disk2] >> + >> # Add in a Bios information structure. >> structures = [X86SMBiosBiosInformation()] >> self.smbios_table.structures = structures >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev >> >> >> > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
