[gem5-users] Re: ARM KVM
To use hardware-accelerated virtualization (i.e., KVM) your host and guest must have the same ISA (and the host must have virtualization extension). Cheers, Jason On Mon, Jul 12, 2021 at 12:17 PM Νικόλαος Ταμπουρατζής via gem5-users < gem5-users@gem5.org> wrote: > Dear gem5 community, > > I have installed the latest gem5 on an x86 machine. Is it possible to > run ARM FS with kvm on X86 machine or the host machine must be > ARM-based? > > I try to execute the following configuration (from this thread > https://www.mail-archive.com/gem5-users@gem5.org/msg19472.html): > > $GEM5/build/ARM/gem5.opt $GEM5/configs/example/arm/fs_bigLITTLE.py > --kernel=vmlinux.arm64 --machine-type VExpress_GEM5 --disk > ubuntu-18.04-arm64-docker.img --cpu-type kvm --big-cpus 4 > > and I get the following error (which means that there is not the kvm > option): > > fs_bigLITTLE.py: error: argument --cpu-type: invalid choice: 'kvm' > (choose from 'atomic', 'timing', 'exynos') > > May you help me, please? > > Best regards, > Nikos > > > > ___ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-users] ARM KVM
Dear gem5 community, I have installed the latest gem5 on an x86 machine. Is it possible to run ARM FS with kvm on X86 machine or the host machine must be ARM-based? I try to execute the following configuration (from this thread https://www.mail-archive.com/gem5-users@gem5.org/msg19472.html): $GEM5/build/ARM/gem5.opt $GEM5/configs/example/arm/fs_bigLITTLE.py --kernel=vmlinux.arm64 --machine-type VExpress_GEM5 --disk ubuntu-18.04-arm64-docker.img --cpu-type kvm --big-cpus 4 and I get the following error (which means that there is not the kvm option): fs_bigLITTLE.py: error: argument --cpu-type: invalid choice: 'kvm' (choose from 'atomic', 'timing', 'exynos') May you help me, please? Best regards, Nikos ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-users] Re: Trouble getting an image to mount
Hi, Can you try changing the "--root-device" option in the command to run gem5 to one of "/dev/vda1", "/dev/sda1", "/dev/hda", "/dev/vda", "/dev/sda"? Regards, Hoa Nguyen On 7/2/21, Eliot Moss via gem5-users wrote: > I've ried my best to follow the instruction on how to build a disk image > using > packer. I obtained an image qemu built and that could mount on the host > system using guestmount. It is for ubuntu 18.04. But when I try to mount > it > in gem5 it says it can't find a root partition (further details below). > > The same gem5 build can mount your ubuntu 18.04 image just fine. > > How can I figure out what I am doing wrong / differently that leads to the > failure? > > Here is the proximal gem5 output (full system.pc.com_1.device file > attached) > along with the terminal output from the command running gem5 > == > VFS: Cannot open root device "hda1" or unknown-block(3,1): error -6 > Please append a correct "root=" boot option; here are the available > partitions: > 0100 16384 ram0 > (driver?) > 0101 16384 ram1 > (driver?) > 0102 16384 ram2 > (driver?) > 0103 16384 ram3 > (driver?) > 0104 16384 ram4 > (driver?) > 0105 16384 ram5 > (driver?) > 0106 16384 ram6 > (driver?) > 0107 16384 ram7 > (driver?) > 0108 16384 ram8 > (driver?) > 0109 16384 ram9 > (driver?) > 010a 16384 ram10 > (driver?) > 010b 16384 ram11 > (driver?) > 010c 16384 ram12 > (driver?) > 010d 16384 ram13 > (driver?) > 010e 16384 ram14 > (driver?) > 010f 16384 ram15 > (driver?) > 0300 2792256 hda > driver: ide-gd > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(3,1) > == > > Here's the output from my script: > == > Global frequency set at 1 ticks per second > warn: DRAM device capacity (8192 Mbytes) does not match the address range > assigned (4096 Mbytes) > info: kernel located at: ../work/gem5-images/vmlinux-4.15.0-147-151-ubuntu > system.pc.com_1.device: Listening for connections on port 3456 > 0: system.remote_gdb: listening for remote gdb on port 7000 > warn: Reading current count from inactive timer. > gem5 Simulator System. http://gem5.org > gem5 is copyrighted software; use the --copyright option for details. > > gem5 version 21.0.1.0 > gem5 compiled Jun 26 2021 03:16:35 > gem5 started Jul 2 2021 17:06:28 > gem5 executing on xclean-moss-25980, pid 38 > command line: build/X86/gem5.fast configs/full_system/myfs.py --mem-size=3GB > > --cpu-type=AtomicSimpleCPU --caches --l2cache --os-type=linux > --kernel=../work/gem5-images/vmlinux-4.15.0-147-151-ubuntu > --disk-image=../work/gem5-images/build/ubuntu1804.img > --root-device=/dev/hda1 --command-line > 'earlyprintk=ttyS0 console=ttyS0 lpj=723 root=%(rootdev)s mem=%(mem)s' > > REAL SIMULATION > warn: iobus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: bridge.master is deprecated. `master` is now called `mem_side_port` > warn: membus.master is deprecated. `master` is now called `mem_side_ports` > warn: bridge.slave is deprecated. `slave` is now called `cpu_side_port` > warn: iobus.master is deprecated. `master` is now called `mem_side_ports` > warn: apicbridge.slave is deprecated. `slave` is now called `cpu_side_port` > warn: membus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: apicbridge.master is deprecated. `master` is now called > `mem_side_port` > warn: membus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: iobus.master is deprecated. `master` is now called `mem_side_ports` > warn: membus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: tol2bus.master is deprecated. `master` is now called `mem_side_ports` > warn: membus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: tol2bus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: tol2bus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: tol2bus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: tol2bus.slave is deprecated. `slave` is now called `cpu_side_ports` > warn: membus.master is deprecated. `master` is now called `mem_side_ports` > warn: membus.master is deprecated. `master` is now called `mem_side_ports` > warn: membus.slave is deprecated. `slave` is now called `cpu_side_ports` > info: Entering event queue @ 0. Starting simulation... > warn: x86 cpuid family 0x: unimplemented function 6 > warn: x86 cpuid family 0x: unimplemented function 6 > warn: x86 cpuid family 0x: unimplemented function 6 > warn: instruction 'fninit' unimplemented > warn: Don't know what interrupt to clear for console. > warn: instruction 'sgdt_Ms' unimplemented > warn: x86 cpuid family 0x: unimplemented function 6 > warn: x86 cpuid
[gem5-users] Re: PCI Express on gem5
Hi Nikos, The author submitted a partial implementation to gerrit (Simply modelling a PCIe Link) some time ago: https://gem5-review.googlesource.com/c/public/gem5/+/13024 A Root Complex and PCI Express Switch implementation was supposed to be uploaded but this never happened as far as I know. If you are really interested I suggest you to contact the author. It would be nice if we could upstream that contribution Please keep us posted Kind Regards Giacomo > -Original Message- > From: Νικόλαος Ταμπουρατζής via gem5-users > Sent: 12 July 2021 16:17 > To: gem5-users > Cc: Νικόλαος Ταμπουρατζής > Subject: [gem5-users] PCI Express on gem5 > > > Dear gem5 community, > > I have successfully connected the two gem5s through Gigabit PCI e1000 card > on ARM FS. However, I would like to use a faster card (more than > gigabit) based on PCI-E instead of PCI. Is there any work on this? I found > this > work: https://www.ideals.illinois.edu/handle/2142/101569 > but unfortunately I can not find the source code of this. I will appreciate > it if > anyone may help me. > > Thank you in advance, > Nikos > ___ > gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an > email to gem5-users- > le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s 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 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-users] PCI Express on gem5
Dear gem5 community, I have successfully connected the two gem5s through Gigabit PCI e1000 card on ARM FS. However, I would like to use a faster card (more than gigabit) based on PCI-E instead of PCI. Is there any work on this? I found this work: https://www.ideals.illinois.edu/handle/2142/101569 but unfortunately I can not find the source code of this. I will appreciate it if anyone may help me. Thank you in advance, Nikos ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-users] Re: CHI - Cluster CPUs having a private L2 cache
Hello Gabriel Thank you for your reply. Will realise your suggestions. Best regards JO -Original Message- From: Gabriel Busnot via gem5-users [mailto:gem5-users@gem5.org] Sent: 12 July 2021 09:23 To: gem5-users@gem5.org Cc: Gabriel Busnot Subject: [gem5-users] Re: CHI - Cluster CPUs having a private L2 cache Hi Javed, This looks fine to me, at least regarding L2s being private. CHI_config.py:538 in the line where you instantiate a cache memory per CPU and CHI_config.py:557 is the line where you instantiate the CHI ruby controller that makes use of that cache memory instance. One way to check if two python variables point to the same instance or not is to test them with "is": ((a is b) == True) means that a and b are the same object. (a is not b) is the test syntax you want to test for non-identity. Just check that ruby_system.littleCluster._cpus[i].l2 as well as ruby_system.littleCluster._cpus[i].l2.cache are different for all i. Best, Gabriel ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-users] Re: CHI - Cluster CPUs having a private L2 cache
Hi Javed, This looks fine to me, at least regarding L2s being private. CHI_config.py:538 in the line where you instantiate a cache memory per CPU and CHI_config.py:557 is the line where you instantiate the CHI ruby controller that makes use of that cache memory instance. One way to check if two python variables point to the same instance or not is to test them with "is": ((a is b) == True) means that a and b are the same object. (a is not b) is the test syntax you want to test for non-identity. Just check that ruby_system.littleCluster._cpus[i].l2 as well as ruby_system.littleCluster._cpus[i].l2.cache are different for all i. Best, Gabriel ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
