Re: [gem5-dev] Architecture of gem5

2016-09-09 Thread Potter, Brandon
Yeah, I remember the "Linux process trackers"; they were my motivation for exploring the memory reads on the kernel structures. I wanted to extend them, but the source was closed so I started hacking around to implement my own. Unfortunately, I don't get to use FS here at AMD much; we rely

Re: [gem5-dev] Architecture of gem5

2016-09-09 Thread Potter, Brandon
gem5/src/arch/x86/process.hh gem5/src/arch/x86/process.cc gem5/src/arch/x86/regs/misc.hh gem5/src/arch/x86/regs/segment.hh I'd look through full-system code and either find a hook or make one to allow access to the segment registers in the preceding files. It might take some time to figure that

Re: [gem5-dev] Review Request 3591: ruby: Allow multiple outstanding DMA requests

2016-09-09 Thread Andreas Hansson
> On Sept. 1, 2016, 3:33 p.m., Jason Lowe-Power wrote: > > What testing did you perform to make sure all of the protocols were > > modified correctly? > > > > Most of these changes seem reasonable to me, but I know from experience > > that even when the SLICC changes seem like they are right,

Re: [gem5-dev] Review Request 3591: ruby: Allow multiple outstanding DMA requests

2016-09-09 Thread Jason Lowe-Power
> On Sept. 1, 2016, 3:33 p.m., Jason Lowe-Power wrote: > > What testing did you perform to make sure all of the protocols were > > modified correctly? > > > > Most of these changes seem reasonable to me, but I know from experience > > that even when the SLICC changes seem like they are right,

Re: [gem5-dev] Review Request 3591: ruby: Allow multiple outstanding DMA requests

2016-09-09 Thread Brad Beckmann
> On Sept. 1, 2016, 3:33 p.m., Jason Lowe-Power wrote: > > What testing did you perform to make sure all of the protocols were > > modified correctly? > > > > Most of these changes seem reasonable to me, but I know from experience > > that even when the SLICC changes seem like they are right,

Re: [gem5-dev] Review Request 3595: dev: Add m5 op to toggle synchronization for dist-gem5.

2016-09-09 Thread Gabor Dozsa
--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3595/#review8713 --- I like the idea of starting the sync on a pseudo op very much. I cannot

Re: [gem5-dev] Architecture of gem5

2016-09-09 Thread Boris Shingarov/Employee/LW-US
I remember back when I was using Simics, there were these things called "Linux process trackers" that did exactly that.  It was all written in Python, and there was a point when various processor-specific trackers got simplified / pulled together into one generic tracker in which only the

[gem5-dev] Cron <m5test@zizzer> /z/m5/regression/do-regression quick

2016-09-09 Thread Cron Daemon
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/minor-timing: passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/minor-timing: passed. * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-timing: passed.*