Hi Fulya, I have attached the patch file. You have to download the kernel source code for 2.6.22 from kernel.org, apply the patch, and then build the kernel.
x86 full-system with more than one O3 CPU with the classic memory model does not currently work in gem5. A couple months ago, Steve Reinhardt described how to potentially fix it. It requires locking the cache lines involved in RMW transactions. I tried to implement a quick solution based on his idea, but I couldn't quite get it to work. Due to time constraints, I started using arm64. If you use ruby instead of the classic memory model in x86, it should work. However, I am not familiar with which ruby configurations work. Ivan On Thu, Sep 18, 2014 at 2:50 PM, Fulya via gem5-users <gem5-users@gem5.org> wrote: > Hi Ivan, > I am having the same problem with running X86 FS with PARSEC, multicore, > detailed cpu and classic memory model. I have been using the same > linux-2.6.22 kernel (which i configured to run with up to 64 CPUs). I have > been getting “bad page” errors after switching to detailed cpu posted below: > …. > [HOOKS] Entering ROI > Bad page state in process 'blackscholes' > page:ffffffff80721d68 flags:0x0000000000000000 mapping:000000baffffffff > mapcount:1 count:0 > Trying to fix it up, but a reboot is needed > Backtrace: > > Call Trace: > [<ffffffff8025d28d>] bad_page+0x5d/0x90 > [<ffffffff8025dcdb>] get_page_from_freelist+0x41b/0x430 > [<ffffffff8025dd81>] __alloc_pages+0x91/0x350 > [<ffffffff8025e074>] get_zeroed_page+0x34/0x70 > [<ffffffff80267558>] __pte_alloc+0x28/0x100 > [<ffffffff80268239>] __handle_mm_fault+0xc09/0xcd0 > [<ffffffff8026c32e>] vma_adjust+0x13e/0x500 > [<ffffffff805be58f>] do_page_fault+0x1af/0x900 > [<ffffffff8026dbac>] do_mmap_pgoff+0x71c/0xab0 > [<ffffffff80378c21>] __up_write+0x21/0x140 > [<ffffffff805bc8bd>] error_exit+0x0/0x84 > > Unable to handle kernel paging request at 926cee92209ab000 RIP: > [<ffffffff8037b092>] clear_page+0x12/0x40 > PGD 0 > ….. > > Could you share with me the linux patch you got from Jiuyue Ma and walk me > through how you applied the patch briefly? > If my problem is instead related to the "unimplemented x86 atomics in the > classic memory hierarchy”, how can I run X86 FS with multicore, detailed > cpu and ruby model? Do you know of a configuration (protocol, simple cpu > type, detailed cpu type to use, whether to use fast forwarding or > checkpointing etc.) that works with a given gem5 stable version? > Best, > Fulya > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
uart_deadlock_linux-2.6.22.patch
Description: Binary data
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
