[gem5-users] How to turn off Gem5 git commit script?

2021-09-23 Thread Todd Bezenek via gem5-users 
(Please be sure to look at my question at the bottom of this message. Also, 
please excuse the length of the message--I want it to be complete.)

You were assigned to review my first Gem5 check-in, so you are getting this 
annoying email. I'm sorry about that, but I do not know who would be a better 
person. :)

In order to satisfy the requirements for a proper Gem5 check-in, I had to do a 
couple of things that changed the way git works on my machine. As a result, 
when I do a "git commit" on a different repository from the machine, the 
required background stuff for Gem5 is launching. How do I turn this off?

The problem is likely because I am creating my own local Gem5 repository to 
play with on the same machine that has the repository I used to create the 
reviewable check-in. Now when I try to do a commit to the "play with" 
repository, the script which helps to set up the Gem5 reviewable check-in 
launches and I get this message:
-
toddb@zippy $ git commit -m "After my change was sent to Gem5."
Invalid commit header
The commit has been cancelled, but a copy of it can be found in 
.git/COMMIT_EDITMSG :

--

After my change was sent to Gem5.

Change-Id: I8f1ef29ab9af589bf433806b5483571728bb0998


--


The first line of a commit must contain one or more gem5 tags separated by
commas (see MAINTAINERS.yaml for the possible tags), followed by a colon and
a commit title. There must be no leading nor trailing whitespaces.

This header line must then be followed by an empty line. A detailed message,
although highly recommended, is not mandatory and can follow that empty line.

e.g.:
cpu: Refactor branch predictors

Refactor branch predictor code to improve its readability, moving functions
X and Y to the base class...

e.g.:
mem,mem-cache: Improve packet class readability

The packet class...

Thu Sep 23 08:38:17 ~/Work/Gem5
-

My question is, how do I get rid of whatever is happening in the background for 
this other repository on the same machine where the repo I have for reviewable 
check-ins is?

If you cannot answer this easily, I will spend more time trying to figure it 
out myself.

Thank you for your patience. The first check-in is always troublesome. :)

-Todd
___
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: gem5 GCN GPU docker error

2021-09-23 Thread Matt Sinclair via gem5-users 
Patch to further update GCN3 webpage posted:
https://gem5-review.googlesource.com/c/public/gem5-website/+/50907

Matt

On Wed, Sep 22, 2021 at 2:10 PM Matt Sinclair 
wrote:

> Thanks Kyle!  I agree we should probably just update the documentation
> Imad found to point to the gem5-resources documentation -- since that was
> what we updated already.  This is part of my plan for later -- that way the
> documentation doesn't go away, but we also don't need to update two
> different sets of documentation.
>
> Matt
>
> On Wed, Sep 22, 2021 at 2:08 PM Kyle Roarty  wrote:
>
>> The issue with the rocblas build is that we don't install rocm-cmake
>> until after we install rocblas. It looks like rocblas downloads it
>> automatically if we don't have it installed, so that's why I didn't get any
>> issues when initially testing it. This patch
>>  should fix
>> the issue.
>>
>> Also, I think the documentation Imad was using was the documentation we
>> have in util/dockerfiles/gcn-gpu. I'm of the opinion that we should just
>> remove that README because we have better documentation on gem5.org and
>> in gem5-resources (Although we still say to build gfx8-apu in the
>> gem5.org documentation)
>>
>> Kyle
>> --
>> *From:* mattdsinclair.w...@gmail.com 
>> *Sent:* Wednesday, September 22, 2021 1:11 PM
>> *To:* gem5 users mailing list 
>> *Cc:* Poremba, Matthew ; Kyle Roarty <
>> kroa...@wisc.edu>; Imad Al Assir ; Bobby Bruce <
>> bbr...@ucdavis.edu>
>> *Subject:* Re: [gem5-users] Re: gem5 GCN GPU docker error
>>
>> Collating responses to emails since you all type faster than me
>>
>> - Imad: glad to hear things work with the updates Matt P proposed!
>> - documentation: Matt P, yes we did update the documentation here:
>> https://resources.gem5.org/ (e.g.,
>> https://resources.gem5.org/resources/square), but apparently didn't
>> propagate those updates to the webpage Imad was using.  I will add that to
>> my list for the week.  Bobby, I see you did part of this already.  I
>> believe there is more that needs to be cleaned up based on what Imad/Matt P
>> said, but I will wait until your version is checked in (imminently) before
>> re-reading and updating.
>> - apt repos: Matt P, you must be right about rocblas updating something.  *
>> Kyle, can you please take care of updating the docker to use the specific
>> rocblas version we need?*
>>
>> Matt
>>
>> On Wed, Sep 22, 2021 at 1:03 PM Bobby Bruce via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>> Just jumping in here,
>>
>> I can confirm I can't build the image anymore. I had assumed this was
>> just a problem on my end before reading these emails. However, the image
>> hosted at http://gcr.io/gem5-test/gcn-gpu should be the most up-to-date
>> version of this Docker prior to this build error being introduced. It
>> should work.
>>
>> I've updated the website script here:
>> https://gem5-review.googlesource.com/c/public/gem5-website/+/50807.
>> Apologies, our documentation could definitely do with some tidying up :).
>>
>> --
>> Dr. Bobby R. Bruce
>> Room 3050,
>> Kemper Hall, UC Davis
>> Davis,
>> CA, 95616
>>
>> web: https://www.bobbybruce.net
>>
>>
>> On Wed, Sep 22, 2021 at 10:02 AM Imad Al Assir via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>> Dear Matt,
>>
>> Many thanks for catching this error! It did indeed solve the problem; I
>> was able to successfully run square and other applications from hip-samples
>> on both, the manually built dockerfile with everything related to rocBLAS
>> and MIOpen commented, and the pre-built docker image which I believe has
>> rocBLAS and MIOpen installed (based on its size).
>>
>> Many thanks again,
>> Imad
>>
>> On Sep 22 2021, at 6:48 pm, Poremba, Matthew 
>> wrote:
>>
>>
>> [AMD Official Use Only]
>>
>>
>>
>> Hi Imad,
>>
>>
>>
>>
>>
>> Yes, the docker seems to have broken in the past few days.
>>
>>
>>
>> Regarding the benchmark not completing, please change your command to use
>> 3 CPUs:
>>
>>
>>
>>
>>
>> docker run --rm -v $PWD/gem5:/gem5 -v $PWD/gem5-resources:/gem5-resources
>> \
>>
>> -w /gem5 gcr.io/gem5-test/gcn-gpu \
>>
>> build/GCN3_X86/gem5.opt configs/example/apu_se.py -n3 \
>>
>> --benchmark-root=/gem5-resources/src/gpu/square/bin \
>>
>> -c square
>>
>>
>>
>> ROCm 4.0 requires 3 CPUs to run now.  I thought we had updated the
>> README.md and website before gem5 21.1 release to reflect this but looks
>> like they are not up to date.
>>
>>
>>
>>
>>
>> -Matt
>>
>>
>>
>> *From:* Imad Al Assir via gem5-users 
>> *Sent:* Wednesday, September 22, 2021 9:31 AM
>> *To:* Matt Sinclair 
>> *Cc:* gem5 users mailing list ; Kyle Roarty <
>> kroa...@wisc.edu>; Imad Al Assir 
>> *Subject:* [gem5-users] Re: gem5 GCN GPU docker error
>>
>>
>> [CAUTION: External Email]
>>
>> Hello,
>> Thank you for your reply. I was simply following the documentation on the
>> gem5 website:
>>

[gem5-users] O3CPU Branch Predictor Similation

2021-09-23 Thread Scott Blankenberg via gem5-users 
Dear all,

I looked at fetch.cc for the O3CPU and in particular looked at the function 
which calls the branch predictor.


bool Fetch::lookupAndUpdateNextPC(const DynInstPtr , TheISA::PCState 
)

Here are the first couple of lines for quick reference:

bool predict_taken;

if (!inst->isControl()) {
inst->staticInst->advancePC(nextPC);
inst->setPredTarg(nextPC);
inst->setPredTaken(false);
return false;
}

ThreadID tid = inst->threadNumber;
predict_taken = branchPred->predict(inst->staticInst, inst->seqNum,
nextPC, tid);

In the above code there is first a check to see whether or not the current 
instruction is a control instruction. If it is not, predict taken = false and 
the function returns. 

Otherwise, if the current instruction is a control instruction, then the branch 
predictor is used for the prediction. 

Here is my question. How is it valid to assume that we already know whether or 
not the instruction is a control instruction before it is put into the branch 
predictor? In other words, does this model of branch prediction implied by the 
code bypass the issue of ghost branches(predicting that non-branch instruction 
addresses correspond to taken branches)? 

One thought I did have was that the branch predictor BTB can filter out the 
non-conditional instructions since I assume the BTB will ideally not contain 
entries which correspond to non-conditional instructions. Thus, in principle, 
if a non-conditional instruction is encountered, even if the branch predictor 
predicts the direction to be taken, the instruction will not hit in the BTB and 
the overall prediction will be not taken. However, this argument breaks down 
when the BTB has partial tags and when false BTB hits can occur.

In summary, how can you know whether or not an instruction is a control 
instruction at fetch time, before it has even been decoded?

Thanks,

Scott Blankenberg
___
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: gem5art, FS mode, panic: PerfKvmCounter (perf_event_paranoid is set to -1)

2021-09-23 Thread Jason Lowe-Power via gem5-users 
Yeah. I would suggest working on a native linux machine if you're going to
use KVM. If you're not using KVM, then WSL *should* (no promises ;)) work
OK.

Cheers,
Jason

On Thu, Sep 23, 2021 at 3:21 PM Reiko Matsuda-dunn <
reiko.matsudad...@colorado.edu> wrote:

> Thanks for the resources! Seems like quite a can of worms.It's almost
> looking like it could be easier to partition a computer for Linux and start
> over. Would you recommend that as an alternative?
>
> All th
>
> On Thu, Sep 23, 2021 at 1:36 PM Jason Lowe-Power via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> Hi Reiko,
>>
>> The KVM CPU requires that the host platform supports KVM. Given that
>> you're using WSL, this means that you need to have nested virtualization
>> enabled and implemented on your WSL kernel.
>> https://www.reddit.com/r/bashonubuntuonwindows/comments/ldbyxa/what_is_the_current_state_of_kvm_acceleration_on/
>> has more information.
>>
>> We can try to help you with this, but currently we only support KVM on
>> native Linux hosts.
>>
>> Cheers,
>> Jason
>>
>> On Thu, Sep 23, 2021 at 11:36 AM Reiko Matsuda-dunn via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>>> Hello,
>>>
>>> I'm trying to troubleshoot this error (output below).  I've looked at
>>> prior posts in this mailing list and was able to change perf_event_paranoid
>>> to -1 ( I confirmed this with $cat /proc/sys/kernel/perf_event_paranoid,
>>> which returns -1, although it resets to 2 every time I reboot). It looks
>>> like there's some mention of a patch, but I haven't been able to find that
>>> patch. If anyone could point me to that, or offer other suggestions I would
>>> be grateful!
>>>
>>> I'm using gem5 21, WSL2, and have otherwise follower the tutorial here:
>>> https://www.gem5.org/documentation/gem5art/tutorials/spec-tutorial
>>> 
>>>
>>> My launch_spec2017_experiment.py has been modified slightly for the
>>> paths and gem5 version.
>>>
>>> Thanks for all your help,
>>> Reiko
>>>
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (1024 Mbytes)
>>> build/X86/mem/mem_interface.cc:791: warn:
>>> DRAM device capacity (32768 Mbytes) does not match the address range 
>>> assigned (128 Mbytes)
>>> build/X86/sim/kernel_workload.cc:46: info: kernel located at:
>>> vmlinux-4.19.83
>>> build/X86/dev/serial/terminal.cc:170: warn:
>>> Sockets disabled, not accepting terminal connections
>>> build/X86/base/remote_gdb.cc:377: warn:
>>> Sockets disabled, not accepting gdb connections
>>> build/X86/mem/coherent_xbar.cc:140: warn:
>>> CoherentXBar system.cpu.mmucache.mmubus has no snooping ports attached!
>>> build/X86/dev/intel_8254_timer.cc:125: warn:
>>> Reading current count from inactive timer.
>>> build/X86/cpu/kvm/base.cc:152: info: KVM:
>>> Coalesced MMIO disabled by config.
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>>> unimplemented function 2
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>>> unimplemented function 3
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>>> unimplemented function 4
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>>> unimplemented function 5
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>>> unimplemented function 6
>>> build/X86/arch/x86/cpuid.cc:180: warn: x86

[gem5-users] Re: gem5art, FS mode, panic: PerfKvmCounter (perf_event_paranoid is set to -1)

2021-09-23 Thread Reiko Matsuda-dunn via gem5-users 
Thanks for the resources! Seems like quite a can of worms.It's almost
looking like it could be easier to partition a computer for Linux and start
over. Would you recommend that as an alternative?

All th

On Thu, Sep 23, 2021 at 1:36 PM Jason Lowe-Power via gem5-users <
gem5-users@gem5.org> wrote:

> Hi Reiko,
>
> The KVM CPU requires that the host platform supports KVM. Given that
> you're using WSL, this means that you need to have nested virtualization
> enabled and implemented on your WSL kernel.
> https://www.reddit.com/r/bashonubuntuonwindows/comments/ldbyxa/what_is_the_current_state_of_kvm_acceleration_on/
> has more information.
>
> We can try to help you with this, but currently we only support KVM on
> native Linux hosts.
>
> Cheers,
> Jason
>
> On Thu, Sep 23, 2021 at 11:36 AM Reiko Matsuda-dunn via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> Hello,
>>
>> I'm trying to troubleshoot this error (output below).  I've looked at
>> prior posts in this mailing list and was able to change perf_event_paranoid
>> to -1 ( I confirmed this with $cat /proc/sys/kernel/perf_event_paranoid,
>> which returns -1, although it resets to 2 every time I reboot). It looks
>> like there's some mention of a patch, but I haven't been able to find that
>> patch. If anyone could point me to that, or offer other suggestions I would
>> be grateful!
>>
>> I'm using gem5 21, WSL2, and have otherwise follower the tutorial here:
>> https://www.gem5.org/documentation/gem5art/tutorials/spec-tutorial
>> 
>>
>> My launch_spec2017_experiment.py has been modified slightly for the
>> paths and gem5 version.
>>
>> Thanks for all your help,
>> Reiko
>>
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (128 Mbytes)
>> build/X86/sim/kernel_workload.cc:46: info: kernel located at:
>> vmlinux-4.19.83
>> build/X86/dev/serial/terminal.cc:170: warn:
>> Sockets disabled, not accepting terminal connections
>> build/X86/base/remote_gdb.cc:377: warn:
>> Sockets disabled, not accepting gdb connections
>> build/X86/mem/coherent_xbar.cc:140: warn:
>> CoherentXBar system.cpu.mmucache.mmubus has no snooping ports attached!
>> build/X86/dev/intel_8254_timer.cc:125: warn:
>> Reading current count from inactive timer.
>> build/X86/cpu/kvm/base.cc:152: info: KVM:
>> Coalesced MMIO disabled by config.
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 2
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 3
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 4
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 5
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 6
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 8
>> build/X86/cpu/kvm/base.cc:152: info: KVM:
>> Coalesced MMIO disabled by config.
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 2
>> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
>> unimplemented function 3
>> build/X86/arch/x86/cpuid.cc:180: warn: x86

[gem5-users] Re: gem5art, FS mode, panic: PerfKvmCounter (perf_event_paranoid is set to -1)

2021-09-23 Thread Jason Lowe-Power via gem5-users 
Hi Reiko,

The KVM CPU requires that the host platform supports KVM. Given that you're
using WSL, this means that you need to have nested virtualization enabled
and implemented on your WSL kernel.
https://www.reddit.com/r/bashonubuntuonwindows/comments/ldbyxa/what_is_the_current_state_of_kvm_acceleration_on/
has more information.

We can try to help you with this, but currently we only support KVM on
native Linux hosts.

Cheers,
Jason

On Thu, Sep 23, 2021 at 11:36 AM Reiko Matsuda-dunn via gem5-users <
gem5-users@gem5.org> wrote:

> Hello,
>
> I'm trying to troubleshoot this error (output below).  I've looked at
> prior posts in this mailing list and was able to change perf_event_paranoid
> to -1 ( I confirmed this with $cat /proc/sys/kernel/perf_event_paranoid,
> which returns -1, although it resets to 2 every time I reboot). It looks
> like there's some mention of a patch, but I haven't been able to find that
> patch. If anyone could point me to that, or offer other suggestions I would
> be grateful!
>
> I'm using gem5 21, WSL2, and have otherwise follower the tutorial here:
> https://www.gem5.org/documentation/gem5art/tutorials/spec-tutorial
> My launch_spec2017_experiment.py has been modified slightly for the paths
> and gem5 version.
>
> Thanks for all your help,
> Reiko
>
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (1024 Mbytes)
> build/X86/mem/mem_interface.cc:791: warn:
> DRAM device capacity (32768 Mbytes) does not match the address range assigned 
> (128 Mbytes)
> build/X86/sim/kernel_workload.cc:46: info: kernel located at:
> vmlinux-4.19.83
> build/X86/dev/serial/terminal.cc:170: warn:
> Sockets disabled, not accepting terminal connections
> build/X86/base/remote_gdb.cc:377: warn:
> Sockets disabled, not accepting gdb connections
> build/X86/mem/coherent_xbar.cc:140: warn:
> CoherentXBar system.cpu.mmucache.mmubus has no snooping ports attached!
> build/X86/dev/intel_8254_timer.cc:125: warn:
> Reading current count from inactive timer.
> build/X86/cpu/kvm/base.cc:152: info: KVM:
> Coalesced MMIO disabled by config.
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 2
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 3
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 4
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 5
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 6
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 8
> build/X86/cpu/kvm/base.cc:152: info: KVM:
> Coalesced MMIO disabled by config.
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 2
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 3
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 4
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 5
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 6
> build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
> unimplemented function 8
> build/X86/sim/simulate.cc:107: info:
> Entering event queue @ 0.  Starting simulation...
> build/X86/cpu/kvm/perfevent.cc:183: panic:
> PerfKvmCounter::attach failed (2)
> Memory Usage: 8738772 KBytes
> build/X86/cpu/kvm/perfevent.cc:183: panic:
> PerfKvmCounter::attach failed (2)
> Memory Usage: 8738772 KBytes
> Program aborted at tick 0
> ___
> 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

[gem5-users] gem5art, FS mode, panic: PerfKvmCounter (perf_event_paranoid is set to -1)

2021-09-23 Thread Reiko Matsuda-dunn via gem5-users 
Hello,

I'm trying to troubleshoot this error (output below).  I've looked at prior
posts in this mailing list and was able to change perf_event_paranoid to -1
( I confirmed this with $cat /proc/sys/kernel/perf_event_paranoid, which
returns -1, although it resets to 2 every time I reboot). It looks like
there's some mention of a patch, but I haven't been able to find that
patch. If anyone could point me to that, or offer other suggestions I would
be grateful!

I'm using gem5 21, WSL2, and have otherwise follower the tutorial here:
https://www.gem5.org/documentation/gem5art/tutorials/spec-tutorial
My launch_spec2017_experiment.py has been modified slightly for the paths
and gem5 version.

Thanks for all your help,
Reiko

build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (1024 Mbytes)
build/X86/mem/mem_interface.cc:791: warn:
DRAM device capacity (32768 Mbytes) does not match the address range
assigned (128 Mbytes)
build/X86/sim/kernel_workload.cc:46: info: kernel located at:
vmlinux-4.19.83
build/X86/dev/serial/terminal.cc:170: warn:
Sockets disabled, not accepting terminal connections
build/X86/base/remote_gdb.cc:377: warn:
Sockets disabled, not accepting gdb connections
build/X86/mem/coherent_xbar.cc:140: warn:
CoherentXBar system.cpu.mmucache.mmubus has no snooping ports attached!
build/X86/dev/intel_8254_timer.cc:125: warn:
Reading current count from inactive timer.
build/X86/cpu/kvm/base.cc:152: info: KVM: Coalesced MMIO disabled by config.
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 2
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 3
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 4
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 5
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 6
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 8
build/X86/cpu/kvm/base.cc:152: info: KVM: Coalesced MMIO disabled by config.
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 2
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 3
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 4
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 5
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 6
build/X86/arch/x86/cpuid.cc:180: warn: x86 cpuid family 0x:
unimplemented function 8
build/X86/sim/simulate.cc:107: info:
Entering event queue @ 0.  Starting simulation...
build/X86/cpu/kvm/perfevent.cc:183: panic: PerfKvmCounter::attach failed (2)
Memory Usage: 8738772 KBytes
build/X86/cpu/kvm/perfevent.cc:183: panic: PerfKvmCounter::attach failed (2)
Memory Usage: 8738772 KBytes
Program aborted at tick 0
___
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: gem5art SPEC2017 FS Tutorial : error opening disk image

2021-09-23 Thread Reiko Matsuda-dunn via gem5-users 
Oh geeze it was just a difficult-to-spot difference in the path! I am using
this tutorial:
https://www.gem5.org/documentation/gem5art/tutorials/spec-tutorial

Thanks!

On Wed, Sep 22, 2021 at 9:07 PM Hoa Nguyen  wrote:

> Hi Reiko,
>
> Can you point to the tutorial and the launch experiment script that you
> used?
>
> I think it's possible that the
> file disk-image/spec2017/spec2017-image/spec2017 didn't exist, or the path
> to that file was incorrect.
>
> Regards,
> Hoa Nguyen
>
> On Wed, Sep 22, 2021, 12:24 PM Reiko Matsuda-dunn via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> Hello!
>>
>> I have been following the tutorial here. I've modified the
>> launch_spec2017_experiment to just run the 602.gcc_s test with the o3 cpu,
>> and I'm getting the error posted below.
>>
>> Some additional info that might be helpful:
>>  - I'm using WSL2.
>>  - from simout:
>> command line: gem5/build/X86/gem5.opt -re 
>> --outdir=/home/user/gem5-resources/src/spec-2017/results/o3/test/602.gcc_s 
>> configs/run_spec.py vmlinux-4.19.83 
>> disk-image/spec2017/spec2017-image/spec2017 o3 602.gcc_s test
>>
>> Any guidance would be much appreciated!
>> -Reiko
>>
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (1024 Mbytes)
>> build/X86/mem/mem_interface.cc:791: warn:
>> DRAM device capacity (32768 Mbytes) does not match the address range 
>> assigned (128 Mbytes)
>> build/X86/sim/kernel_workload.cc:46: info: kernel located at:
>> vmlinux-4.19.83
>> build/X86/dev/serial/terminal.cc:170: warn:
>> Sockets disabled, not accepting terminal connections
>> build/X86/dev/storage/disk_image.cc:95: panic:
>> Error opening disk-image/spec2017/spec2017-image/spec2017
>> Memory Usage: 8726460 KBytes
>> Program aborted at tick 0
>> --- BEGIN LIBC BACKTRACE ---
>> gem5/build/X86/gem5.opt(+0x951420)[0x55d0ad0f7420]
>> gem5/build/X86/gem5.opt(+0x97407e)[0x55d0ad11a07e]
>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f63f0e9a3c0]
>> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f63f047518b]
>> /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f63f0454859]
>> gem5/build/X86/gem5.opt(+0x345fb5)[0x55d0acaebfb5]
>> gem5/build/X86/gem5.opt(+0x107f1a0)[0x55d0ad8251a0]
>> gem5/build/X86/gem5.opt(+0x107f37d)[0x55d0ad82537d]
>> gem5/build/X86/gem5.opt(+0x1448796)[0x55d0adbee796]
>> gem5/build/X86/gem5.opt(+0x1449a66)[0x55d0adbefa66]
>> gem5/build/X86/gem5.opt(+0x31a261)[0x55d0acac0261]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8738)[0x7f63f1150738]
>>
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyObject_MakeTpCall+0xab)[0x7f63f1150b1b]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8de0)[0x7f63f1150de0]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x74d6d)[0x7f63f0f1cd6d]
>>
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x7d86)[0x7f63f0f24ef6]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x8006b)[0x7f63f0f2806b]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8daa)[0x7f63f1150daa]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x74d6d)[0x7f63f0f1cd6d]
>>
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x7d86)[0x7f63f0f24ef6]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x8006b)[0x7f63f0f2806b]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8daa)[0x7f63f1150daa]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x74d6d)[0x7f63f0f1cd6d]
>>
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x7d86)[0x7f63f0f24ef6]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x8006b)[0x7f63f0f2806b]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8daa)[0x7f63f1150daa]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x74d6d)[0x7f63f0f1cd6d]
>>
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x7d86)[0x7f63f0f24ef6]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x8006b)[0x7f63f0f2806b]
>> /lib/x86_64-linux-gnu/libpython3.8.so.1.0(+0x2a8daa)[0x7f63f1150daa]
>>

[gem5-users] Get Size of Stack and Heap

2021-09-23 Thread Ange via gem5-users 
Hi all,

I am trying to keep track of the size of the stack and heap while executing a 
binary, and at the moment, I can get the address of the stack pointer using 
this line of code 
cpu->readArchIntReg(ArmISA::INTREG_SP ,tid). 
I am also trying to read the frame pointer (FP), but I am having trouble 
getting the address for it
because it always prints zero as its address, and I am using Register 11 for 
the FP (cpu->readArchIntReg(ArmISA::INTREG_R11) ).
Am I doing something wrong, or is there a better way to get the stack size?  
and also the heap size with its addresses?

I saw that someone asked a similar question a while back on this forum, but it 
was not fully answered. 
Here is the link https://www.mail-archive.com/gem5-users@gem5.org/msg04154.html

I need help! 

Ange
___
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: Problems with Deprecated names are not supported by the compiler

2021-09-23 Thread Jason Lowe-Power via gem5-users 
Hi Xihui,

The error is "died with "

I would guess you're out of memory or trying to compile too many files at
once. But, it could be many different problems. If it's an issue with
dependencies or your host, you can always use our docker images:
https://www.gem5.org/documentation/general_docs/building#:~:text=dev%20pkg-config-,Docker,-For%20users%20struggling

Cheers,
Jason

On Thu, Sep 23, 2021 at 1:01 AM Xihui Yuan via gem5-users <
gem5-users@gem5.org> wrote:

> Hi Jason,
>
>   Thanks for your help.
>   But there are lots of errors in the first time to build gem5.
>
> scons: *** [build/X86/mem/ruby/protocol/DMA_Controller.py.cc]
> CalledProcessError : Command '['/home/xihui/下载/gem5/build/X86/marshal',
> 'build/X86/mem/ruby/protocol/DMA_Controller.py']' died with
> .
> Traceback (most recent call last):
>   File "/usr/lib/scons/SCons/Action.py", line 1209, in execute
> result = self.execfunction(target=target, source=rsources, env=env)
>   File "/home/xihui/下载/gem5/build/X86/SConscript", line 1293, in
> embedPyFile
> marshalled = subprocess.check_output(
>   File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
> return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
>   File "/usr/lib/python3.8/subprocess.py", line 516, in run
> raise CalledProcessError(retcode, process.args,
> subprocess.CalledProcessError: Command
> '['/home/xihui/下载/gem5/build/X86/marshal',
> 'build/X86/mem/ruby/protocol/DMA_Controller.py']' died with
> .
> scons: building terminated because of errors.
>
> Do you have any opinion or suggestion?
>
>
> Regards,
> Xihui
> ___
> 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: syscall perf_event_open (#241) unimplemented

2021-09-23 Thread walt_90--- via gem5-users 
 Hi Giacomo,
Thanks for your reply.
Is there any reason for implementing it in full system simulation only?
Can we implement it in SE mode?
Best regards.
On Thursday, September 23, 2021, 11:04:42 AM GMT+3, Giacomo Travaglini via 
gem5-users  wrote:  
 
 Hi

It has been fixed for full-system simulation (the patch you are referring to is 
providing visibility of the PMU to the linux kernel),
But the syscall in SE mode is still un-implemented.

Kind Regards

Giacomo


> -Original Message-
> From: walt_90--- via gem5-users 
> Sent: 22 September 2021 20:06
> To: Gem5 Users Mailing List 
> Cc: walt...@yahoo.com
> Subject: [gem5-users] syscall perf_event_open (#241) unimplemented
>
> I got the following error while trying to run a binary with se.py
>
> build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open (#241)
> unimplemented.
> Memory Usage: 703864 KBytes
>
> I am using the latest version of gem5 on Ubuntu 18.04.
>
>
>
> I read the related threads titled:
>
>
> [gem5-users] Using perf_event with the ARM PMU inside gem5 on Linux
>
> gem5-dev] Change in gem5/gem5[develop]: arch-arm: Implement ArmPMU
> DTB generation
>
>
> According to my understanding to these threads, this problem have been
> fixed, am I correct?
>
> Thanks.
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 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: Simulation Frequency is always constant - 1THz

2021-09-23 Thread Gabriel Busnot via gem5-users 
Hi,

Arthur's answer still stands. As he said, sim_freq is the time resolution of 
the simulator itself. It defines the points in time where you are 'allowed' to 
schedule events. By default, you can schedule an event every 1e-12 second of 
simulated time (1THz). That does not mean all components in the model take 
action at this frequency. The CPU model, for instance, will use its own 
frequency (c.f. ClockedObject class) to compute how many simulation ticks have 
to elapse before its next own clockEdge().

Regards,
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] Re: Wrong stats in gem5 v21.1

2021-09-23 Thread Pedro Becker via gem5-users 
I just saw you sent a fix to gem5 repo and there is a new minor version that 
should solve this problem. I'll try it out. Thanks.

Pedro.
___
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: Wrong stats in gem5 v21.1

2021-09-23 Thread Pedro Becker via gem5-users 
Hi Meng, 

Did you found a solution to this problem? Rollback the code to the previous 
version?
I have the same weird behavior on my stats.txt with gem5 version 21.1.0.0.

Best, 
Pedro.
___
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: syscall perf_event_open (#241) unimplemented

2021-09-23 Thread Giacomo Travaglini via gem5-users 
Hi

It has been fixed for full-system simulation (the patch you are referring to is 
providing visibility of the PMU to the linux kernel),
But the syscall in SE mode is still un-implemented.

Kind Regards

Giacomo


> -Original Message-
> From: walt_90--- via gem5-users 
> Sent: 22 September 2021 20:06
> To: Gem5 Users Mailing List 
> Cc: walt...@yahoo.com
> Subject: [gem5-users] syscall perf_event_open (#241) unimplemented
>
> I got the following error while trying to run a binary with se.py
>
> build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open (#241)
> unimplemented.
> Memory Usage: 703864 KBytes
>
> I am using the latest version of gem5 on Ubuntu 18.04.
>
>
>
> I read the related threads titled:
>
>
> [gem5-users] Using perf_event with the ARM PMU inside gem5 on Linux
>
> gem5-dev] Change in gem5/gem5[develop]: arch-arm: Implement ArmPMU
> DTB generation
>
>
> According to my understanding to these threads, this problem have been
> fixed, am I correct?
>
> Thanks.
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] Re: Problems with Deprecated names are not supported by the compiler

2021-09-23 Thread Xihui Yuan via gem5-users 
Hi Jason,
  
  Thanks for your help.
  But there are lots of errors in the first time to build gem5.

scons: *** [build/X86/mem/ruby/protocol/DMA_Controller.py.cc] 
CalledProcessError : Command '['/home/xihui/下载/gem5/build/X86/marshal', 
'build/X86/mem/ruby/protocol/DMA_Controller.py']' died with .
Traceback (most recent call last):
  File "/usr/lib/scons/SCons/Action.py", line 1209, in execute
result = self.execfunction(target=target, source=rsources, env=env)
  File "/home/xihui/下载/gem5/build/X86/SConscript", line 1293, in embedPyFile
marshalled = subprocess.check_output(
  File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 516, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 
'['/home/xihui/下载/gem5/build/X86/marshal', 
'build/X86/mem/ruby/protocol/DMA_Controller.py']' died with .
scons: building terminated because of errors.

Do you have any opinion or suggestion?


Regards,
Xihui
___
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: regarding gem5

2021-09-23 Thread Gabriel Busnot via gem5-users 
Are you talking about Ruby, Garnet and the like? It is perfectly available in 
the link I gave to you. git clone will provide you with gem5 v.21.1.0.2, the 
very latest stable release as of today. There is no "special" public version of 
gem5 I am aware of, anyway.

The commands I gave to you are, word for word, the commands you need to build 
gem5 with Garnet-standalone, once dependencies are installed using apt. Follow 
these steps very carefully if you have bad luck with my commands: 
https://www.gem5.org/documentation/learning_gem5/part1/building/.

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] Re: Access to gem5 101 course

2021-09-23 Thread Javed Osmany via gem5-users 
Hello Scott

Ahh, no I can't access any of the parts of the courses, just realised. 

Tks
JO


-Original Message-
From: Scott Blankenberg via gem5-users [mailto:gem5-users@gem5.org] 
Sent: 22 September 2021 23:02
To: gem5-users@gem5.org
Cc: scot...@synopsys.com
Subject: [gem5-users] Re: Access to gem5 101 course

Hello Javed Osmany,

Did you try clicking the links to the different parts of the course?

Thanks,

Scott Blankenberg
___
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