[gem5-dev] [S] Change in gem5/gem5[develop]: stdlib, configs: Fix riscv-ubuntu-run error

[Hoa Nguyen (Gerrit) via gem5-dev]

Hoa Nguyen has submitted this change. (  
https://gem5-review.googlesource.com/c/public/gem5/+/58889 )


Change subject: stdlib, configs: Fix riscv-ubuntu-run error
..

stdlib, configs: Fix riscv-ubuntu-run error

This change,
https://gem5-review.googlesource.com/c/public/gem5/+/58790,
mistakenly constructs the root object outside of the
Simulator object, which would create another Root object.

The correct usage of a Simulator object is to pass the board to
the object without defining the root.

Change-Id: Iaa9aabe058a00abd964bf935b1b3f05456713275
Signed-off-by: Hoa Nguyen 
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/58889
Reviewed-by: Jason Lowe-Power 
Maintainer: Jason Lowe-Power 
Tested-by: kokoro 
---
M configs/example/gem5_library/riscv-ubuntu-run.py
1 file changed, 22 insertions(+), 2 deletions(-)

Approvals:
  Jason Lowe-Power: Looks good to me, approved; Looks good to me, approved
  kokoro: Regressions pass




diff --git a/configs/example/gem5_library/riscv-ubuntu-run.py  
b/configs/example/gem5_library/riscv-ubuntu-run.py

index 1c95d3f..f3e6d13 100644
--- a/configs/example/gem5_library/riscv-ubuntu-run.py
+++ b/configs/example/gem5_library/riscv-ubuntu-run.py
@@ -115,7 +115,5 @@
 ),
 )

-root = Root(full_system=True, system=board)
-
 simulator = Simulator(board=board)
 simulator.run()

--
To view, visit https://gem5-review.googlesource.com/c/public/gem5/+/58889
To unsubscribe, or for help writing mail filters, visit  
https://gem5-review.googlesource.com/settings


Gerrit-Project: public/gem5
Gerrit-Branch: develop
Gerrit-Change-Id: Iaa9aabe058a00abd964bf935b1b3f05456713275
Gerrit-Change-Number: 58889
Gerrit-PatchSet: 2
Gerrit-Owner: Hoa Nguyen 
Gerrit-Reviewer: Bobby Bruce 
Gerrit-Reviewer: Hoa Nguyen 
Gerrit-Reviewer: Jason Lowe-Power 
Gerrit-Reviewer: Jason Lowe-Power 
Gerrit-Reviewer: kokoro 
Gerrit-MessageType: merged
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] Re: Build failed in Jenkins: nightly #193

[Hoa Nguyen via gem5-dev]

Hi Bobby,

Sorry for that mistake. I pushed the fix and ran the first few minutes of
the simulation, which means the simulator.run() was being executed when the
simulation stopped. No errors occurred!

https://gem5-review.googlesource.com/c/public/gem5/+/58889

Regards,
Hoa Nguyen

On Thu, Apr 14, 2022 at 10:32 AM Bobby Bruce  wrote:

> Hoa,
>
> Looks like you broke the tests with this commit:
> https://gem5-review.googlesource.com/c/public/gem5/+/58790. You should've
> removed the `root = Root(full_system=True, system=board)` line, this is set
> when you execute simulator.run()
>
> Can you push a quick fix (and run it to make sure it works)?
>
> Kind regards,
> Bobby
> --
> Dr. Bobby R. Bruce
> Room 3050,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
> web: https://www.bobbybruce.net
>
>
> On Thu, Apr 14, 2022 at 6:24 AM jenkins-no-reply--- via gem5-dev <
> gem5-dev@gem5.org> wrote:
>
>> See <
>> https://jenkins.gem5.org/job/nightly/193/display/redirect?page=changes>
>>
>> Changes:
>>
>> [Giacomo Travaglini] mem-ruby: CHI fix for WUs on local+upstream line
>>
>> [Bobby R. Bruce] tests: Disable failing MI_Example/Timing CPU X86 Boot
>> Tests
>>
>> [Bobby R. Bruce] tests: Disable failing 8-core Boot Tests for
>> Timing/Atomic
>>
>> [hoanguyen] stdlib, configs: Migrate riscv-ubuntu-run example to Simulator
>>
>> [Jason Lowe-Power] scons: Fix bug in error message
>>
>> [gabe.black] arch-x86: Override make(Read|Write) instead of
>> (read|write)_code.
>>
>> [gabe.black] arch: Eliminate the now unused read_code and write_code args.
>>
>> [yuhsingw] scons: Fix script failed when default files not found
>>
>> [gabe.black] scons: Ensure the fast model license count is always at
>> least 1.
>>
>> [yuhsingw] fastmodel: Export more CortexA76 reset pin
>>
>> [yuhsingw] fastmodel: Export more CortexR52 reset pin
>>
>> [joy] arch-riscv: Added the Zba and Zbb bitmanip instructions
>>
>> [joy] arch-riscv: Added the Zbc bitmanip instructions
>>
>> [joy] arch-riscv: Added the Zbs bitmanip instructions
>>
>>
>> --
>> [...truncated 1.74 MB...]
>> Logging call to command:
>> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
>> /tmp/gem5outissh55y8 -re --silent-redirect
>> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
>> LinearGenerator 1 MESITwoLevel gem5.components.memory HBM2Stack 512MiB
>> Starting Test Suite:
>> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
>>
>> Starting Test Case:
>> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Test:
>> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Passed
>> Logging call to command:
>> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
>> /tmp/gem5outw4uy5g8f -re --silent-redirect
>> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
>> RandomGenerator 1 MESITwoLevel gem5.components.memory
>> SingleChannelDDR3_1600 512MiB
>> Starting Test Suite:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
>>
>> Starting Test Case:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Test:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Passed
>> Logging call to command:
>> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
>> /tmp/gem5outhyxrz3n9 -re --silent-redirect
>> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
>> RandomGenerator 1 MESITwoLevel gem5.components.memory
>> SingleChannelDDR3_2133 512MiB
>> Starting Test Suite:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
>>
>> Starting Test Case:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Test:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
>> Passed
>> Logging call to command:
>> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
>> /tmp/gem5outd3eyei8w -re --silent-redirect
>> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
>> RandomGenerator 1 MESITwoLevel gem5.components.memory
>> SingleChannelDDR4_2400 512MiB
>> Starting Test Suite:
>> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
>>
>> Starting Test Case:
>> 

[gem5-dev] [S] Change in gem5/gem5[develop]: stdlib, configs: Fix riscv-ubuntu-run error

[Hoa Nguyen (Gerrit) via gem5-dev]

Hoa Nguyen has uploaded this change for review. (  
https://gem5-review.googlesource.com/c/public/gem5/+/58889 )



Change subject: stdlib, configs: Fix riscv-ubuntu-run error
..

stdlib, configs: Fix riscv-ubuntu-run error

This change,
https://gem5-review.googlesource.com/c/public/gem5/+/58790,
mistakenly constructs the root object outside of the
Simulator object, which would create another Root object.

The correct usage of a Simulator object is to pass the board to
the object without defining the root.

Change-Id: Iaa9aabe058a00abd964bf935b1b3f05456713275
Signed-off-by: Hoa Nguyen 
---
M configs/example/gem5_library/riscv-ubuntu-run.py
1 file changed, 18 insertions(+), 2 deletions(-)



diff --git a/configs/example/gem5_library/riscv-ubuntu-run.py  
b/configs/example/gem5_library/riscv-ubuntu-run.py

index 1c95d3f..f3e6d13 100644
--- a/configs/example/gem5_library/riscv-ubuntu-run.py
+++ b/configs/example/gem5_library/riscv-ubuntu-run.py
@@ -115,7 +115,5 @@
 ),
 )

-root = Root(full_system=True, system=board)
-
 simulator = Simulator(board=board)
 simulator.run()

--
To view, visit https://gem5-review.googlesource.com/c/public/gem5/+/58889
To unsubscribe, or for help writing mail filters, visit  
https://gem5-review.googlesource.com/settings


Gerrit-Project: public/gem5
Gerrit-Branch: develop
Gerrit-Change-Id: Iaa9aabe058a00abd964bf935b1b3f05456713275
Gerrit-Change-Number: 58889
Gerrit-PatchSet: 1
Gerrit-Owner: Hoa Nguyen 
Gerrit-MessageType: newchange
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] [S] Change in gem5/gem5[develop]: dev-amdgpu: Fix frame writes for <32-bit writes

[Matthew Poremba (Gerrit) via gem5-dev]

Matthew Poremba has uploaded this change for review. (  
https://gem5-review.googlesource.com/c/public/gem5/+/58852 )



Change subject: dev-amdgpu: Fix frame writes for <32-bit writes
..

dev-amdgpu: Fix frame writes for <32-bit writes

In theory a packet between one and eight bytes can be written to frame
buffer memory from the driver. In gem5 pkt->getLE() will
assert if the packet size is <32-bits. Change to pkt->getUintX(...) to
fix this issue.

Change-Id: If8554013e4ea7bac90985487991d0bf8bdc765ea
---
M src/dev/amdgpu/amdgpu_device.cc
1 file changed, 15 insertions(+), 1 deletion(-)



diff --git a/src/dev/amdgpu/amdgpu_device.cc  
b/src/dev/amdgpu/amdgpu_device.cc

index 3c5b179..132a81a 100644
--- a/src/dev/amdgpu/amdgpu_device.cc
+++ b/src/dev/amdgpu/amdgpu_device.cc
@@ -253,7 +253,7 @@
 Addr aperture_offset = offset - aperture;

 // Record the value
-frame_regs[offset] = pkt->getLE();
+frame_regs[offset] = pkt->getUintX(ByteOrder::little);
 if (aperture == gpuvm.gartBase()) {
 frame_regs[aperture_offset] = pkt->getLE();
 DPRINTF(AMDGPUDevice, "GART translation %p -> %p\n",  
aperture_offset,


--
To view, visit https://gem5-review.googlesource.com/c/public/gem5/+/58852
To unsubscribe, or for help writing mail filters, visit  
https://gem5-review.googlesource.com/settings


Gerrit-Project: public/gem5
Gerrit-Branch: develop
Gerrit-Change-Id: If8554013e4ea7bac90985487991d0bf8bdc765ea
Gerrit-Change-Number: 58852
Gerrit-PatchSet: 1
Gerrit-Owner: Matthew Poremba 
Gerrit-MessageType: newchange
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] Re: gem5 v22.0 to be released in early May. Staging branch to be created by the end of April

[Bobby Bruce via gem5-dev]

Dear all,

We intend to create the staging branch on April 28th, with the intent of
releasing gem5 v22.0 in early May. This is a two week warning. Please
ensure all your patches you wish to be part of v22.0 are submitted to the
develop branch prior to April 28th.

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Mon, Apr 4, 2022 at 10:28 AM Bobby Bruce  wrote:

> Dear all,
>
> In line with our policy of having three major releases a year, we're
> aiming to have v22.0 of gem5 released in early May.  This means we'll be
> creating a staging branch from the develop branch by the end of April. The
> staging branch will be intensely tested to ensure it is suitable for
> general community use before being merged into the stable branch.
>
> We understand there's a backlog of patches to be reviewed. We'll try to
> ensure everyone who puts in the effort to submit for this release, and
> responds promptly to feedback, makes it into the v22.0 release. If you feel
> your patches have been ignored, please ping us on the relevant Gerrit
> submission (if you have not already added reviewers, remember to add them).
> Help with reviewing over the next month would also be greatly appreciated.
>
> Kind regards,
> Bobby
> --
> Dr. Bobby R. Bruce
> Room 3050,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
>
> web: https://www.bobbybruce.net
>
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] Re: Build failed in Jenkins: nightly #193

[Bobby Bruce via gem5-dev]

Hoa,

Looks like you broke the tests with this commit:
https://gem5-review.googlesource.com/c/public/gem5/+/58790. You should've
removed the `root = Root(full_system=True, system=board)` line, this is set
when you execute simulator.run()

Can you push a quick fix (and run it to make sure it works)?

Kind regards,
Bobby
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616

web: https://www.bobbybruce.net


On Thu, Apr 14, 2022 at 6:24 AM jenkins-no-reply--- via gem5-dev <
gem5-dev@gem5.org> wrote:

> See <
> https://jenkins.gem5.org/job/nightly/193/display/redirect?page=changes>
>
> Changes:
>
> [Giacomo Travaglini] mem-ruby: CHI fix for WUs on local+upstream line
>
> [Bobby R. Bruce] tests: Disable failing MI_Example/Timing CPU X86 Boot
> Tests
>
> [Bobby R. Bruce] tests: Disable failing 8-core Boot Tests for Timing/Atomic
>
> [hoanguyen] stdlib, configs: Migrate riscv-ubuntu-run example to Simulator
>
> [Jason Lowe-Power] scons: Fix bug in error message
>
> [gabe.black] arch-x86: Override make(Read|Write) instead of
> (read|write)_code.
>
> [gabe.black] arch: Eliminate the now unused read_code and write_code args.
>
> [yuhsingw] scons: Fix script failed when default files not found
>
> [gabe.black] scons: Ensure the fast model license count is always at least
> 1.
>
> [yuhsingw] fastmodel: Export more CortexA76 reset pin
>
> [yuhsingw] fastmodel: Export more CortexR52 reset pin
>
> [joy] arch-riscv: Added the Zba and Zbb bitmanip instructions
>
> [joy] arch-riscv: Added the Zbc bitmanip instructions
>
> [joy] arch-riscv: Added the Zbs bitmanip instructions
>
>
> --
> [...truncated 1.74 MB...]
> Logging call to command:
> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
> /tmp/gem5outissh55y8 -re --silent-redirect
> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
> LinearGenerator 1 MESITwoLevel gem5.components.memory HBM2Stack 512MiB
> Starting Test Suite:
> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
>
> Starting Test Case:
> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Test:
> test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Passed
> Logging call to command:
> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
> /tmp/gem5outw4uy5g8f -re --silent-redirect
> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
> RandomGenerator 1 MESITwoLevel gem5.components.memory
> SingleChannelDDR3_1600 512MiB
> Starting Test Suite:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
>
> Starting Test Case:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Test:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Passed
> Logging call to command:
> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
> /tmp/gem5outhyxrz3n9 -re --silent-redirect
> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
> RandomGenerator 1 MESITwoLevel gem5.components.memory
> SingleChannelDDR3_2133 512MiB
> Starting Test Suite:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
>
> Starting Test Case:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Test:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Passed
> Logging call to command:
> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
> /tmp/gem5outd3eyei8w -re --silent-redirect
> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
> RandomGenerator 1 MESITwoLevel gem5.components.memory
> SingleChannelDDR4_2400 512MiB
> Starting Test Suite:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
>
> Starting Test Case:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Test:
> test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
> Passed
> Logging call to command:
> /nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d
> /tmp/gem5outm48qeir1 -re --silent-redirect
> /nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
> RandomGenerator 1 MESITwoLevel gem5.components.memory
> 

[gem5-dev] Build failed in Jenkins: nightly #193

[jenkins-no-reply--- via gem5-dev]

See 

Changes:

[Giacomo Travaglini] mem-ruby: CHI fix for WUs on local+upstream line

[Bobby R. Bruce] tests: Disable failing MI_Example/Timing CPU X86 Boot Tests

[Bobby R. Bruce] tests: Disable failing 8-core Boot Tests for Timing/Atomic

[hoanguyen] stdlib, configs: Migrate riscv-ubuntu-run example to Simulator

[Jason Lowe-Power] scons: Fix bug in error message

[gabe.black] arch-x86: Override make(Read|Write) instead of (read|write)_code.

[gabe.black] arch: Eliminate the now unused read_code and write_code args.

[yuhsingw] scons: Fix script failed when default files not found

[gabe.black] scons: Ensure the fast model license count is always at least 1.

[yuhsingw] fastmodel: Export more CortexA76 reset pin

[yuhsingw] fastmodel: Export more CortexR52 reset pin

[joy] arch-riscv: Added the Zba and Zbb bitmanip instructions

[joy] arch-riscv: Added the Zbc bitmanip instructions

[joy] arch-riscv: Added the Zbs bitmanip instructions


--
[...truncated 1.74 MB...]
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5outissh55y8 -re --silent-redirect 
/nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
 LinearGenerator 1 MESITwoLevel gem5.components.memory HBM2Stack 512MiB
Starting Test Suite: 
test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
 
Starting Test Case: 
test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
Test: 
test-memory-LinearGenerator-1-MESITwoLevel-gem5.components.memory-HBM2Stack-512MiB-NULL-x86_64-opt-MESI_Two_Level
 Passed
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5outw4uy5g8f -re --silent-redirect 
/nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
 RandomGenerator 1 MESITwoLevel gem5.components.memory SingleChannelDDR3_1600 
512MiB
Starting Test Suite: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
 
Starting Test Case: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
Test: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
 Passed
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5outhyxrz3n9 -re --silent-redirect 
/nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
 RandomGenerator 1 MESITwoLevel gem5.components.memory SingleChannelDDR3_2133 
512MiB
Starting Test Suite: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
 
Starting Test Case: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
Test: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR3_2133-512MiB-NULL-x86_64-opt-MESI_Two_Level
 Passed
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5outd3eyei8w -re --silent-redirect 
/nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
 RandomGenerator 1 MESITwoLevel gem5.components.memory SingleChannelDDR4_2400 
512MiB
Starting Test Suite: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
 
Starting Test Case: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
Test: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelDDR4_2400-512MiB-NULL-x86_64-opt-MESI_Two_Level
 Passed
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5outm48qeir1 -re --silent-redirect 
/nobackup/jenkins/workspace/nightly/tests/gem5/traffic_gen/simple_traffic_run.py
 RandomGenerator 1 MESITwoLevel gem5.components.memory SingleChannelLPDDR3_1600 
512MiB
Starting Test Suite: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelLPDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
 
Starting Test Case: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelLPDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
Test: 
test-memory-RandomGenerator-1-MESITwoLevel-gem5.components.memory-SingleChannelLPDDR3_1600-512MiB-NULL-x86_64-opt-MESI_Two_Level
 Passed
Logging call to command: 
/nobackup/jenkins/workspace/nightly/build/NULL_MESI_Two_Level/gem5.opt -d 
/tmp/gem5out2pu4c1d9 -re --silent-redirect 

[gem5-dev] Re: Adding an extension object to Packet-s

[Yan Lee via gem5-dev]

Hi Gabe and everyone,

Thanks Gabe for bringing this up. Currently I am making a model in AXI
protocol and this model will need the AxUser and AxProt fields in the AXI
protocol. The packet in gem5 cannot carry additional information except the
actual read/write data. I think we can have the extension mechanism in our
gem5 packet just like the way in SystemC. Therefore, we can simulate some
protocol-related behavior with this extension in each gem5 packet.

I think we can have an array-based or linked-list-based extension mechanism
in gem5 packet. That is, we can have multiple extensions in one packet and
may be increased during the transaction. But we can discuss the way of
searching for one extension. In systemc, it uses linear search to find if
one extension exists or not.

Look forward to any feedback or ideas, and thanks for your sharing.

Yan

On Thu, Apr 14, 2022 at 3:37 PM Gabe Black  wrote:

> Hi folks. Yan Lee, a Google colleague of mine, is interested in adding one
> or more extension objects to gem5 Packet. Systemc has a mechanism like this
> already, and it's come up a few times where we've wanted to have something
> like this on the gem5 side as well.
>
> Yan, can you please talk about the problem you're trying to solve, and the
> mechanism you want to add to handle it?
>
> Gabe
>
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[gem5-dev] Adding an extension object to Packet-s

[Gabe Black via gem5-dev]

Hi folks. Yan Lee, a Google colleague of mine, is interested in adding one
or more extension objects to gem5 Packet. Systemc has a mechanism like this
already, and it's come up a few times where we've wanted to have something
like this on the gem5 side as well.

Yan, can you please talk about the problem you're trying to solve, and the
mechanism you want to add to handle it?

Gabe
___
gem5-dev mailing list -- gem5-dev@gem5.org
To unsubscribe send an email to gem5-dev-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s