Re: [gem5-dev] Review Request 3684: alpha: Remove ALPHA support and supplemental files

[Jason Lowe-Power]

> On Oct. 25, 2016, 10:13 p.m., Jason Lowe-Power wrote:
> > util/regress, line 45
> > 
> >
> > I think this has been pointed out by Brad in the past, but we need to 
> > keep these tests for other Ruby protocols around. I think it's fine to just 
> > switch them to using x86 instead of Alpha. As far as I know, most Ruby 
> > users are using x86 anyway.
> 
> Andreas Hansson wrote:
> Why X86 and not NULL? I would suggest to let all the ruby testers simply 
> be part of NULL (as suggested in the patch summary). It would be even nicer 
> if we didn't have to compile gem5 for every protocol, but that may be asking 
> too much.
> 
> Jason Lowe-Power wrote:
> There's two components to testing the protocols. First, do they compile, 
> which the NULL ISA would test perfectly well. Second, do they work, which we 
> need to run some applications on the protocol (Linux boot is actually a 
> pretty good application for this).
> 
> I agree that it would be good if Ruby was a library, but I do think it's 
> too much to ask :).
> 
> Andreas Hansson wrote:
> Feel free to add Linux boot to Ruby+X86. Today all we do is "hello" and 
> rubytest. For the latter we don't need an ISA, NULL will do just fine (we use 
> NULL for all the memtest and traffic-gen tests of the classic memory system). 
> Running "hello" seems fairly redundant to me. I would think adding some more 
> synthetic tests should be just as good as "hello" if not better. No?

Yeah, you're probably right. You've convinced me it's fine to just use the NULL 
ISA for most of the protocols. We can revisit adding other tests later.


- Jason


---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3684/#review8981
---


On Oct. 24, 2016, 8:43 p.m., Andreas Hansson wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3684/
> ---
> 
> (Updated Oct. 24, 2016, 8:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11689:e1835e5846b9
> ---
> alpha: Remove ALPHA support and supplemental files
> 
> This patch removes support for ALPHA, and correspondingly also removes
> any devices, tests, supporting functions, and configurations unique to
> ALPHA.
> 
> R.I.P.
> 
> A few things that are worth re-adding using something other than
> ALPHA:
> 
> 1) A two-system regresssion using Ethernet
> 
> 2) Ruby tester regressions using NULL for the variuos Ruby protocols
> 
> 
> Diffs
> -
> 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/drivesys.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/tw

Re: [gem5-dev] Base cpu modification

[Jason Lowe-Power]

Hello,

Could you give us some more details on what you're proposing. What is this
"component"? Do you expect that many people in the community will need/want
to use this component? If so, then it may make sense to incorporate some
changes to the BaseCPU object.

The way I see it is you have three high-level options:
1) Make changes to the BaseCPU. This will likely be the most work to get
the community to accept. Unless it's a change that almost everyone will be
using, I doubt we will want to incorporate it.
2) Make your changes very modular. Modular in the sense that if someone
wants to use gem5 without using your new component they'll never knew you
added it. This should be more that just adding a default "off" parameter.
The key goal is to be the least invasive as possible.
3) Post your code on a fork of gem5. Sometimes you have to make major
modifications to central components to complete your research objective. In
this case, it may be better just to post your code somewhere like github.
Or to go the route we did with gem5-gpu and make it an "external"
component. Though this has the drawback of trying to keep it up to date
with the mainline.

In conclusion, if you can give us more information we'll be able to guide
you better.

Cheers,
Jason

On Tue, Oct 25, 2016 at 9:29 AM Pierre-Yves Péneau <
pierre-yves.pen...@lirmm.fr> wrote:

> Hi all,
>
> I would like to add a new hardware component in gem5. This component
> will be at the same level than L1 caches. I am planning to modify the
> base cpu to add a new port and use it to communicate with my component.
>
> Eventually, I would like to share my work with the gem5 community.
> Louisa Bessad (from my lab) had a discussion with Gabor Dozsa from ARM
> and told me that any modification to the base cpu must be strongly
> justified to the developers, and so could be very hard to merge in gem5.
>
> So, my questions are:
> - can I do what I want without modifying the base cpu ?
> - if not, what are the chances that my work will be accepted ?
>
> Thank you all.
>
> --
> +-+
> | Pierre-Yves Péneau - PhD student |  first.last at lirmm.fr  |
> | LIRMM / CNRS - SYSMIC team   |+ 33 4 67 41 86 33
> <+33%204%2067%2041%2086%2033>|
> | Building 4 Office H2.2   |http://walafc0.org|
> +-+
> ___
> gem5-dev mailing list
> gem5-dev@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev
>
___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

Re: [gem5-dev] Review Request 3684: alpha: Remove ALPHA support and supplemental files

[Andreas Hansson]

> On Oct. 25, 2016, 10:13 p.m., Jason Lowe-Power wrote:
> > util/regress, line 45
> > 
> >
> > I think this has been pointed out by Brad in the past, but we need to 
> > keep these tests for other Ruby protocols around. I think it's fine to just 
> > switch them to using x86 instead of Alpha. As far as I know, most Ruby 
> > users are using x86 anyway.
> 
> Andreas Hansson wrote:
> Why X86 and not NULL? I would suggest to let all the ruby testers simply 
> be part of NULL (as suggested in the patch summary). It would be even nicer 
> if we didn't have to compile gem5 for every protocol, but that may be asking 
> too much.
> 
> Jason Lowe-Power wrote:
> There's two components to testing the protocols. First, do they compile, 
> which the NULL ISA would test perfectly well. Second, do they work, which we 
> need to run some applications on the protocol (Linux boot is actually a 
> pretty good application for this).
> 
> I agree that it would be good if Ruby was a library, but I do think it's 
> too much to ask :).

Feel free to add Linux boot to Ruby+X86. Today all we do is "hello" and 
rubytest. For the latter we don't need an ISA, NULL will do just fine (we use 
NULL for all the memtest and traffic-gen tests of the classic memory system). 
Running "hello" seems fairly redundant to me. I would think adding some more 
synthetic tests should be just as good as "hello" if not better. No?


- Andreas


---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3684/#review8981
---


On Oct. 24, 2016, 8:43 p.m., Andreas Hansson wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3684/
> ---
> 
> (Updated Oct. 24, 2016, 8:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11689:e1835e5846b9
> ---
> alpha: Remove ALPHA support and supplemental files
> 
> This patch removes support for ALPHA, and correspondingly also removes
> any devices, tests, supporting functions, and configurations unique to
> ALPHA.
> 
> R.I.P.
> 
> A few things that are worth re-adding using something other than
> ALPHA:
> 
> 1) A two-system regresssion using Ethernet
> 
> 2) Ruby tester regressions using NULL for the variuos Ruby protocols
> 
> 
> Diffs
> -
> 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/drivesys.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/testsys.terminal
>  b3d5f0e9e258 
>   tests/quick/se/0

Re: [gem5-dev] Review Request 3684: alpha: Remove ALPHA support and supplemental files

[Jason Lowe-Power]

> On Oct. 25, 2016, 10:13 p.m., Jason Lowe-Power wrote:
> > util/regress, line 45
> > 
> >
> > I think this has been pointed out by Brad in the past, but we need to 
> > keep these tests for other Ruby protocols around. I think it's fine to just 
> > switch them to using x86 instead of Alpha. As far as I know, most Ruby 
> > users are using x86 anyway.
> 
> Andreas Hansson wrote:
> Why X86 and not NULL? I would suggest to let all the ruby testers simply 
> be part of NULL (as suggested in the patch summary). It would be even nicer 
> if we didn't have to compile gem5 for every protocol, but that may be asking 
> too much.

There's two components to testing the protocols. First, do they compile, which 
the NULL ISA would test perfectly well. Second, do they work, which we need to 
run some applications on the protocol (Linux boot is actually a pretty good 
application for this).

I agree that it would be good if Ruby was a library, but I do think it's too 
much to ask :).


- Jason


---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3684/#review8981
---


On Oct. 24, 2016, 8:43 p.m., Andreas Hansson wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3684/
> ---
> 
> (Updated Oct. 24, 2016, 8:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11689:e1835e5846b9
> ---
> alpha: Remove ALPHA support and supplemental files
> 
> This patch removes support for ALPHA, and correspondingly also removes
> any devices, tests, supporting functions, and configurations unique to
> ALPHA.
> 
> R.I.P.
> 
> A few things that are worth re-adding using something other than
> ALPHA:
> 
> 1) A two-system regresssion using Ethernet
> 
> 2) Ruby tester regressions using NULL for the variuos Ruby protocols
> 
> 
> Diffs
> -
> 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/drivesys.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/testsys.terminal
>  b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simerr b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simout b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/stats.txt b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/config.ini b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/

Re: [gem5-dev] Review Request 3684: alpha: Remove ALPHA support and supplemental files

[Andreas Hansson]

> On Oct. 25, 2016, 10:13 p.m., Jason Lowe-Power wrote:
> > SConstruct, line 421
> > 
> >
> > Clearly X86 should be the default, not ARM! ;)
> > 
> > Joking aside, maybe the default should be the same as the host system? 
> > Or we could remove the default entirely. I didn't even know a default 
> > existed.

It was based on ASCII distance (and the fact that I think it's fair to say that 
ARM is the best supported ISA).


> On Oct. 25, 2016, 10:13 p.m., Jason Lowe-Power wrote:
> > util/regress, line 45
> > 
> >
> > I think this has been pointed out by Brad in the past, but we need to 
> > keep these tests for other Ruby protocols around. I think it's fine to just 
> > switch them to using x86 instead of Alpha. As far as I know, most Ruby 
> > users are using x86 anyway.

Why X86 and not NULL? I would suggest to let all the ruby testers simply be 
part of NULL (as suggested in the patch summary). It would be even nicer if we 
didn't have to compile gem5 for every protocol, but that may be asking too much.


- Andreas


---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3684/#review8981
---


On Oct. 24, 2016, 8:43 p.m., Andreas Hansson wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3684/
> ---
> 
> (Updated Oct. 24, 2016, 8:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11689:e1835e5846b9
> ---
> alpha: Remove ALPHA support and supplemental files
> 
> This patch removes support for ALPHA, and correspondingly also removes
> any devices, tests, supporting functions, and configurations unique to
> ALPHA.
> 
> R.I.P.
> 
> A few things that are worth re-adding using something other than
> ALPHA:
> 
> 1) A two-system regresssion using Ethernet
> 
> 2) Ruby tester regressions using NULL for the variuos Ruby protocols
> 
> 
> Diffs
> -
> 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/drivesys.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/testsys.terminal
>  b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simerr b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simout b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/stats.txt b3d5f0e9e258 
>   tests/quick/se/00

Re: [gem5-dev] Review Request 3684: alpha: Remove ALPHA support and supplemental files

[Jason Lowe-Power]

---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3684/#review8981
---


I'm a little surprised at how much coupling there is between the CPU models and 
the ISAs. I didn't expect this to require so many modifications.

Thanks for putting this together, Andreas, other than a couple of small things 
below it looks good. I'm fully on board with dropping Alpha support.


SConstruct (line 421)


Clearly X86 should be the default, not ARM! ;)

Joking aside, maybe the default should be the same as the host system? Or 
we could remove the default entirely. I didn't even know a default existed.



util/regress 


I think this has been pointed out by Brad in the past, but we need to keep 
these tests for other Ruby protocols around. I think it's fine to just switch 
them to using x86 instead of Alpha. As far as I know, most Ruby users are using 
x86 anyway.


- Jason Lowe-Power


On Oct. 24, 2016, 8:43 p.m., Andreas Hansson wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3684/
> ---
> 
> (Updated Oct. 24, 2016, 8:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11689:e1835e5846b9
> ---
> alpha: Remove ALPHA support and supplemental files
> 
> This patch removes support for ALPHA, and correspondingly also removes
> any devices, tests, supporting functions, and configurations unique to
> ALPHA.
> 
> R.I.P.
> 
> A few things that are worth re-adding using something other than
> ALPHA:
> 
> 1) A two-system regresssion using Ethernet
> 
> 2) Ruby tester regressions using NULL for the variuos Ruby protocols
> 
> 
> Diffs
> -
> 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-atomic/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing-dual/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simerr 
> b3d5f0e9e258 
>   tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/simout 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/stats.txt 
> b3d5f0e9e258 
>   
> tests/quick/fs/10.linux-boot/ref/alpha/linux/tsunami-simple-timing/system.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/config.ini
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/drivesys.terminal
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simerr
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/simout
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/stats.txt
>  b3d5f0e9e258 
>   
> tests/quick/fs/80.netperf-stream/ref/alpha/linux/twosys-tsunami-simple-atomic/testsys.terminal
>  b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/config.ini 
> b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simerr b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/simout b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/minor-timing/stats.txt b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/config.ini b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/simerr b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/simout b3d5f0e9e258 
>   tests/quick/se/00.hello/ref/alpha/linux/o3-timing/stats.t

Re: [gem5-dev] Removal of ALPHA from gem5

[Steve Reinhardt]

I agree with Alex: the ISA description system was designed for Alpha, and
it remains the purest example of how it was intended to be used, so I think
there's some value in keeping it around for that.

To me, it should boil down to a cost/benefit consideration. I agree that
the benefits are not that great any more, but I think the costs are pretty
minimal too, and could be reduced further without abandoning Alpha
altogether. For example, seeing some of the things Brandon has run into
with his Process code restructuring & enhancement, I'm in favor of dropping
Tru64 support. Also, we certainly could get rid of many or all of the
long-running regression tests that aren't adding any value (which is not
even a problem that's unique to Alpha). But it seems overkill to me to get
rid of Alpha entirely, especially since it's such a clean ISA for the most
part.

Now if someone proposed getting rid of an ISA that would let us drop a
microarchitectural complexity like register windows, or branch delay slots,
or predication ;), (or to be fair, microcode!) then the cost side of the
equation might be different, but of course the benefits are more tangible
for those ISAs as well.

Steve


On Tue, Oct 25, 2016 at 9:46 AM Dutu, Alexandru 
wrote:

> Hi Andreas,
>
> Not sure I understand this decision/proposal. Certainly, there are some
> ISAs in the current repo which are not used or maintained by anyone. This
> might render them good candidates for removal. However, ALPHA is quite a
> big exception in my mind.
>
> Surely, very few people are using ALPHA in their research and no one
> maintains it, yet gem5 was developed with ALPHA in mind. There might still
> exist assumptions baked in the current code because of how ALPHA works. I
> addition, I would also argue that ALPHA has a good example of  ISA
> generation code. If not in research, it can be used in educating users
> about gem5.
>
> Therefore, keeping ALPHA around is reasonable to me, it can be helpful in
> refining the gem5 models and finding out bugs.
>
> Best regards,
> Alex
> -Original Message-
> From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Andreas
> Hansson
> Sent: Monday, October 24, 2016 1:50 PM
> To: gem5-dev@gem5.org; gem5-us...@gem5.org
> Subject: [gem5-dev] Removal of ALPHA from gem5
>
> Hi all,
>
> The day has come.
>
> As previously discussed, http://reviews.gem5.org/r/3684/ removes support
> for ALPHA from gem5. Ultimately this has to be a community decision. Thus,
> if anyone is actually relying on ALPHA for their work please let us know
> within the next two weeks.
>
> If there are any questions or concerns, please speak up. Depending on the
> feedback, I aim to push this patch on November 14th.
>
> Kind regards,
>
> Andreas
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> ___
> gem5-dev mailing list
> gem5-dev@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev
> ___
> gem5-dev mailing list
> gem5-dev@gem5.org
> http://m5sim.org/mailman/listinfo/gem5-dev
>
___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

Re: [gem5-dev] Removal of ALPHA from gem5

[Dutu, Alexandru]

Hi Andreas,

Not sure I understand this decision/proposal. Certainly, there are some ISAs in 
the current repo which are not used or maintained by anyone. This might render 
them good candidates for removal. However, ALPHA is quite a big exception in my 
mind.

Surely, very few people are using ALPHA in their research and no one maintains 
it, yet gem5 was developed with ALPHA in mind. There might still exist 
assumptions baked in the current code because of how ALPHA works. I addition, I 
would also argue that ALPHA has a good example of  ISA generation code. If not 
in research, it can be used in educating users about gem5.

Therefore, keeping ALPHA around is reasonable to me, it can be helpful in 
refining the gem5 models and finding out bugs.

Best regards,
Alex
-Original Message-
From: gem5-dev [mailto:gem5-dev-boun...@gem5.org] On Behalf Of Andreas Hansson
Sent: Monday, October 24, 2016 1:50 PM
To: gem5-dev@gem5.org; gem5-us...@gem5.org
Subject: [gem5-dev] Removal of ALPHA from gem5

Hi all,

The day has come.

As previously discussed, http://reviews.gem5.org/r/3684/ removes support for 
ALPHA from gem5. Ultimately this has to be a community decision. Thus, if 
anyone is actually relying on ALPHA for their work please let us know within 
the next two weeks.

If there are any questions or concerns, please speak up. Depending on the 
feedback, I aim to push this patch on November 14th.

Kind regards,

Andreas

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev
___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

[gem5-dev] Base cpu modification

[Pierre-Yves Péneau]

Hi all,

I would like to add a new hardware component in gem5. This component
will be at the same level than L1 caches. I am planning to modify the
base cpu to add a new port and use it to communicate with my component.

Eventually, I would like to share my work with the gem5 community.
Louisa Bessad (from my lab) had a discussion with Gabor Dozsa from ARM
and told me that any modification to the base cpu must be strongly
justified to the developers, and so could be very hard to merge in gem5.

So, my questions are:
- can I do what I want without modifying the base cpu ?
- if not, what are the chances that my work will be accepted ?

Thank you all.

-- 
+-+
| Pierre-Yves Péneau - PhD student |  first.last at lirmm.fr  |
| LIRMM / CNRS - SYSMIC team   |+ 33 4 67 41 86 33|
| Building 4 Office H2.2   |http://walafc0.org|
+-+
___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

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

[Sophiane SENNI]

---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3502/
---

(Updated Oct. 25, 2016, 9:18 a.m.)


Review request for Default.


Repository: gem5


Description (updated)
---

Changeset 11688:74be5cba513a
---
mem: Split the hit_latency into tag_latency and data_latency

If the cache access mode is parallel, i.e. "sequential_access" parameter
is set to "False", tags and data are accessed in parallel. Therefore,
the hit_latency is the maximum latency between tag_latency and
data_latency. On the other hand, if the cache access mode is
sequential, i.e. "sequential_access" parameter is set to "True",
tags and data are accessed sequentially. Therefore, the hit_latency
is the sum of tag_latency plus data_latency.


Diffs (updated)
-

  configs/common/Caches.py 4aac82f10951 
  configs/common/O3_ARM_v7a.py 4aac82f10951 
  configs/example/arm/devices.py 4aac82f10951 
  configs/learning_gem5/part1/caches.py 4aac82f10951 
  src/mem/cache/Cache.py 4aac82f10951 
  src/mem/cache/base.hh 4aac82f10951 
  src/mem/cache/base.cc 4aac82f10951 
  src/mem/cache/tags/Tags.py 4aac82f10951 
  src/mem/cache/tags/base.hh 4aac82f10951 
  src/mem/cache/tags/base.cc 4aac82f10951 
  src/mem/cache/tags/base_set_assoc.hh 4aac82f10951 
  src/mem/cache/tags/fa_lru.hh 4aac82f10951 
  src/mem/cache/tags/fa_lru.cc 4aac82f10951 

Diff: http://reviews.gem5.org/r/3502/diff/


Testing
---

Tested using --Debug-flags=Cache


Thanks,

Sophiane SENNI

___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

Re: [gem5-dev] Review Request 3666: arm, config: added support for ex5 model of big.LITTLE

[Pierre-Yves Péneau]

---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3666/#review8979
---

Ship it!


Ship It!

- Pierre-Yves Péneau


On Oct. 20, 2016, 6:39 p.m., Anastasiia Butko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/3666/
> ---
> 
> (Updated Oct. 20, 2016, 6:39 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Repository: gem5
> 
> 
> Description
> ---
> 
> Changeset 11687:b3946ea8b081
> ---
> arm, config: added support for ex5 model of big.LITTLE
> 
> This patch enables using calibrated big and LITTLE
> cores, ex5_big and ex5_LITTLE instead of the default
> 'arm_detailed' and 'minor' cpus. The ex5 model is based
> on the Samsung Exynos 5 Octa (5422) SoC. Operation and
> memory hierarchy latencies have been calibrated using the
> lmbench micro-benchmark suite. The preliminary validation
> results have been published as:
> 'Full-System Simulation of big.LITTLE Multicore Architecture
> for Performance and Energy Exploration', in International
> Symposium on Embedded Multicore/Many-core Systems-on-Chip
> (MCSoC'16), Lyon, France (Sep, 2016).
> 
> Reported-by: Anastasiia Butko 
> 
> 
> Diffs
> -
> 
>   configs/common/CpuConfig.py 4a86763c0b30 
>   configs/common/ex5_LITTLE.py PRE-CREATION 
>   configs/common/ex5_big.py PRE-CREATION 
>   configs/example/arm/fs_bigLITTLE.py 4a86763c0b30 
> 
> Diff: http://reviews.gem5.org/r/3666/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Anastasiia Butko
> 
>

___
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev

[gem5-dev] Cron /z/m5/regression/do-regression quick

[Cron Daemon]

* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/minor-timing: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-timing: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/o3-timing: passed.
 * build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-atomic: 
passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby: 
passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/minor-timing: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/o3-timing: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/simple-atomic: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing: passed.
* build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby: 
passed.
* build/ALPHA/tests/opt/quick/se/01.hello-2T-smt/alpha/linux/o3-timing-mt: 
passed.
* 
build/ALPHA/tests/opt/quick/se/03.learning-gem5/alpha/linux/learning-gem5-p1-simple:
 passed.
* build/ALPHA/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby: 
passed.* 
build/ALPHA/tests/opt/quick/se/03.learning-gem5/alpha/linux/learning-gem5-p1-two-level:
 passed.
* build/ALPHA/tests/opt/quick/se/30.eon/alpha/tru64/simple-atomic: passed.
* build/ALPHA/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby: 
passed.
* build/ALPHA/tests/opt/quick/se/50.vortex/alpha/tru64/simple-atomic: 
passed.
* build/ALPHA/tests/opt/quick/se/50.vortex/alpha/tru64/simple-timing: 
passed.
* 
build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-atomic: 
passed.
* build/ALPHA/tests/opt/quick/se/70.twolf/alpha/tru64/simple-atomic: passed.
* 
build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-atomic-dual:
 passed.
* 
build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-timing: 
passed.
* build/ALPHA/tests/opt/quick/se/70.twolf/alpha/tru64/simple-timing: passed.
* 
build/ALPHA/tests/opt/quick/fs/10.linux-boot/alpha/linux/tsunami-simple-timing-dual:
 passed.
* 
build/ALPHA/tests/opt/quick/fs/80.netperf-stream/alpha/linux/twosys-tsunami-simple-atomic:
 passed.
* 
build/ALPHA_MOESI_hammer/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer:
 passed.* 
build/ALPHA_MOESI_hammer/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby-MOESI_hammer:
 passed.* 
build/ALPHA_MOESI_hammer/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby-MOESI_hammer:
 passed.
* 
build/ALPHA_MOESI_hammer/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer:
 passed.
* 
build/ALPHA_MESI_Two_Level/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby-MESI_Two_Level:
 passed.
* 
build/ALPHA_MESI_Two_Level/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby-MESI_Two_Level:
 passed.
* 
build/ALPHA_MESI_Two_Level/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby-MESI_Two_Level:
 passed.
 * 
build/ALPHA_MESI_Two_Level/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby-MESI_Two_Level:
 passed.
* 
build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_directory:
 passed.
* 
build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_directory:
 passed.
* 
build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_directory:
 passed.
* 
build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_directory:
 passed.
* 
build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby-MOESI_CMP_token:
 passed.
* 
build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby-MOESI_CMP_token:
 passed.
* 
build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby-MOESI_CMP_token:
 passed.
* 
build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby-MOESI_CMP_token:
 passed.
* build/MIPS/tests/opt/quick/se/00.hello/mips/linux/simple-timing-ruby: 
passed.
* build/MIPS/tests/opt/quick/se/00.hello/mips/linux/simple-timing: passed.
* 
build/MIPS/tests/opt/quick/se/03.learning-gem5/mips/linux/learning-gem5-p1-two-level:
 passed.
* 
build/MIPS/tests/opt/quick/se/03.learning-gem5/mips/linux/learning-gem5-p1-simple:
 passed.
* build/MIPS/tests/opt/quick/se/00.hello/mips/linux/o3-timing: passed.* 
build/MIPS/tests/opt/quick/se/00.hello/mips/linux/simple-atomic: passed.
* build/NULL/tests/opt/quick/se/50.memtest/null/none/memtest: passed.
* build/NULL/tests/opt/quick/se/70.tgen/null/none/tgen-dram-ctrl: passed.
* build/NULL/tests/opt/quick/se/50.memtest/null/none/memtest-filter: passed.
* build/NULL/tests/opt/quick/se/70.tgen/null/none/tgen-simple-mem: passed.
* build/NULL/tests/opt/quick/se/51.memcheck/null/none/memcheck: passed.
* build/POW