From c1c517a1c7cdcca7dfdd76ef7a416ac21380234d Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Thu, 12 Apr 2018 11:20:58 +0100 Subject: [PATCH] readme: link to gem5 spectre meltdown poc --- README.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.adoc b/README.adoc index addf2b4..66e76da 100644 --- a/README.adoc +++ b/README.adoc @@ -2526,9 +2526,11 @@ Like QEMU, gem5 also has a syscall emulation mode (SE), but in this tutorial we * advantages of gem5: ** simulates a generic more realistic pipelined and optionally out of order CPU cycle by cycle, including a realistic DRAM memory access model with latencies, caches and page table manipulations. This allows us to: *** do much more realistic performance benchmarking with it, which makes absolutely no sense in QEMU, which is purely functional -*** make certain functional cache observations that are not possible in QEMU, e.g.: -**** use Linux kernel APIs that flush memory like DMA, which are crucial for driver development. In QEMU, the driver would still work even if we forget to flush caches. -**** TODO spectre / meltdown +*** make certain functional observations that are not possible in QEMU, e.g.: +**** use Linux kernel APIs that flush cache memory like DMA, which are crucial for driver development. In QEMU, the driver would still work even if we forget to flush caches. +**** spectre / meltdown: +***** https://www.mail-archive.com/gem5-users@gem5.org/msg15319.html +***** https://github.com/jlpresearch/gem5/tree/spectre-test + It is not of course truly cycle accurate, as that ** would require exposing proprietary information of the CPU designs: link:https://stackoverflow.com/questions/17454955/can-you-check-performance-of-a-program-running-with-qemu-simulator/33580850#33580850[]