Searched hist:13209 (Results 1 - 4 of 4) sorted by relevance
| /gem5/src/systemc/core/ | ||
| H A D | scheduler.hh | diff 13209:aad30faa966b Fri Sep 14 23:20:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Change how the scheduler orders processes. The Accellera implementation looks like it does all the methods, then all the threads, and then loops back and tries again, and there are even comments in the code that suggests that. What it actually does, however, is runs all the methods, then runs a single thread if one is waiting, and then starts over. The effect is that the scheduler will run any methods first, then run threads until a method might have become ready, and then repeat. This will actually result in more mixing of threads and methods, more context switches, and worse performance, but it makes the regressions pass more. Change-Id: I7cb0485e26eed79204ff2a3c3ded27b973e0b7b0 Reviewed-on: https://gem5-review.googlesource.com/c/12808 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| H A D | scheduler.cc | diff 13209:aad30faa966b Fri Sep 14 23:20:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Change how the scheduler orders processes. The Accellera implementation looks like it does all the methods, then all the threads, and then loops back and tries again, and there are even comments in the code that suggests that. What it actually does, however, is runs all the methods, then runs a single thread if one is waiting, and then starts over. The effect is that the scheduler will run any methods first, then run threads until a method might have become ready, and then repeat. This will actually result in more mixing of threads and methods, more context switches, and worse performance, but it makes the regressions pass more. Change-Id: I7cb0485e26eed79204ff2a3c3ded27b973e0b7b0 Reviewed-on: https://gem5-review.googlesource.com/c/12808 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/mem/cache/tags/ | ||
| H A D | fa_lru.hh | diff 13164:da6240a1ccfb Wed Oct 03 08:55:00 EDT 2018 Daniel R. Carvalho <odanrc@yahoo.com.br> mem-cache: Make checking function const in FALRU The checking function should not be able to modify either the head and tail pointers nor should it modify its class. Change-Id: I2ad495f0c8c6b778d48512143e94b4c9a353f22e Signed-off-by: Daniel R. Carvalho <odanrc@yahoo.com.br> Reviewed-on: https://gem5-review.googlesource.com/c/13209 Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com> Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> |
| H A D | fa_lru.cc | diff 13164:da6240a1ccfb Wed Oct 03 08:55:00 EDT 2018 Daniel R. Carvalho <odanrc@yahoo.com.br> mem-cache: Make checking function const in FALRU The checking function should not be able to modify either the head and tail pointers nor should it modify its class. Change-Id: I2ad495f0c8c6b778d48512143e94b4c9a353f22e Signed-off-by: Daniel R. Carvalho <odanrc@yahoo.com.br> Reviewed-on: https://gem5-review.googlesource.com/c/13209 Reviewed-by: Nikos Nikoleris <nikos.nikoleris@arm.com> Maintainer: Nikos Nikoleris <nikos.nikoleris@arm.com> |
Completed in 58 milliseconds