[gem5-users] Re: Help: "Error: Can't find a working Python installation"

[李明轩 via gem5-users]

Hi! Thanks for your detailed reply and advice! I’ve tried to switch to 
`develop` branch and successfully compile it. Thanks a lot!

Best regards,
Siris Li.

> 2023年6月21日 04:26，Richard Cooper via gem5-users  写道：
> 
> Hello,

> Until then, you could either:
>  
> 1) Use the `develop` branch of gem5 
>  
>  
> I hope one of these options fixes your problem!
>  
> Best regards,
>  
> Richard.
>  

___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: Help: "Error: Can't find a working Python installation"

[Richard Cooper via gem5-users]

Hello,

The default python-config probably picks up your default Python installation 
(3.11) even if you choose a different Python version to invoke scons.
You could check this by running python-config and checking which link options 
it produces.

As Gabriel mentioned, Python 3.11 isn’t supported in the stable release of gem5 
yet – full support will be added in the upcoming gem5 v23.0 release.

Until then, you could either:

1) Use the `develop` branch of gem5

2) Make sure you are using the correct `python-config`. It looks like you 
should be able to set this with an environment variable before running scons:

`export PYTHON_CONFIG=python3.10-config`

3) You could alternatively find where the list of possible `python-config`s is 
defined (`site_scons/gem5_scons/defaults.py`) and add e.g. `python3.10-config` 
at a higher priority.

4) Cherry pick the following three patches onto gem5 v22.1:

https://gem5-review.googlesource.com/c/public/gem5/+/70237
https://gem5-review.googlesource.com/c/public/gem5/+/68818
https://gem5-review.googlesource.com/c/public/gem5/+/68817

There is more information in this thread:
https://www.mail-archive.com/gem5-users@gem5.org/msg21505.html

I hope one of these options fixes your problem!

Best regards,

Richard.



From: 李明轩 via gem5-users 
Sent: Tuesday, June 20, 2023 8:41 PM
To: gem5-users@gem5.org
Cc: 李明轩 <212...@stu.pku.edu.cn>
Subject: [gem5-users] Re: Help: "Error: Can't find a working Python 
installation"

Hello, I’ve looked through the web you provided and tried python 3.8.17, python 
3.9.17, python 3.10.12. None of them solved my problem, the terminal still 
outputs "Error: Can't find a working Python installation”.


Hi,

With the current latest version of gem5, you must use python <= 3.10. Python 
3.11 will be supported in the next release of gem5 coming very soon.

For details: https://gem5.atlassian.net/browse/GEM5-1295

Regards,

Gabriel
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to 
gem5-users-le...@gem5.org

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-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: Help: "Error: Can't find a working Python installation"

[李明轩 via gem5-users]

Hello, I’ve looked through the web you provided and tried python 3.8.17, python 
3.9.17, python 3.10.12. None of them solved my problem, the terminal still 
outputs "Error: Can't find a working Python installation”.

> Hi,
> With the current latest version of gem5, you must use python <= 3.10. Python 
> 3.11 will be supported in the next release of gem5 coming very soon.
> 
> For details: https://gem5.atlassian.net/browse/GEM5-1295
> 
> Regards,
> 
> Gabriel
> 
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org

___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

[Matt Sinclair via gem5-users]

Right, the error you got with HeteroSync is because the generation of GPU
the Makefile compiled for (gfxXXX) was not the same as the version the
simulation supported.  Since you were using GCN3 you would need to compile
for gfx801 (APU) or gfx803 (dGPU) depending on what if you are trying to
run a tightly coupled or discrete GPU experiment.  It looks like you were
running APU based on what was in your command line, for what it’s worth.

There is not a docker setup for FS mode in the same way there is for SE
mode, but there is this:
https://www.gem5.org/2023/02/13/moving-to-full-system-gpu.html

Matt

On Tue, Jun 20, 2023 at 2:18 PM Anoop Mysore via gem5-users <
gem5-users@gem5.org> wrote:

> Wrong build; it works when built for gfx-8 (per readme)
> $ make release-gfx8
> in heterosync directory.
>
> On Tue, Jun 20, 2023, 6:26 PM Anoop Mysore  wrote:
>
>> Oh I see, that makes sense; I was on ROCm 5.1.0.
>> I am now running on docker and the square test works as expected.
>> I don't see a ready-made config for full system emulation with gcn3 -- is
>> that available someplace else or should I figure out how to build one? I
>> think I need that because when I try and run the heterosync benchmark
>> (through docker), I see the following:
>> ```
>> /HIP/rocclr/hip_code_object.cpp:120: guarantee(false &&
>> "hipErrorNoBinaryForGpu: Coudn't find binary for current devices!")
>> build/GCN3_X86/sim/faults.cc:60: panic: panic condition !FullSystem
>> occurred: fault (General-Protection) detected @ PC
>> (0x76afa941=>0x76afa942).(0=>1)
>> Memory Usage: 2502568 KBytes
>> Program aborted at tick 7278973
>> ```
>> Is this expected as I'm running SE mode?
>>
>>> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
>
-- 
Regards,
Matt Sinclair
Assistant Professor
University of Wisconsin-Madison
Computer Sciences Department
cs.wisc.edu/~sinclair
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: Simple Switchable Processor with checkpoint restoration

[Ayaz Akram via gem5-users]

Hi Abdal,

Assuming that you run into this problem when using different start and
switch core types for SimpleSwitchable processor in your script, I think
the main problem is that on restore the start core type is not the same as
the core with which you took the checkpoint (which I am assuming was the
switch core type, let me know if that is not the case). I think you can
restore your checkpoint using SimpleProcessor as well. However, in that
case if you want to switch again after restoring you would not be able to
do so. Another solution/option is to create a new class that inherits from
SimpleSwitchableProcessor in which you just swap the start and switch keys,
for example some thing like following:

self._start_key = "switch"
self._switch_key = "start"


And then use this new processor type in your restore script. This way
you will restore with the correct CPU type and if you want to switch
to a different CPU type you can do that as well.

-Ayaz


On Mon, Jun 19, 2023 at 11:45 AM AbdelQader AlKilany via gem5-users <
gem5-users@gem5.org> wrote:

> Hello gem5 users,
>
>
>
>
>
> I was having some trouble trying to restore a simulation from a checkpoint
> when using a stdlib switchable processor (SimpleSwitchableProcessor).
>
>
>
> When I would attempt to run a simulation like this the simulation would
> freeze up and not restore the checkpoint at all.
>
>
>
> I was wondering whether this functionality had been implemented yet or
> whether there was another way to achieve this using by adding to one of the
> processor or configuration scripts.
>
>
>
> The only difference I could find between SwitchableProcessor and
> SimpleProcessor (which restored checkpoints fine) was that the former
> inherits directly from AbstractProcessor and the latter inherits from
> BaseCPUProcessor so I thought some functionality may have been added to
> BaseCPUProcessor which wasn’t available in AbstractProcessor alone.
>
>
>
> Thank you for any help! 
>
>
>
> Kind Regards,
>
> Abdal
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

[Anoop Mysore via gem5-users]

Wrong build; it works when built for gfx-8 (per readme)
$ make release-gfx8
in heterosync directory.

On Tue, Jun 20, 2023, 6:26 PM Anoop Mysore  wrote:

> Oh I see, that makes sense; I was on ROCm 5.1.0.
> I am now running on docker and the square test works as expected.
> I don't see a ready-made config for full system emulation with gcn3 -- is
> that available someplace else or should I figure out how to build one? I
> think I need that because when I try and run the heterosync benchmark
> (through docker), I see the following:
> ```
> /HIP/rocclr/hip_code_object.cpp:120: guarantee(false &&
> "hipErrorNoBinaryForGpu: Coudn't find binary for current devices!")
> build/GCN3_X86/sim/faults.cc:60: panic: panic condition !FullSystem
> occurred: fault (General-Protection) detected @ PC
> (0x76afa941=>0x76afa942).(0=>1)
> Memory Usage: 2502568 KBytes
> Program aborted at tick 7278973
> ```
> Is this expected as I'm running SE mode?
>
>>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: Help: "Error: Can't find a working Python installation"

[gabriel.busnot--- via gem5-users]

Hi,

With the current latest version of gem5, you must use python <= 3.10. Python 
3.11 will be supported in the next release of gem5 coming very soon.

For details: https://gem5.atlassian.net/browse/GEM5-1295

Regards,

Gabriel
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

[Anoop Mysore via gem5-users]

Oh I see, that makes sense; I was on ROCm 5.1.0.
I am now running on docker and the square test works as expected.
I don't see a ready-made config for full system emulation with gcn3 -- is
that available someplace else or should I figure out how to build one? I
think I need that because when I try and run the heterosync benchmark
(through docker), I see the following:
```
/HIP/rocclr/hip_code_object.cpp:120: guarantee(false &&
"hipErrorNoBinaryForGpu: Coudn't find binary for current devices!")
build/GCN3_X86/sim/faults.cc:60: panic: panic condition !FullSystem
occurred: fault (General-Protection) detected @ PC
(0x76afa941=>0x76afa942).(0=>1)
Memory Usage: 2502568 KBytes
Program aborted at tick 7278973
```
Is this expected as I'm running SE mode?

>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Help: "Error: Can't find a working Python installation"

[李明轩 via gem5-users]

I follow the instructions on gem5 website and try to compile using command 
`scons build/X86/gem5.opt -j 4`.
However, it shows such error: "Error: Can't find a working Python installation”.

My environment is M2 MacBook Air, gem5 v22.1.0.0.
I’m sure that I have already installed Python 3.11.4 on my machine.
When I type `which python` in my zsh, it shows 
`/opt/homebrew/opt/python@3.11/libexec/bin/python`.
When I type `which python-config`, it shows 
`/opt/homebrew/opt/python@3.11/libexec/bin/python-config`.

I have searched the web and tried to add `PYTHON_CONFIG=`, 
but it doesn’t work.
I have no idea why `scons` can’t find my Python.___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: simulate a multi-core processor with Gem5

[Jason Lowe-Power via gem5-users]

Hello,

You may also find the "Learning gem5" documentation
https://www.gem5.org/documentation/learning_gem5/introduction/ and the
bootcamp videos
https://www.youtube.com/playlist?list=PL_hVbFs_loVSaSDPr1RJXP5RRFWjBMqq3
useful.

Cheers,
Jason

On Tue, Jun 20, 2023 at 10:49 AM Eliot Moss via gem5-users <
gem5-users@gem5.org> wrote:

> On 6/20/2023 10:41 AM, 中国石油大学张天 via gem5-users wrote:
> > How to simulate a multi-core processor with Gem5, such as how to write
> configuration files? For
> > example, in the following form:
>
> You don't write config files.  You write python code that creates
> instances of python classes.  The gem5 system will instantiate the
> corresponding C++ classes and connect everything together as the
> python objects indicate.
>
> Regards - EM
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: About Risc-V custom ISA

[Jason Lowe-Power via gem5-users]

Hello,

I believe you would have to modify your compiler to emit the instruction to
avoid using embedded assembly.

Cheers,
Jason

On Tue, Jun 20, 2023 at 10:36 AM 中国石油大学张天 via gem5-users <
gem5-users@gem5.org> wrote:

> When I have customized a RISC-V instruction, I want to know how to make
> the load program execute it naturally, without using embedded assembly? At
> present, I only know how to use embedded assembly to force this custom
> instruction to run.
> ___
> gem5-users mailing list -- gem5-users@gem5.org
> To unsubscribe send an email to gem5-users-le...@gem5.org
>
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: simulate a multi-core processor with Gem5

[Eliot Moss via gem5-users]

On 6/20/2023 10:41 AM, 中国石油大学张天 via gem5-users wrote:
How to simulate a multi-core processor with Gem5, such as how to write configuration files? For 
example, in the following form:


You don't write config files.  You write python code that creates
instances of python classes.  The gem5 system will instantiate the
corresponding C++ classes and connect everything together as the
python objects indicate.

Regards - EM
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] simulate a multi-core processor with Gem5

[中国石油大学张天 via gem5-users]

How to simulate a multi-core processor with Gem5, such as how to write 
configuration files? For example, in the following form:___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] About Risc-V custom ISA

[中国石油大学张天 via gem5-users]

When I have customized a RISC-V instruction, I want to know how to make the 
load program execute it naturally, without using embedded assembly? At present, 
I only know how to use embedded assembly to force this custom instruction to 
run.___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

[gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

[Poremba, Matthew via gem5-users]

[AMD Official Use Only - General]

Hi,


SE mode supports ROCm 4.0 only.  What version of ROCm is installed on the host 
machine?  If they are different the IOCTLs might be as well.

You can alternately try full system with GPU if you want to avoid docker.


-Matt

From: Anoop Mysore via gem5-users 
Sent: Tuesday, June 20, 2023 2:35 AM
To: gem5-users@gem5.org
Cc: Anoop Mysore 
Subject: [gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

Caution: This message originated from an External Source. Use proper caution 
when opening attachments, clicking links, or responding.

Log:
___
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version 22.1.0.0
gem5 compiled Jun 19 2023 11:00:56
gem5 started Jun 20 2023 11:14:53
gem5 executing on a, pid 7265
command line: ../../../../gem5/build/GCN3_X86/gem5.opt 
../../../../gem5/configs/example/apu_se.py -n 4 -c bin/square

Num SQC =  1 Num scalar caches =  1 Num CU =  4
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away from 
using this function.
Global frequency set at 1 ticks per second
warn: system.ruby.network adopting orphan SimObject param 'ext_links'
warn: system.ruby.network adopting orphan SimObject param 'int_links'
warn: No dot file generated. Please install pydot to generate the dot file and 
pdf.
build/GCN3_X86/mem/dram_interface.cc:690: warn: DRAM device capacity (8192 
Mbytes) does not match the address range assigned (512 Mbytes)
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not divide 
range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not divide 
range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not divide 
range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not divide 
range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not divide 
range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does not 
divide range [1:1.6e+06] into equal-sized buckets. Rounding up.

[gem5-users] Re: bad ioctl error in gpu_comput_driver.cc

[Anoop Mysore via gem5-users]

Log:
___
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version 22.1.0.0
gem5 compiled Jun 19 2023 11:00:56
gem5 started Jun 20 2023 11:14:53
gem5 executing on a, pid 7265
command line: ../../../../gem5/build/GCN3_X86/gem5.opt
../../../../gem5/configs/example/apu_se.py -n 4 -c bin/square

Num SQC =  1 Num scalar caches =  1 Num CU =  4
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
warn: The `get_runtime_isa` function is deprecated. Please migrate away
from using this function.
Global frequency set at 1 ticks per second
warn: system.ruby.network adopting orphan SimObject param 'ext_links'
warn: system.ruby.network adopting orphan SimObject param 'int_links'
warn: No dot file generated. Please install pydot to generate the dot file
and pdf.
build/GCN3_X86/mem/dram_interface.cc:690: warn: DRAM device capacity (8192
Mbytes) does not match the address range assigned (512 Mbytes)
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not
divide range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not
divide range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not
divide range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (5) does not
divide range [1:75] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:10] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (2) does not
divide range [1:64] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/statistics.hh:280: warn: One of the stats is a legacy
stat. Legacy stat is a stat that does not belong to any statistics::Group.
Legacy stat is deprecated.
build/GCN3_X86/base/stats/storage.hh:279: warn: Bucket size (1) does
not divide range [1:1.6e+06] into equal-sized buckets. Rounding up.
build/GCN3_X86/base/stats/storage.hh:279: 

[gem5-users] bad ioctl error in gpu_comput_driver.cc

[Anoop Mysore via gem5-users]

I built gem5-gcn3 following:
https://www.gem5.org/documentation/general_docs/gpu_models/GCN3


I am currently trying the square test:
https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/gpu/square/


I was unable to run in docker; so I'm running on my host machine.

When I run the following (for the square binary)
gem5.opt apu_se.py -n 3 -c bin/square,
I see at some point:
build/GCN3_X86/gpu-compute/gpu_compute_driver.cc:926: fatal: 3223866242:
bad ioctl %

gem5: v22.1.0.0
gem5-resources: v22.0.0.2

Is this an error with the simulated driver in gem5? Or am I doing something
wrong? This also happens with other binaries I tried from
gem5-resources/src/gpu/...
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org