Searched hist:12584 (Results 1 - 6 of 6) sorted by relevance
| /gem5/src/arch/x86/isa/insts/system/ | ||
| H A D | invlpg.py | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
| H A D | segmentation.py | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
| H A D | msrs.py | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/arch/x86/isa/insts/general_purpose/control_transfer/ | ||
| H A D | interrupts_and_exceptions.py | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/arch/x86/isa/insts/general_purpose/data_transfer/ | ||
| H A D | move.py | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/arch/x86/isa/ | ||
| H A D | macroop.isa | 12584:2af98e1fb894 Mon Mar 12 20:06:00 EDT 2018 Gabe Black <gabeblack@google.com> x86: Replace the .serializing directive with .serialize_(before|after). This makes it explicit which type of serialization you want, and also makes it possible to make a macroop serialize before. The old serializing directive was renamed .serialize_after in the microcode assembler, and throughout the microcode implementation, and its behavior is unchanged. More specifically, it still marks the last microop within the macroop as IsSerializing and IsSerializeAfter. The new .serialize_before directive does something similar and marks the first microop as IsSerializing and IsSerializeBefore. Change-Id: Ia53466c734c651c65400809de7ef903c4a6c3e7e Reviewed-on: https://gem5-review.googlesource.com/9041 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Maintainer: Gabe Black <gabeblack@google.com> |
Completed in 29 milliseconds