Searched hist:11435 (Results 1 - 25 of 28) sorted by relevance
/gem5/src/gpu-compute/ | ||
H A D | ndrange.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | shader.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | dispatcher.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | shader.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | compute_unit.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/ext/sst/ | ||
H A D | ExtMaster.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/arch/arm/ | ||
H A D | vtophys.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | isa.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/arch/hsail/insts/ | ||
H A D | mem.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/minor/ | ||
H A D | fetch1.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | lsq.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/arch/mips/ | ||
H A D | locked_mem.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/mem/cache/prefetch/ | ||
H A D | queued.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/trace/ | ||
H A D | trace_cpu.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/testers/rubytest/ | ||
H A D | Check.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/kvm/ | ||
H A D | x86_cpu.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | base.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/checker/ | ||
H A D | cpu_impl.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | cpu.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/testers/memtest/ | ||
H A D | memtest.cc | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/o3/ | ||
H A D | lsq.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | lsq_impl.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/mem/ | ||
H A D | request.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
/gem5/src/cpu/ | ||
H A D | base.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
H A D | base_dyn_inst.hh | 11435:0f1b46dde3fa Thu Apr 07 10:30:00 EDT 2016 Mitch Hayenga <mitch.hayenga@arm.com> mem: Remove threadId from memory request class In general, the ThreadID parameter is unnecessary in the memory system as the ContextID is what is used for the purposes of locks/wakeups. Since we allocate sequential ContextIDs for each thread on MT-enabled CPUs, ThreadID is unnecessary as the CPUs can identify the requesting thread through sideband info (SenderState / LSQ entries) or ContextID offset from the base ContextID for a cpu. This is a re-spin of 20264eb after the revert (bd1c6789) and includes some fixes of that commit. |
Completed in 289 milliseconds