[gem5-users] Re: AMD GCN3 - Can't use single CPU - fatal no spare thread context

2020-08-07 Thread Sampad Mohapatra via gem5-users
Thanks Matt. Thats a lot of helpful information. I will investigate further. Virus-free. www.avast.com

[gem5-users] Re: AMD GCN3 - Can't use single CPU - fatal no spare thread context

2020-08-07 Thread Matt Sinclair via gem5-users
I don't know the answer to this, and would need to look just the same as you. My guess is that a) the thread contexts do not necessarily require running on different CPUs and b) after the check I described, the one thread won't be doing anything more after that point, so its effect on subsequent c

[gem5-users] Re: AMD GCN3 - Can't use single CPU - fatal no spare thread context

2020-08-07 Thread Sampad Mohapatra via gem5-users
Hi Matt, Thanks for the clarification. My issue is I need more than 1 cpu. In this scenario what will be the effect of this extra cpu on the coherence traffic, i.e. does it become part of a Core Pair and take part in coherence exchanges ? When I am placing cpus in a garnet topology, how do I igno

[gem5-users] Re: AMD GCN3 - Can't use single CPU - fatal no spare thread context

2020-08-07 Thread Matt Sinclair via gem5-users
Hi Sampad, To literally answer the clone error part: this happens when your application needs multiple thread contexts to run. The failure happens when -n 1 is used because the simulator doesn't have enough thread contexts to fulfill what the application needs. Of course, the next logical questi

[gem5-users] AMD GCN3 - Can't use single CPU - fatal no spare thread context

2020-08-07 Thread Sampad Mohapatra via gem5-users
Hi All, Why does the GCN3 model require at least 2 CPUs ? Every time I use a single CPU, gem5 crashes with the following error: *fatal: clone: no spare thread context in system* In contrast, I was able to run the HSAIL model with a single CPU. Thank You, Sampad Mohapatra

[gem5-users] Re: Reading from memory in Gem5

2020-08-07 Thread ABD ALRHMAN ABO ALKHEEL via gem5-users
Hello Jason, It is for a debug-only read and I want to see what is in the main memory only not in the cache. Thanks for your email, I really appreciate that. From: Jason Lowe-Power Sent: Friday, August 7, 2020 5:52 PM To: ABD ALRHMAN ABO ALKHEEL Cc: gem5 users

[gem5-users] Re: Reading from memory in Gem5

2020-08-07 Thread ABD ALRHMAN ABO ALKHEEL via gem5-users
Hi Jason, Thanks for your email. I am sorry about that, I sent the second email in order to update the first one about reading the memory with 256 bytes size of the data not to make any spamming. Thanks From: Jason Lowe-Power Sent: Friday, August 7, 2020 5:52

[gem5-users] Re: Error only occurs with higher number of clusters and cpus

2020-08-07 Thread Sebastian Block via gem5-users
Thank you very much. I will give Ruby a try.Am Freitag, 7. August 2020, 16:41:12 MESZ hat Ciro Santilli Folgendes geschrieben: #yiv9784044512 P {margin-top:0;margin-bottom:0;}It might be the same as:  https://gem5.atlassian.net/browse/GEM5-711 I want to investigate that soon hopefully

[gem5-users] Re: Reading from memory in Gem5

2020-08-07 Thread Jason Lowe-Power via gem5-users
Hello, Is this a debug-only read or are you trying to simulate the timing for the read? Do you want to see what's in the main memory or do you want to see the up-to-date values in the caches? The answers to these questions will drive what type of access you want to make and what object you want to

[gem5-users] Re: Error only occurs with higher number of clusters and cpus

2020-08-07 Thread Ciro Santilli via gem5-users
It might be the same as: https://gem5.atlassian.net/browse/GEM5-711 I want to investigate that soon hopefully. If you try Ruby and it fails, please open a separate bug, we want it to work as well 🙂 From: Sebastian Block via gem5-users Sent: Friday, August 7, 202

[gem5-users] Error only occurs with higher number of clusters and cpus

2020-08-07 Thread Sebastian Block via gem5-users
Hi all, My gem5 project consists of clusters and some cpus in the clusters, simulating them in fs mode.Simulating in atomic mode always works. While simulating less then 6 cpus works perfectly fine in timing mode, with more then 6 the simulation crashes with the error:  panic: panic conditio