Request req->isUncacheable() checks if the request is an uncacheable access, and is set by the TLB lookup. Based on a quick search in the source code, I see that this has only been implemented in the classic memory model, and not in Ruby. Hopefully someone correct me if I am wrong.
You could try searching the reviewboard (www.reviews.gem5.org) to see if someone has attempted to add this functionality, but I don't think there is any good way to search the review board currently. Alternatively, you could implement this yourself, and later submit your changes into the mainstream gem5 source. Cheers, Swapnil Haria, Graduate Student, Dept of Computer Sciences, University of Wisconsin-Madison On Mon, Nov 21, 2016 at 12:30 AM, Azin Heidarshenas < azin.heidarshe...@gmail.com> wrote: > Hi, > Is it possible to have uncacheable memory address space in Ruby? > > Thanks, > -- > Azin > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
