Searched hist:11097 (Results 1 - 4 of 4) sorted by relevance
/gem5/src/cpu/ | ||
H A D | base_dyn_inst_impl.hh | 11097:da477ae38907 Tue Sep 15 09:14:00 EDT 2015 Hongil Yoon <ongal@cs.wisc.edu> cpu, o3: consider split requests for LSQ checksnoop operations This patch enables instructions in LSQ to track two physical addresses for corresponding two split requests. Later, the information is used in checksnoop() to search for/invalidate the corresponding LD instructions. The current implementation has kept track of only the physical address that is referenced by the first split request. Thus, for checksnoop(), the line accessed by the second request has not been considered, causing potential correctness issues. Committed by: Nilay Vaish <nilay@cs.wisc.edu> |
H A D | base_dyn_inst.hh | 11097:da477ae38907 Tue Sep 15 09:14:00 EDT 2015 Hongil Yoon <ongal@cs.wisc.edu> cpu, o3: consider split requests for LSQ checksnoop operations This patch enables instructions in LSQ to track two physical addresses for corresponding two split requests. Later, the information is used in checksnoop() to search for/invalidate the corresponding LD instructions. The current implementation has kept track of only the physical address that is referenced by the first split request. Thus, for checksnoop(), the line accessed by the second request has not been considered, causing potential correctness issues. Committed by: Nilay Vaish <nilay@cs.wisc.edu> |
/gem5/src/cpu/o3/ | ||
H A D | iew_impl.hh | 11097:da477ae38907 Tue Sep 15 09:14:00 EDT 2015 Hongil Yoon <ongal@cs.wisc.edu> cpu, o3: consider split requests for LSQ checksnoop operations This patch enables instructions in LSQ to track two physical addresses for corresponding two split requests. Later, the information is used in checksnoop() to search for/invalidate the corresponding LD instructions. The current implementation has kept track of only the physical address that is referenced by the first split request. Thus, for checksnoop(), the line accessed by the second request has not been considered, causing potential correctness issues. Committed by: Nilay Vaish <nilay@cs.wisc.edu> |
H A D | lsq_unit_impl.hh | 11097:da477ae38907 Tue Sep 15 09:14:00 EDT 2015 Hongil Yoon <ongal@cs.wisc.edu> cpu, o3: consider split requests for LSQ checksnoop operations This patch enables instructions in LSQ to track two physical addresses for corresponding two split requests. Later, the information is used in checksnoop() to search for/invalidate the corresponding LD instructions. The current implementation has kept track of only the physical address that is referenced by the first split request. Thus, for checksnoop(), the line accessed by the second request has not been considered, causing potential correctness issues. Committed by: Nilay Vaish <nilay@cs.wisc.edu> |
Completed in 109 milliseconds