Hi Ruijie, Thanks for your kindly reply. I also successfully run the Parsec suite on Alpha architecture. When I tried on X86, I got
request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c request_module: runaway loop modprobe binfmt-464c I think there is something wrong with the disk image I used. Can you please tell me how did you get the parsec binaries into the x86root image? I know the gem5img.py tool, but it seems like there is very limited information on this. I tried to load two disk images at the same time but failed. Thanks for any of your inputs! -Yang On Thu, Nov 1, 2012 at 10:12 AM, Runjie Zhang <[email protected]> wrote: > I did ran parsec in x86, multi thread with ruby without any > modification to the source code. (Thanks to Marco Elver's great help!) > > Here are some details about disk images, binaries and linux kernel > file that I used: > > - Pre-compiled X86 kernel: > [http://www.cs.utexas.edu/~parsec_m5/x86_64-vmlinux-2.6.28.4-smp] > - linux-bigswap2.img: From the alpha bundle > [http://www.m5sim.org/dist/current/m5_system_2.0b3.tar.bz2] > - X86 full system image: > [http://www.m5sim.org/dist/current/x86/x86-system.tar.bz2]. > - Parsec pre-compiled binaries: > [ > http://parsec.cs.princeton.edu/download/2.1/binaries/parsec-2.1-amd64-linux.tar.gz > ] > > To get parsec binaries into the x86root image, you can use > gem5/util/gem5img.py. > To be able to take checkpoint and restore with Ruby mem, you need to > use MOESI_hammer protocol. > > Hope this helps! > Runjie > > > ----------------------------------------------------------------------------------------------------- > > Did you run them all in x86, multi thread with ruby? > I guess you should've edit the source code ... > > I'd appreciate if you post the disk image :) > > On Wed, Oct 31, 2012 at 5:34 PM, Runjie Zhang <[email protected]> wrote: > > I have successfully ran Parsec with recent > version(changeset:01c8c5ff2c3b) > > of Gem5 for both ALPHA and X86 ISA. > > > > What error did you get? > > > > Runjie > > > > > ----------------------------------------------------------------------------------------------------- > > > > Date: Wed, 31 Oct 2012 00:12:12 -0700 > > From: Frank Yang <[email protected]> > > To: [email protected] > > Subject: [gem5-users] Running PARSEC on GEM5 > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset=us-ascii > > > > > > Hi All, > > > > I am trying to run Parsec on Gem5. After did a google work, I found that > > there is a project to port Parsec 2.1 to Gem5 ALPHA architecture. I tried > > that but failed. In that website, they also provided a X85_64 kernel to > run > > the Parsec binary, also failed. I was wondering is this because the Gem5 > I > > am using is the most recent version so it changes something? > > > > The last approach I want to try is to boot using the disk image provided > by > > the Gem5 website (which I am able to run under X85 FS mode), and mount > > another image with the Parsec suite. But I have 2 concerns. The first > one is > > if I have to build the Parsec suite on the simulator, will it take a very > > long time? The second is how to boot the simulation system by mounting > two > > disk images? > > > > Thanks! > > Frank > > > > _______________________________________________ > > gem5-users mailing list > > [email protected] > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- Yang "Frank" Yang Graduate Student Computer Architecture Group University of California, Riverside
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
