From cc190fd3554dc9867e50cdb3c09a95c8d9e604c8 Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Sat, 7 Apr 2018 18:46:26 +0100 Subject: [PATCH] readme: fix all broken asciidoctor links. Add the -v flag to build-doc to help catch them later. --- README.adoc | 10 +++++----- build-doc | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.adoc b/README.adoc index e3feeae..5d4acf1 100644 --- a/README.adoc +++ b/README.adoc @@ -23,7 +23,7 @@ cd linux-kernel-module-cheat ./configure && ./build && ./run .... -The first configure will take a while (30 minutes to 2 hours) to clone and build, see <> for more details. +The first configure will take a while (30 minutes to 2 hours) to clone and build, see <> for more details. If you don't want to wait, you could also try to compile the examples and run them on your host computer as explained on at <>, but as explained on that section, that is dangerous, limited, and will likely not work. @@ -1204,7 +1204,7 @@ To enable networking by default, use the methods documented at <> by passing enabling KVM with: +You can make QEMU or gem5 <> by passing enabling KVM with: .... ./run -K @@ -2373,8 +2373,8 @@ It is not of course truly cycle accurate, as that but the approximation is reasonable. + It is used mostly for microarchitecture research purposes: when you are making a new chip technology, you don't really need to specialize enormously to an existing microarchitecture, but rather develop something that will work with a wide range of future architectures. -** runs are deterministic by default, unlike QEMU which has a special <> mode, that requires first playing the content once and then replaying -* disadvantage of gem5: slower than QEMU, see: <> +** runs are deterministic by default, unlike QEMU which has a special <> mode, that requires first playing the content once and then replaying +* disadvantage of gem5: slower than QEMU, see: <> + This implies that the user base is much smaller, since no Android devs. + @@ -2967,7 +2967,7 @@ We are unable to use `gdbserver` because of networking: <>. -First make sure that for your arch the kernel debugging on the given target works for the architecture: <>, on which we rely. When we last tested, this was not the case for aarch64: <> +First make sure that for your arch the kernel debugging on the given target works for the architecture: <>, on which we rely. When we last tested, this was not the case for aarch64: <> Next, follow the exact same steps explained at <>, but passing `-g` to every command as usual. diff --git a/build-doc b/build-doc index a485c49..5d514f8 100755 --- a/build-doc +++ b/build-doc @@ -1,2 +1,2 @@ #!/usr/bin/env bash -asciidoctor -o out/README.html README.adoc +asciidoctor -o out/README.html -v README.adoc