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 <abhishek.singh199...@gmail.com> 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 Nguyen <hoangu...@ucdavis.edu> 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.
>>
>> Sorry about the confusion!
>>
>> Regards,
>> Hoa Nguyen
>>
>>
>> On Mon, Mar 2, 2020, 7:55 PM Abhishek Singh <
>> abhishek.singh199...@gmail.com> wrote:
>>
>>> 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 coming weeks
>>>
>>> If you or ANYONE have already posted SPEC 2017 benchmarks for O3CPU
>>> please share your knowledge and steps ?
>>>
>>> On Mon, Mar 2, 2020 at 10:50 PM 616653241 <616653...@qq.com> wrote:
>>>
>>>> Hi Abhishek ,
>>>>           I am running the spec 2017 in the gem5 simulator(X86). But a
>>>> lot of benchmarks didnt works.
>>>>           It shown tha :
>>>>           warn:instruction 'movntdq_Mo_Vo' unimplemented.
>>>>            So,what I do for it?
>>>>      And anyone can tell me how to deal with it? Thank you.
>>>>
>>>> ------------------ 原始邮件 ------------------
>>>> *发件人:* "Abhishek Singh"<abhishek.singh199...@gmail.com>;
>>>> *发送时间:* 2020年3月3日(星期二) 凌晨5:09
>>>> *收件人:* "gem5 users mailing list"<gem5-users@gem5.org>;"yazakram"<
>>>> yazak...@ucdavis.edu>;
>>>> *主题:* Re: [gem5-users] Installing Shared Libraries to Image in Full
>>>> Simulation
>>>>
>>>> Hi Ayaz,
>>>>
>>>> I am using gem5art to get spec 2017 installed in the image.
>>>> I am at this "Building the Disk Image" step
>>>> When I use this command "./packer build spec2017/spec2017.json"
>>>> I get the following error:
>>>>
>>>> qemu output will be in this color.
>>>>
>>>> ==> qemu: Retrieving ISO
>>>> ==> qemu: Trying
>>>> http://old-releases.ubuntu.com/releases/18.04.2/ubuntu-18.04.2-server-amd64.iso
>>>> ==> qemu: Trying
>>>> http://old-releases.ubuntu.com/releases/18.04.2/ubuntu-18.04.2-server-amd64.iso?checksum=md5%3A34416ff83179728d54583bf3f18d42d2
>>>> ==> qemu:
>>>> http://old-releases.ubuntu.com/releases/18.04.2/ubuntu-18.04.2-server-amd64.iso?checksum=md5%3A34416ff83179728d54583bf3f18d42d2
>>>> =>
>>>> /home/abs218/spec2017-experiments/disk-image/packer_cache/8ecbb06d2a38105b7d1cb3316cf5b970ee389dad.iso
>>>> ==> qemu: Creating floppy disk...
>>>>     qemu: Copying files flatly from floppy_files
>>>>     qemu: Copying file: shared/preseed.cfg
>>>>     qemu: Done copying files from floppy_files
>>>>     qemu: Collecting paths from floppy_dirs
>>>>     qemu: Resulting paths from floppy_dirs : []
>>>>     qemu: Done copying paths from floppy_dirs
>>>> ==> qemu: Creating required virtual machine disks
>>>> ==> qemu: Starting HTTP server on port 8208
>>>> ==> qemu: Found port for communicator (SSH, WinRM, etc): 4049.
>>>> ==> qemu: Looking for available port between 5900 and 6000 on 127.0.0.1
>>>> ==> qemu: Starting VM, booting from CD-ROM
>>>>     qemu: The VM will be run headless, without a GUI. If you want to
>>>>     qemu: view the screen of the VM, connect via VNC without a password
>>>> to
>>>>     qemu: vnc://127.0.0.1:5993
>>>> ==> qemu: Overriding defaults Qemu arguments with QemuArgs...
>>>> ==> qemu: Error launching VM: Qemu failed to start. Please run with
>>>> PACKER_LOG=1 to get more info.
>>>> ==> qemu: Deleting output directory...
>>>>
>>>>
>>>>
>>>> *Build 'qemu' errored: Build was halted.==> Some builds didn't complete
>>>> successfully and had errors:--> qemu: Build was halted.*
>>>>
>>>> Please note I am doing ssh into the machine and I ssh using "ssh -Y"
>>>> for
>>>> getting x11 display.
>>>>
>>>> I am not able to bypass this error, do you have any tips how to
>>>> overcome
>>>> this error?
>>>>
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Abhishek
>>>>
>>>>
>>>> On Sat, Feb 8, 2020 at 5:42 PM Ayaz Akram <yazak...@ucdavis.edu> wrote:
>>>>
>>>>> Hi  Abhishek,
>>>>>
>>>>> That was at least the case with the gem5 version we tested (commit:
>>>>> d40f0bc579fb8b10da7181). Please, note that this is the status of linux
>>>>> boot. I am not sure if this status will change with the latest gem5
>>>>> source.
>>>>> One thing that might work for you is to boot linux kernel with KVM cpu
>>>>> and
>>>>> then switch to O3 to run your applications (which may or may not
>>>>> work).
>>>>> However, I am not sure that how much can you rely on those results as
>>>>> inability to boot linux kernel with O3 clearly shows there exist some
>>>>> bugs
>>>>> in gem5. We need to figure out those issues and fix them.
>>>>>
>>>>> Regards,
>>>>> Ayaz
>>>>>
>>>>> On Sat, Feb 8, 2020 at 9:30 AM Abhishek Singh <
>>>>> abhishek.singh199...@gmail.com> wrote:
>>>>>
>>>>>> Hi Ayaz,
>>>>>>
>>>>>> Thanks for providing the image and kernel, I see on gem5art test
>>>>>> results that the image can support at the most only one cpu for O3CPU
>>>>>> model.
>>>>>> Is that still the case ?
>>>>>> I wanted to use this image for running multithreaded applications on
>>>>>> x86 O3CPU FS mode.
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 4, 2020 at 4:12 PM Ayaz Akram <yazak...@ucdavis.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Muhammet,
>>>>>>>
>>>>>>> This is the expected behavior. Basically, this disk image correspond
>>>>>>> to this tutorial:
>>>>>>>
>>>>>>> https://gem5art.readthedocs.io/en/latest/tutorials/boot-tutorial.html
>>>>>>>
>>>>>>>
>>>>>>> and if you go through the disk creation process in that tutorial,
>>>>>>> you
>>>>>>> will realize that there is a post installation script that runs on
>>>>>>> the disk
>>>>>>> image after its creation (
>>>>>>> https://github.com/darchr/gem5art/blob/master/docs/disks/boot-exit/post-installation.sh).
>>>>>>> In that script, the contents of exit.sh (
>>>>>>> https://github.com/darchr/gem5art/blob/master/docs/disks/boot-exit/exit.sh)
>>>>>>> which are written to /root/.bashrc are responsible for exiting the
>>>>>>> simulation as soon as linux is booted.
>>>>>>>
>>>>>>> One thing you can do to avoid exiting the simulation after linux is
>>>>>>> booted is modify the  /root/.bashrc in your disk (after mounting it
>>>>>>> on your
>>>>>>> file system.) Or you can modify the post-installation.sh and create a
>>>>>>> new
>>>>>>> disk image. Another thing you can do is modify your fs.py to call
>>>>>>> m5.simulate() again when simulation terminates the first time
>>>>>>> (following
>>>>>>> the m5 exit call from .bashrc).
>>>>>>>
>>>>>>> Hope this helps.
>>>>>>>
>>>>>>>   -Ayaz
>>>>>>>
>>>>>>> On Tue, Feb 4, 2020 at 5:41 AM Muhammet Abdullah Soytürk <
>>>>>>> muhammetabdullahsoyt...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Ayaz,
>>>>>>>>
>>>>>>>> I have been trying to run a full system simulation with the image
>>>>>>>> and kernel you provided (
>>>>>>>> https://www.mail-archive.com/gem5-users@gem5.org/msg17274.html )
>>>>>>>> but I could not succeed it so far. When I run it with fs.py
>>>>>>>> (build/X86/gem5.opt configs/example/fs.py
>>>>>>>> --disk-image=/home/muhammet/Desktop/gem5/base.img
>>>>>>>> --kernel=/home/muhammet/Desktop/gem5/vmlinux-4.14.134), I get the
>>>>>>>> following
>>>>>>>> output after "Welcome to Ubuntu 18.04.2 LTS!" message and it
>>>>>>>> automatically
>>>>>>>> quits:
>>>>>>>>
>>>>>>>> systemd[1]: Set hostname to <gem5-host>.
>>>>>>>> systemd[1]: File /lib/systemd/system/systemd-journald.service:36
>>>>>>>> configures an IP firewall (IPAddressDeny=any), but the local system
>>>>>>>> does
>>>>>>>> not support BPF/cgroup based firewalling.
>>>>>>>> systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning
>>>>>>>> is only shown for the first loaded unit using IP firewalling.)
>>>>>>>> systemd[1]: Configuration file
>>>>>>>> /lib/systemd/system/serial-getty@.service
>>>>>>>> is marked executable. Please remove executable permission bits.
>>>>>>>> Proceeding
>>>>>>>> anyway.
>>>>>>>> random: systemd: uninitialized urandom read (16 bytes read)
>>>>>>>> systemd[1]: Reached target Remote File Systems.
>>>>>>>> [  OK  ] Reached target Remote File Systems.
>>>>>>>> random: systemd: uninitialized urandom read (16 bytes read)
>>>>>>>> systemd[1]: Created slice User and Session Slice.
>>>>>>>> [  OK  ] Created slice User and Session Slice.
>>>>>>>> random: systemd: uninitialized urandom read (16 bytes read)
>>>>>>>> systemd[1]: Reached target User and Group Name Lookups.
>>>>>>>> [  OK  ] Reached target User and Group Name Lookups.
>>>>>>>> systemd[1]: Created slice System Slice.
>>>>>>>> [  OK  ] Created slice System Slice.
>>>>>>>> [  OK  ] Listening on Journal Socket (/dev/log).
>>>>>>>> [  OK  ] Listening on fsck to fsckd communication Socket.
>>>>>>>> [  OK  ] Listening on Journal Audit Socket.
>>>>>>>> [  OK  ] Listening on udev Control Socket.
>>>>>>>> [  OK  ] Reached target Slices.
>>>>>>>> [  OK  ] Listening on udev Kernel Socket.
>>>>>>>> [  OK  ] Started Forward Password Requests to Wall Directory Watch.
>>>>>>>> [  OK  ] Created slice system-serial\x2dgetty.slice.
>>>>>>>> [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
>>>>>>>> [  OK  ] Listening on Syslog Socket.
>>>>>>>> [  OK  ] Listening on Journal Socket.
>>>>>>>>          Mounting Huge Pages File System...
>>>>>>>>          Starting Load Kernel Modules...
>>>>>>>> [  OK  ] Started Read required files in advance.
>>>>>>>>          Mounting POSIX Message Queue File System...
>>>>>>>>          Starting Journal Service...
>>>>>>>>          Starting Set the console keyboard layout...
>>>>>>>>          Mounting Kernel Debug File System...
>>>>>>>>          Starting Uncomplicated firewall...
>>>>>>>>          Starting udev Coldplug all Devices...
>>>>>>>>          Starting Remount Root and Kernel File Systems...
>>>>>>>>          Starting Create Static Device Nodes in /dev...
>>>>>>>> [  OK  ] Mounted Huge Pages File System.
>>>>>>>> [  OK  ] Mounted POSIX Message Queue File System.
>>>>>>>> [  OK  ] Mounted Kernel Debug File System.
>>>>>>>> [  OK  ] Started Uncomplicated firewall.
>>>>>>>> [  OK  ] Started Set the console keyboard layout.
>>>>>>>> [  OK  ] Started Load Kernel Modules.
>>>>>>>>          Mounting Kernel Configuration File System...
>>>>>>>>          Mounting FUSE Control File System...
>>>>>>>>          Starting Apply Kernel Variables...
>>>>>>>> [  OK  ] Mounted Kernel Configuration File System.
>>>>>>>> [  OK  ] Started Create Static Device Nodes in /dev.
>>>>>>>> [  OK  ] Mounted FUSE Control File System.
>>>>>>>> [  OK  ] Started Journal Service.
>>>>>>>> [  OK  ] Started Apply Kernel Variables.
>>>>>>>> [  OK  ] Started Remount Root and Kernel File Systems.
>>>>>>>>          Starting Flush Journal to Persistent Storage...
>>>>>>>>          Starting udev Kernel Device Manager...
>>>>>>>> [  OK  ] Reached target Local File Systems (Pre).
>>>>>>>>          Starting Load/Save Random Seed...
>>>>>>>>          Activating swap /swapfile...
>>>>>>>> [  OK  ] Reached target Local File Systems.
>>>>>>>>          Starting Set console font and keymap...
>>>>>>>>          Starting Tell Plymouth To Write Out Runtime Data...
>>>>>>>> [  OK  ] Started Load/Save Random Seed.
>>>>>>>> [  OK  ] Started udev Kernel Device Manager.
>>>>>>>>          Starting Network Service...
>>>>>>>> [  OK  ] Started Set console font and keymap.
>>>>>>>> [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
>>>>>>>> [  OK  ] Started Flush Journal to Persistent Storage.
>>>>>>>>          Starting Create Volatile Files and Directories...
>>>>>>>> [  OK  ] Started udev Coldplug all Devices.
>>>>>>>> [  OK  ] Started Dispatch Password Requests to Console Directory
>>>>>>>> Watch.
>>>>>>>> [  OK  ] Reached target Local Encrypted Volumes.
>>>>>>>> [  OK  ] Reached target Paths.
>>>>>>>> [  OK  ] Found device /dev/ttyS0.
>>>>>>>> [  OK  ] Started Network Service.
>>>>>>>> [  OK  ] Started Create Volatile Files and Directories.
>>>>>>>> [  OK  ] Activated swap /swapfile.
>>>>>>>> [  OK  ] Reached target Swap.
>>>>>>>>          Starting Update UTMP about System Boot/Shutdown...
>>>>>>>>          Starting Network Time Synchronization...
>>>>>>>>          Starting Network Name Resolution...
>>>>>>>> [  OK  ] Started Update UTMP about System Boot/Shutdown.
>>>>>>>> [  OK  ] Started Network Name Resolution.
>>>>>>>> [  OK  ] Reached target Host and Network Name Lookups.
>>>>>>>> [  OK  ] Reached target Network.
>>>>>>>> [  OK  ] Started Network Time Synchronization.
>>>>>>>> [  OK  ] Reached target System Initialization.
>>>>>>>> [  OK  ] Listening on UUID daemon activation socket.
>>>>>>>> [  OK  ] Started Message of the Day.
>>>>>>>> [  OK  ] Listening on D-Bus System Message Bus Socket.
>>>>>>>> [  OK  ] Reached target Sockets.
>>>>>>>> [  OK  ] Reached target Basic System.
>>>>>>>>          Starting OpenBSD Secure Shell server...
>>>>>>>> [  OK  ] Started Set the CPU Frequency Scaling governor.
>>>>>>>>          Starting System Logging Service...
>>>>>>>>          Starting Permit User Sessions...
>>>>>>>> [  OK  ] Started D-Bus System Message Bus.
>>>>>>>>          Starting Login Service...
>>>>>>>> [  OK  ] Started irqbalance daemon.
>>>>>>>>          Starting Dispatcher daemon for systemd-networkd...
>>>>>>>> [  OK  ] Started Daily Cleanup of Temporary Directories.
>>>>>>>> [  OK  ] Started Regular background program processing daemon.
>>>>>>>>          Starting Accounts Service...
>>>>>>>>          Starting LSB: Record successful boot for GRUB...
>>>>>>>> [  OK  ] Reached target System Time Synchronized.
>>>>>>>> [  OK  ] Started Daily apt download activities.
>>>>>>>> [  OK  ] Started Daily apt upgrade and clean activities.
>>>>>>>> [  OK  ] Started Discard unused blocks once a week.
>>>>>>>> [  OK  ] Reached target Timers.
>>>>>>>> [  OK  ] Started System Logging Service.
>>>>>>>> [  OK  ] Started Permit User Sessions.
>>>>>>>>          Starting Terminate Plymouth Boot Screen...
>>>>>>>>          Starting Hold until boot process finishes up...
>>>>>>>> [  OK  ] Started Hold until boot process finishes up.
>>>>>>>>          Starting Set console scheme...
>>>>>>>> [  OK  ] Started Serial Getty on ttyS0.
>>>>>>>> [  OK  ] Started Terminate Plymouth Boot Screen.
>>>>>>>> [  OK  ] Started Login Service.
>>>>>>>> [  OK  ] Started Set console scheme.
>>>>>>>> [  OK  ] Created slice system-getty.slice.
>>>>>>>> [  OK  ] Started Getty on tty1.
>>>>>>>> [  OK  ] Reached target Login Prompts.
>>>>>>>> [FAILED] Failed to start Accounts Service.
>>>>>>>> See 'systemctl status accounts-daemon.service' for details.
>>>>>>>> [  OK  ] Started LSB: Record successful boot for GRUB.
>>>>>>>> [  OK  ] Started OpenBSD Secure Shell server.
>>>>>>>> [FAILED] Failed to start Dispatcher daemon for systemd-networkd.
>>>>>>>> See 'systemctl status networkd-dispatcher.service' for details.
>>>>>>>> [  OK  ] Reached target Multi-User System.
>>>>>>>> [  OK  ] Reached target Graphical Interface.
>>>>>>>> [  OK  ] Started Stop ureadahead data collection 45s after
>>>>>>>> completed
>>>>>>>> startup.
>>>>>>>>          Starting Update UTMP about System Runlevel Changes...
>>>>>>>> [  OK  ] Started Update UTMP about System Runlevel Changes.
>>>>>>>>
>>>>>>>> Ubuntu 18.04.2 LTS gem5-host ttyS0
>>>>>>>>
>>>>>>>> gem5-host login: root (automatic login)
>>>>>>>>
>>>>>>>>
>>>>>>>> Welcome to Ubuntu 18.04.2 LTS (GNU/Linux 4.14.134 x86_64)
>>>>>>>>
>>>>>>>>  * Documentation:  https://help.ubuntu.com
>>>>>>>>  * Management:     https://landscape.canonical.com
>>>>>>>>  * Support:        https://ubuntu.com/advantage
>>>>>>>>
>>>>>>>>
>>>>>>>> The programs included with the Ubuntu system are free software;
>>>>>>>> the exact distribution terms for each program are described in the
>>>>>>>> individual files in /usr/share/doc/*/copyright.
>>>>>>>>
>>>>>>>> Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted
>>>>>>>> by
>>>>>>>> applicable law.
>>>>>>>>
>>>>>>>> Ayaz Akram <yazak...@ucdavis.edu>, 3 Şub 2020 Pzt, 21:20 tarihinde
>>>>>>>> şunu yazdı:
>>>>>>>>
>>>>>>>>> We have recently uploaded a disk image with ubuntu 18.04 installed
>>>>>>>>> which should have basic packages/libraries available. See the
>>>>>>>>> following
>>>>>>>>> post on the mailing list:
>>>>>>>>>
>>>>>>>>> https://www.mail-archive.com/gem5-users@gem5.org/msg17274.html
>>>>>>>>>
>>>>>>>>> You can also refer to gem5art's documentation on building your own
>>>>>>>>> disk images:
>>>>>>>>>
>>>>>>>>> https://gem5art.readthedocs.io/en/latest/main-doc/disks.html
>>>>>>>>>
>>>>>>>>> -Ayaz
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Feb 3, 2020 at 4:04 AM Muhammet Abdullah Soytürk <
>>>>>>>>> muhammetabdullahsoyt...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> What is the best way to install shared libraries to
>>>>>>>>>> linux-x86.img?
>>>>>>>>>> Since apt or dpkg is not installed, I don't know how to add the
>>>>>>>>>> shared
>>>>>>>>>> libraries to the images that I need to execute PageRank in GAP
>>>>>>>>>> benchmark
>>>>>>>>>> suite.
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>> Muhammet
>>>>>>>>>> _______________________________________________
>>>>>>>>>> gem5-users mailing list
>>>>>>>>>> gem5-users@gem5.org
>>>>>>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> gem5-users mailing list
>>>>>>>>> gem5-users@gem5.org
>>>>>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> gem5-users mailing list
>>>>>>>> gem5-users@gem5.org
>>>>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> gem5-users mailing list
>>>>>>> gem5-users@gem5.org
>>>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>>>
>>>>>> _______________________________________________
>>>>>> gem5-users mailing list
>>>>>> gem5-users@gem5.org
>>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>>
>>>>> _______________________________________________
>>>>> gem5-users mailing list
>>>>> gem5-users@gem5.org
>>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>>
>>>> _______________________________________________
>>>> gem5-users mailing list
>>>> gem5-users@gem5.org
>>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>>
>>> _______________________________________________
>>> gem5-users mailing list
>>> gem5-users@gem5.org
>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>>
>> _______________________________________________
>> gem5-users mailing list
>> gem5-users@gem5.org
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to