You need to replace [number of workers] with a number such as 1,2,4 etc.
On 4 Mar 2020 Wed at 6:31 PM Abhishek Singh
wrote:
> Hi Hao,
>
> I was able to solve the git error. Thank you for that.
> I followed commands for setting up docker from your tutorial.
> When I enter the command to set
Hi Hao,
I was able to solve the git error. Thank you for that.
I followed commands for setting up docker from your tutorial.
When I enter the command to set "celery" in my database path, I get the
following error:
Error Message:
usage: celery worker [options]
celery: error: unrecognized
Hi Abhishek,
Regarding to the git error, you’ll need to “git commit” the changes in the
git repos that you created.
Using celery is not required, but it is useful to manage a large amount of
gem5art runs. You might find these links helpful,
- What is task/celery?
Hi Hao,
I followed all git commands and I get the following error:
(gem5art-env) abs218@comparchT640:~/gem5art_fs/spec2017-experiments$
python3 launch_spec2017_experiments.py
*fatal: your current branch 'master' does not have any commits yet*Traceback
(most recent call last):
File
Hi,
I do not understand how it will be different, is it anyway using my host
machine library?
When I mount the image, the binaries are present in "/usr" as you mentioned.
Also is this sed command correct? sed -i
"s/\/opt\/rh\/devtoolset-7\/root\/usr/\/usr/g"
Hi Hoa,
I mounted the spec image and found that in file "myconfig.x86.cfg" file
which is used to compile spec benchmarks have this gcc linking to
"/SW/compilers/GCC/Linux/x86_64/gcc-6.3.0"
Did you guys use this "myconfig.x86.cfg" file in the result shown on the "
I mounted the image and there was no SW folder
On Tue, Mar 3, 2020 at 8:42 PM Hoa Nguyen wrote:
> Hi,
>
> I'm not sure where is the error, but I would look into why the path to gcc
> is "/SW/compilers/GCC/Linux/x86_64/gcc-6.3.0/bin/gcc".
>
> Regards,
> Hoa Nguyen
>
> On Tue, Mar 3, 2020, 5:28
Hi,
I'm not sure where is the error, but I would look into why the path to gcc
is "/SW/compilers/GCC/Linux/x86_64/gcc-6.3.0/bin/gcc".
Regards,
Hoa Nguyen
On Tue, Mar 3, 2020, 5:28 PM Abhishek Singh
wrote:
> Hi Hoa,
>
> For now, I will try to get a single-core.
>
> In Building the Disk Image
Hi Hoa,
For now, I will try to get a single-core.
In Building the Disk Image Step, I get an error in compiling spec
benchmarks in the image i.e., after this command ./packer build
spec2017/spec2017.json
I have posted the long error message, I also looked into most of the
make.out the file, the
Hi Abhishek,
Yes, but the gem5 config only has one-core O3CPU. It could be tweaked to
multiple cores.
Regards,
Hoa Nguyen
On Tue, Mar 3, 2020, 3:48 PM Abhishek Singh
wrote:
> Hi,
>
> In order to run SPEC2k17 benchmarks, should we follow the same tutorial "
>
Hi,
In order to run SPEC2k17 benchmarks, should we follow the same tutorial "
https://gem5art.readthedocs.io/en/latest/tutorials/spec2017-tutorial.html;?
Best regards,
Abhishek
On Tue, Mar 3, 2020 at 6:45 PM Hoa Nguyen wrote:
> Hi Abhishek,
>
> We ran a few spec2017 workloads on O3CPU, and
Hi Abhishek,
We ran a few spec2017 workloads on O3CPU, and they ran successfully.
We used gem5 19.
Regards,
Hoa Nguyen
On 3/3/20, Abhishek Singh wrote:
> Hi Hoa,
> Are you able to run on o3 cpu.
> Also, is it same gem5 commit as mentioned on the website?
>
> On Tue, Mar 3, 2020 at 4:35 AM Hoa
Hi Hoa,
Are you able to run on o3 cpu.
Also, is it same gem5 commit as mentioned on the website?
On Tue, Mar 3, 2020 at 4:35 AM Hoa Nguyen wrote:
> Hi there,
>
> We're actually able to run SPEC 2017 workloads in FS mode using the
> gem5art's tutorial.
>
> The table should have been updated.
>
>
Hi there,
We're actually able to run SPEC 2017 workloads in FS mode using the
gem5art's tutorial.
The table should have been updated.
Sorry about the confusion!
Regards,
Hoa Nguyen
On Mon, Mar 2, 2020, 7:55 PM Abhishek Singh
wrote:
> Hi,
>
> This is the i got in past when I was trying to
Hi,
This is the i got in past when I was trying to run SPEC in SE mode
If you check mailing list there are suggestions about it
I have not yet ported the spec 2017 to gem5, I was trying to use FS but
then I saw that 03 CPU in gem5art shows unsuccessful
I am planning to port spec benchmarks in
15 matches
Mail list logo
