Re: [gem5-dev] Review Request 3578: ruby: Size the MI_example directory to cover all phys mem

> On July 25, 2016, 2:26 p.m., Jason Lowe-Power wrote: > > This seems like it's OK. The only problem that may crop up is that the > > DirectoryMemory pre-populates an entry for every block in physical memory > > (as configured here). So, if the max physical memory is high, you may run > > out

Re: [gem5-dev] Review Request 3579: x86, sim: add some syscalls to X86

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3579/#review8540 --- Ship it! Ship It! - Michael LeBeane On July 22, 2016, 3:58 p.m.,

Re: [gem5-dev] Review Request 3575: ruby: Implement support for functional accesses to PIO ranges

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3575/#review8539 --- Ship it! Ship It! - Michael LeBeane On July 22, 2016, 3:47 p.m.,

Re: [gem5-dev] Review Request 3577: arm, config: Add initial support for Ruby

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3577/#review8538 --- Ship it! Ship It! - Brad Beckmann On July 22, 2016, 3:06 p.m.,

Re: [gem5-dev] Review Request 3576: arm, dev: Add support for listing DMA ports in new platforms

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3576/#review8537 --- Ship it! Ship It! - Brad Beckmann On July 22, 2016, 3:05 p.m.,

Re: [gem5-dev] Review Request 3575: ruby: Implement support for functional accesses to PIO ranges

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3575/#review8536 --- Ship it! Thanks for posting this. We actually have a very similar

[gem5-dev] Installing a Compiled Kernel to Disk Image for ARM

Hi, I have compiled a linux kernel as instructed on the wiki http://www.m5sim.org/ARM_Linux_Kernel. Can anyone let me know as to how to create a disk image from this compiled kernel, or how to install the kernel on to a disk image ? Regards Yasir

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

> On July 25, 2016, 1:18 p.m., Nikos Nikoleris wrote: > > Ship It! > > Sophiane SENNI wrote: > How can I commit the patch ? I am not sure I have the commit access ? > > Nikos Nikoleris wrote: > You can't commit it youself, one of the maintainers will have to commit > it for you. Hi

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

> On July 25, 2016, 1:18 p.m., Nikos Nikoleris wrote: > > Ship It! > > Sophiane SENNI wrote: > How can I commit the patch ? I am not sure I have the commit access ? You can't commit it youself, one of the maintainers will have to commit it for you. - Nikos

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

> On juil. 25, 2016, 1:18 après-midi, Nikos Nikoleris wrote: > > Ship It! How can I commit the patch ? I am not sure I have the commit access ? - Sophiane --- This is an automatically generated e-mail. To reply, visit:

Re: [gem5-dev] Review Request 3577: arm, config: Add initial support for Ruby

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3577/#review8531 --- Ship it! Nice to see ARM thinking about Ruby support! Should we enable

Re: [gem5-dev] Review Request 3579: x86, sim: add some syscalls to X86

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3579/#review8530 --- Ship it! Seems reasonable. Any chance for a simple test of these

Re: [gem5-dev] Review Request 3578: ruby: Size the MI_example directory to cover all phys mem

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3578/#review8529 --- This seems like it's OK. The only problem that may crop up is that the

Re: [gem5-dev] Review Request 3575: ruby: Implement support for functional accesses to PIO ranges

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3575/#review8528 --- Ship it! Ship It! - Jason Lowe-Power On July 22, 2016, 3:47 p.m.,

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3502/#review8527 --- Ship it! Ship It! - Pierre-Yves Péneau On July 25, 2016, 3:16 p.m.,

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

> On juil. 23, 2016, 2:05 après-midi, Nikos Nikoleris wrote: > > src/mem/cache/tags/Tags.py, line 68 > > > > > > This stale argument causes the problems you're facing please remove it, > > I don't think it is needed You

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3502/#review8525 --- Ship it! Ship It! - Nikos Nikoleris On July 25, 2016, 1:16 p.m.,

Re: [gem5-dev] Review Request 3502: mem: Split the hit_latency into tag_latency and data_latency

--- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/3502/ --- (Updated juil. 25, 2016, 1:16 après-midi) Review request for Default.

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

* build/ALPHA/tests/opt/quick/se/20.eio-short/alpha/eio/simple-atomic: CHANGED! * build/ALPHA/tests/opt/quick/se/20.eio-short/alpha/eio/simple-timing: CHANGED!*** diff[simout]: SKIPPED * build/ALPHA/tests/opt/quick/se/30.eio-mp/alpha/eio/simple-atomic-mp: CHANGED! *