website: Change Googlesource links to GitHub
This patch changes the Googlesource links to point to
GitHub.
However, the Gerrit review associated links
(i.e. gem5-review.googlesource.com) have been
unchanged.
Change-Id: Ic704c2011d914fb3d646c866e39be03cdee2dbb3
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5-website/+/71720
Tested-by: Bobby Bruce <bbruce@ucdavis.edu>
Maintainer: Bobby Bruce <bbruce@ucdavis.edu>
Reviewed-by: Bobby Bruce <bbruce@ucdavis.edu>
diff --git a/README.md b/README.md
index 9d7e163..5e46696 100644
--- a/README.md
+++ b/README.md
@@ -14,8 +14,8 @@
using:
```
-git clone https://gem5.googlesource.com/public/gem5-website
-cd gem5-website
+git clone https://github.com/gem5/website.git
+cd website
bundle
jekyll serve --config _config.yml,_config_dev.yml
```
diff --git a/_includes/footer.html b/_includes/footer.html
index bd22d57..7615a5b 100755
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -14,7 +14,7 @@
<p>Docs</p>
<p><a href="{{ "/documentation" | prepend: site.baseurl }}">Documentation</a></p>
<p><a href="http://gem5.org/Documentation">Old Documentation</a></p>
- <p><a href="https://gem5.googlesource.com/public/gem5">Source</a></p>
+ <p><a href="https://github.com/gem5/gem5">Source</a></p>
<br></div>
<div class="col-12 col-sm-4">
diff --git a/_pages/contributing.md b/_pages/contributing.md
index e066390..d2a87d7 100644
--- a/_pages/contributing.md
+++ b/_pages/contributing.md
@@ -7,7 +7,7 @@
This document serves as a beginners guide to contributing to gem5. If questions
arise while following this guide, we advise consulting [CONTRIBUTING.md](
-https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/CONTRIBUTING.md)
+https://github.com/gem5/gem5/blob/stable/CONTRIBUTING.md)
which contains more details on how to contribute to gem5.
The following subsections outline, in order, the steps involved in contributing
@@ -37,15 +37,15 @@
## Obtaining the git repo
-The gem5 git repository is hosted at <https://gem5.googlesource.com>.
-**Please note: contributions made to other gem5 repos (e.g., our GitHub mirror)
-will not be considered. Please contribute to <https://gem5.googlesource.com>
+The gem5 git repository is hosted at <https://github.com/gem5/gem5>.
+**Please note: contributions made to other gem5 repos
+will not be considered. Please contribute to <https://github.com/gem5/gem5>
exclusively.**
To pull the gem5 git repo:
```Shell
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
```
### stable / develop branch
@@ -245,7 +245,7 @@
the "header". The header starts with a tag (or tags, separated by a comma),
then a colon. Which tags are used depend on which components of gem5
you have modified. **Please refer to the [MAINTAINERS.yaml](
-https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/MAINTAINERS.yaml) for
+https://github.com/gem5/gem5/blob/stable/MAINTAINERS.yaml) for
a comprehensive list of accepted tags**. After this colon a short description
of the commit must be provided. **This header line must not exceed 65
characters**.
@@ -317,7 +317,7 @@
components you have modified should be added as reviewers. These should
correspond to the tags you included in the commit header. **Please consult
[MAINTAINERS.yaml](
-https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/MAINTAINERS.yaml) to
+https://github.com/gem5/gem5/blob/stable/MAINTAINERS.yaml) to
see who maintains which component**. As an example, for a commit with a header
of `tests,arch : This is testing the arch component` then the maintainers for
both `tests` and `arch` should be included as reviewers.
diff --git a/_pages/documentation/gem5-stdlib/0-overview.md b/_pages/documentation/gem5-stdlib/0-overview.md
index ebbc4f8..ccc8d27 100644
--- a/_pages/documentation/gem5-stdlib/0-overview.md
+++ b/_pages/documentation/gem5-stdlib/0-overview.md
@@ -10,11 +10,11 @@
## An overview of the gem5 standard library
Similar to standard libraries in programming languages, the gem5 standard library is designed to provide users of gem5 with commonly used components, features, and functionality with the goal of improving their productivity.
-The gem5 stdlib was introduced in [v21.1](https://gem5.googlesource.com/public/gem5/+/refs/tags/v21.1.0.0) in an alpha-release state (then referred to as "gem5 components"), and has been fully released as of [v21.2](https://gem5.googlesource.com/public/gem5/+/refs/tags/v21.2.0.0).
+The gem5 stdlib was introduced in [v21.1](https://github.com/gem5/gem5/tree/v21.1.0.0) in an alpha-release state (then referred to as "gem5 components"), and has been fully released as of [v21.2](https://github.com/gem5/gem5/tree/v21.2.0.0).
For users new to the gem5 standard library, the following tutorials may be of help in understanding how the gem5 stdlib may be used to improve the creation of gem5 simulations.
They include a tutorial on building syscall emulation and full-system simulations, as well as a guide on how to extend the library and contribute.
-The [`configs/examples/gem5_library`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/example/gem5_library/) directory in the gem5 repository also contains example scripts which use the library.
+The [`configs/examples/gem5_library`](https://github.com/gem5/gem5/tree/stable/configs/example/gem5_library) directory in the gem5 repository also contains example scripts which use the library.
The following subsections give a broad overview of the gem5 stdlib packages and what there intended purposes are.
@@ -103,9 +103,7 @@
This will obtain the `riscv-disk-img` resource and store it locally for use in a gem5 simulation.
-The resources package references the [`resources.json` file](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/resources.json) in the [gem5-resources repository](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable) to get info on what resources are available and where they may be downloaded from.
-While this is a machine-readable JSON file, users may use it to lookup the resources available.
-**We hope in the near future to have a website which renders this in a more human-readable manner**.
+The resources package references the resources that are available to view at the [gem5 Resources website](https://resources.gem5.org) and the [gem5 Resources repository](https://github.com/gem5/gem5-resources). The website is strongly recommended to get info on what resources are available and where they may be downloaded from.
## The Simulate package
diff --git a/_pages/documentation/gem5-stdlib/1-tutorial-hello-world.md b/_pages/documentation/gem5-stdlib/1-tutorial-hello-world.md
index 4a22ed1..7856fe0 100644
--- a/_pages/documentation/gem5-stdlib/1-tutorial-hello-world.md
+++ b/_pages/documentation/gem5-stdlib/1-tutorial-hello-world.md
@@ -100,7 +100,8 @@
```
The `Resource` class takes a string which specifies which resource, from [gem5-resources](/documentation/general_docs/gem5_resources), is to be obtained for the simulation.
-All the gem5 resources are specified in the [gem5 resources `resources.json` file](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/resources.json).
+All the gem5 resources can be found on the [gem5 Resources website](https://resources.gem5.org).
+
If the resource is not present on the host system it'll be automatically downloaded.
In this example we are going to use the `x86-hello-64-static` resource;
an x86, 64-bit, statically compiled binary which will print "Hello World!" to stdout.
diff --git a/_pages/documentation/gem5-stdlib/2-tutorial-x86-fs.md b/_pages/documentation/gem5-stdlib/2-tutorial-x86-fs.md
index 80a0ded..d6db76d 100644
--- a/_pages/documentation/gem5-stdlib/2-tutorial-x86-fs.md
+++ b/_pages/documentation/gem5-stdlib/2-tutorial-x86-fs.md
@@ -152,7 +152,7 @@
Both these are obtainable from the gem5 resources repository.
Therefore, via the `Resource` class, we specify `x86-linux-kernel-5.4.49` for the Kernel (a Linux kernel, version 5.4.49, compiled to X86) and `x86-ubuntu-18.04-img` for the disk image (a disk image containing Ubuntu 18.04, for X86).
The `Resource` class will automatically retrieve these resources if they are not already present on the host system.
-**Note: If a user wishes to use their own resource (that is, a resource not prebuilt as part of gem5-resources), they may use the `CustomResource` and `CustomDiskImageResource` classes, included in the [resource module](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/python/gem5/resources/resource.py))**.
+**Note: If a user wishes to use their own resource (that is, a resource not prebuilt as part of gem5-resources), they may follow the tutorial [here](../general_docs/gem5_resources.md)**
The `x86-ubuntu-18.04-img` has been designed to boot the OS, automatically login, and run `m5 readfile`.
The `m5 readfile` will read a file and execute it.
diff --git a/_pages/documentation/gem5-stdlib/3-tutorial-developing-own-components.md b/_pages/documentation/gem5-stdlib/3-tutorial-developing-own-components.md
index 2dda145..d493e63 100644
--- a/_pages/documentation/gem5-stdlib/3-tutorial-developing-own-components.md
+++ b/_pages/documentation/gem5-stdlib/3-tutorial-developing-own-components.md
@@ -51,7 +51,7 @@
As with every abstract base class, there are virtual functions which must be implemented.
Once implemented the `UniqueCacheHierarchy` can be used in simulations.
-The `get_mem_side_port` and `get_cpu_side_port` are declared in the [AbstractClassicCacheHierarchy](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/python/gem5/components/cachehierarchies/classic/abstract_classic_cache_hierarchy.py), while `incorporate_cache` is declared in the [AbstractCacheHierarchy](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/python/gem5/components/cachehierarchies/abstract_cache_hierarchy.py)
+The `get_mem_side_port` and `get_cpu_side_port` are declared in the [AbstractClassicCacheHierarchy](https://github.com/gem5/gem5/blob/stable/src/python/gem5/components/cachehierarchies/classic/abstract_classic_cache_hierarchy.py), while `incorporate_cache` is declared in the [AbstractCacheHierarchy](https://github.com/gem5/gem5/blob/stable/src/python/gem5/components/cachehierarchies/abstract_cache_hierarchy.py)
The `get_mem_side_port` and `get_cpu_side_port` functions return a `Port` each.
As their name suggests, these are ports used by the board to access the cache hierarchy from the memory side and the cpu side.
@@ -61,7 +61,7 @@
The contents of this function will vary between cache hierarchy setups but will typically inspect the board it is connected to, and use the board's API to connect the cache hierarchy.
In this example we assume the user is looking to implement a private L1 cache hierarchy, consisting of a data cache and instruction cache for each CPU core.
-This has actually already been implemented in the gem5 stdlib as the [PrivateL1CacheHierarchy](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/python/gem5/components/cachehierarchies/classic/private_l1_cache_hierarchy.py), but for this example we shall duplicate the effort.
+This has actually already been implemented in the gem5 stdlib as the [PrivateL1CacheHierarchy](https://github.com/gem5/gem5/blob/stable/src/python/gem5/components/cachehierarchies/classic/private_l1_cache_hierarchy.py), but for this example we shall duplicate the effort.
First we start by implementing the `get_mem_side_port` and `get_cpu_side_port` functions:
diff --git a/_pages/documentation/gem5art/main/main_2_artifacts.md b/_pages/documentation/gem5art/main/main_2_artifacts.md
index 78be4c4..fdc45e5 100644
--- a/_pages/documentation/gem5art/main/main_2_artifacts.md
+++ b/_pages/documentation/gem5art/main/main_2_artifacts.md
@@ -57,7 +57,7 @@
inputs = [gem5_repo,],
documentation = '''
Default gem5 binary compiled for the X86 ISA.
- This was built from the main gem5 repo (gem5.googlesource.com) without
+ This was built from the main gem5 repo (github.com/gem5/gem5) without
any modifications. We recently updated to the current gem5 master
which has a fix for memory channel address striping.
'''
diff --git a/_pages/documentation/gem5art/tutorials/tutorial_1_boot.md b/_pages/documentation/gem5art/tutorials/tutorial_1_boot.md
index 8d05815..1a55fea 100644
--- a/_pages/documentation/gem5art/tutorials/tutorial_1_boot.md
+++ b/_pages/documentation/gem5art/tutorials/tutorial_1_boot.md
@@ -94,7 +94,7 @@
See the commands below:
```sh
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
cd gem5
git checkout v20.1.0.0
scons build/X86/gem5.opt -j8
@@ -104,12 +104,12 @@
```python
gem5_repo = Artifact.registerArtifact(
- command = 'git clone https://gem5.googlesource.com/public/gem5',
+ command = 'git clone https://github.com/gem5/gem5',
typ = 'git repo',
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 from googlesource and checked out v20.1.0.0'
+ documentation = 'cloned gem5 from github and checked out v20.1.0.0'
)
gem5_binary = Artifact.registerArtifact(
@@ -182,7 +182,7 @@
Let's use an example of kernel v5.4.49 to see how to compile the kernel.
-First, add a folder linux-configs to store linux kernel config files. The configuration files of interest are available [here](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/linux-kernel/).
+First, add a folder linux-configs to store linux kernel config files. The configuration files of interest are available [here](https://github.com/gem5/gem5-resources/tree/stable/src/linux-kernel).
Then, we will get the linux source and checkout the required linux version (e.g. v5.4.49 in this case).
```
@@ -304,12 +304,12 @@
```python
gem5_repo = Artifact.registerArtifact(
- command = 'git clone https://gem5.googlesource.com/public/gem5',
+ command = 'git clone https://github.com/gem5/gem5',
typ = 'git repo',
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 from googlesource and checked out v20.1.0.0'
+ documentation = 'cloned gem5 from github and checked out v20.1.0.0'
)
m5_binary = Artifact.registerArtifact(
diff --git a/_pages/documentation/gem5art/tutorials/tutorial_2_npb.md b/_pages/documentation/gem5art/tutorials/tutorial_2_npb.md
index 89680bf..b7021b7 100644
--- a/_pages/documentation/gem5art/tutorials/tutorial_2_npb.md
+++ b/_pages/documentation/gem5art/tutorials/tutorial_2_npb.md
@@ -105,10 +105,10 @@
## Building gem5
-Next clone gem5 from googlesource:
+Next clone gem5 from GitHub:
```sh
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
```
If you want to use the exact gem5 source that was used at the time of creating this tutorial you will have to checkout the relevant commit. If you want to try with the current version of gem5 at the time of reading this tutorial, you can ignore the git checkout command.
@@ -348,7 +348,7 @@
## Compiling the linux kernel
In this tutorial, we use one of the LTS (long term support) releases of linux kernel v4.19.83 with gem5 to run NAS parallel benchmarks.
-First, get the linux kernel config file from [here](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/linux-kernel/linux-configs/), and place it in npb-tests folder.
+First, get the linux kernel config file from [here](https://github.com/gem5/gem5-resources/tree/stable/src/linux-kernel/linux-configs), and place it in npb-tests folder.
Then, we will get the linux source of version 4.19.83:
```
@@ -372,7 +372,7 @@
Next, we need to add gem5 run scripts. We will do that in a folder named configs-npb-tests.
Get the run script named run_npb.py from [here](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/npb/configs/run_npb.py), and other system configuration files from
-[here]((https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/npb/configs/system/).
+[here](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/npb/configs/system/).
The main script `run_npb.py` expects following arguments:
@@ -469,12 +469,12 @@
```python
gem5_repo = Artifact.registerArtifact(
- command = 'git clone https://gem5.googlesource.com/public/gem5',
+ command = 'git clone https://github.com/gem5/gem5',
typ = 'git repo',
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 from googlesource and checked out v20.1.0.0'
+ documentation = 'cloned gem5 from github and checked out v20.1.0.0'
)
m5_binary = Artifact.registerArtifact(
diff --git a/_pages/documentation/gem5art/tutorials/tutorial_3_parsec.md b/_pages/documentation/gem5art/tutorials/tutorial_3_parsec.md
index 9027014..8d0f3a2 100644
--- a/_pages/documentation/gem5art/tutorials/tutorial_3_parsec.md
+++ b/_pages/documentation/gem5art/tutorials/tutorial_3_parsec.md
@@ -45,7 +45,7 @@
- configs-parsec-tests: gem5 run and configuration scripts to run PARSEC
- disk-image: contains packer script and template files used to build a disk image.
The built disk image will be stored in the same folder
-- gem5: gem5 [source code](https://gem5.googlesource.com/public/gem5) and the compiled binary
+- gem5: gem5 [source code](https://github.com/gem5/gem5) and the compiled binary
- linux-stable: linux kernel [source code](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git) used for full-system experiments
- config.4.19.83: linux kernel config file used for its compilation
- results: directory to store the results of the experiments (generated once gem5 jobs are executed)
@@ -418,7 +418,7 @@
gem5_repo = Artifact.registerArtifact(
command = '''
- git clone https://gem5.googlesource.com/public/gem5;
+ git clone https://github.com/gem5/gem5;
cd gem5;
git remote add darchr https://github.com/darchr/gem5;
git fetch darchr;
@@ -429,7 +429,7 @@
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 master branch from googlesource (Nov 18, 2019) and cherry-picked 2 commits from darchr/gem5'
+ documentation = 'cloned gem5 master branch from github (Nov 18, 2019) and cherry-picked 2 commits from darchr/gem5'
)
m5_binary = Artifact.registerArtifact(
diff --git a/_pages/documentation/gem5art/tutorials/tutorial_4_spec.md b/_pages/documentation/gem5art/tutorials/tutorial_4_spec.md
index de7ee89..f543c6a 100644
--- a/_pages/documentation/gem5art/tutorials/tutorial_4_spec.md
+++ b/_pages/documentation/gem5art/tutorials/tutorial_4_spec.md
@@ -11,14 +11,14 @@
# Tutorial: Run SPEC CPU 2017 / SPEC CPU 2006 Benchmarks in Full System Mode with gem5art
## Introduction
-In this tutorial, we will demonstrate how to utilize [gem5art](https://github.com/darchr/gem5art) and [gem5-resources](https://gem5.googlesource.com/public/gem5-resources/) to run [SPEC CPU 2017 benchmarks](https://www.spec.org/cpu2017/) in gem5 full system mode.
+In this tutorial, we will demonstrate how to utilize [gem5art](https://github.com/gem5/gem5/tree/stable/util/gem5art) and [gem5-resources](https://github.com/gem5/gem5-resources/tree/stable/) to run [SPEC CPU 2017 benchmarks](https://www.spec.org/cpu2017/) in gem5 full system mode.
The scripts in this tutorial work with gem5art v1.3.0, gem5 20.1.0.4, and gem5-resources 20.1.0.4.
The content of this tutorial is mostly for conducting SPEC CPU 2017 experiments.
However, due to the similarity of SPEC 2006 and SPEC 2017 resources, this tutorial also applies to conducting SPEC 2006 experiment by using `src/spec-2006` folder instead of `src/spec-2017` of gem5-resources.
### gem5-resources
-[gem5-resources](https://gem5.googlesource.com/public/gem5-resources/) is an actively maintained collections of gem5-related resources that are commonly used.
+[gem5-resources](https://github.com/gem5/gem5-resources/tree/stable/) is an actively maintained collections of gem5-related resources that are commonly used.
The resources include scripts, binaries and disk images for full system simulation of many commonly used benchmarks.
This tutorial will offer guidance in utilizing gem5-resources for full system simulation.
@@ -71,13 +71,13 @@
## Setting up the Experiment
In this part, we have two concurrent tasks: setting up the resources and documenting the process using gem5art.
-We will structure the [SPEC 2017 resources as laid out by gem5-resources](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/).
+We will structure the [SPEC 2017 resources as laid out by gem5-resources](https://github.com/gem5/gem5-resources/tree/stable/src/spec-2017/).
The script `launch_spec2017_experiment.py` will contain the documentation about the artifacts we create and will also serve as Python script that launches the experiment.
### Acquiring gem5-resources and Setting up the Experiment Folder
First, we clone the gem5-resource repo and check out the stable branch upto the `1fe56ffc94005b7fa0ae5634c6edc5e2cb0b7357` commit, which is the most recent version of gem5-resources that is compatible with gem5 20.1.0.4 as of March 2021.
```sh
-git clone https://gem5.googlesource.com/public/gem5-resources
+git clone https://github.com/gem5/gem5-resources
cd gem5-resources
git checkout 1fe56ffc94005b7fa0ae5634c6edc5e2cb0b7357
```
@@ -94,7 +94,7 @@
```sh
experiments_repo = Artifact.registerArtifact(
command = '''
- git clone https://gem5.googlesource.com/public/gem5-resources
+ git clone https://github.com/gem5/gem5-resources
cd gem5-resources
git checkout 1fe56ffc94005b7fa0ae5634c6edc5e2cb0b7357
cd src/spec-2017
@@ -107,7 +107,7 @@
cwd = './',
documentation = '''
local repo to run spec 2017 experiments with gem5 full system mode;
- resources cloned from https://gem5.googlesource.com/public/gem5-resources upto commit 1fe56ffc94005b7fa0ae5634c6edc5e2cb0b7357 of stable branch
+ resources cloned from https://github.com/gem5/gem5-resources upto commit 1fe56ffc94005b7fa0ae5634c6edc5e2cb0b7357 of stable branch
'''
)
```
@@ -143,7 +143,7 @@
In the root folder of the experiment,
```sh
-git clone -b v20.1.0.4 https://gem5.googlesource.com/public/gem5
+git clone -b v20.1.0.4 https://github.com/gem5/gem5
cd gem5
scons build/X86/gem5.opt -j8
```
@@ -154,7 +154,7 @@
```python
gem5_repo = Artifact.registerArtifact(
command = '''
- git clone -b v20.1.0.4 https://gem5.googlesource.com/public/gem5
+ git clone -b v20.1.0.4 https://github.com/gem5/gem5
cd gem5
scons build/X86/gem5.opt -j8
''',
@@ -279,7 +279,7 @@
### Obtaining a Compiled Linux Kernel that Works with gem5
The compiled Linux kernel binaries that is known to work with gem5 can be found here: [https://www.gem5.org/documentation/general_docs/gem5_resources/](https://www.gem5.org/documentation/general_docs/gem5_resources/).
-The Linux kernel configurations that are used to compile the Linux kernel binaries are documented and maintained in gem5-resources: [https://gem5.googlesource.com/public/gem5-resources/+/cee972a1727abd80924dad73d9f3b5cf0f13012d/src/linux-kernel/](https://gem5.googlesource.com/public/gem5-resources/+/cee972a1727abd80924dad73d9f3b5cf0f13012d/src/linux-kernel/).
+The Linux kernel configurations that are used to compile the Linux kernel binaries are documented and maintained in gem5-resources: [https://github.com/gem5/gem5-resources/tree/stable/src/linux-kernel/](https://github.com/gem5/gem5-resources/tree/stable/src/linux-kernel/).
The following command downloads the compiled Linux kernel of version 4.19.83.
In the root folder of the experiment,
diff --git a/_pages/documentation/gem5art/tutorials/tutorial_5_microbench.md b/_pages/documentation/gem5art/tutorials/tutorial_5_microbench.md
index 35f1146..600d303 100644
--- a/_pages/documentation/gem5art/tutorials/tutorial_5_microbench.md
+++ b/_pages/documentation/gem5art/tutorials/tutorial_5_microbench.md
@@ -23,7 +23,7 @@
This tutorial follows the following directory structure:
- configs-micro-tests: the base gem5 configuration to be used to run SE mode simulations
-- gem5: gem5 [source code](https://gem5.googlesource.com/public/gem5) and the compiled binary
+- gem5: gem5 [source code](https://github.com/gem5/gem5) and the compiled binary
- results: directory to store the results of the experiments (generated once gem5 jobs are executed)
- launch_micro_tests.py: gem5 jobs launch script (creates all of the needed artifacts as well)
@@ -71,7 +71,7 @@
First clone gem5 in your micro-tests repo:
```sh
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
cd gem5
```
@@ -184,7 +184,7 @@
)
gem5_repo = Artifact.registerArtifact(
- command = '''git clone https://gem5.googlesource.com/public/gem5;
+ command = '''git clone https://github.com/gem5/gem5;
cd gem5;
wget https://github.com/darchr/gem5/commit/38d07ab0251ea8f5181abc97a534bb60157b2b5d.patch;
git am 38d07ab0251ea8f5181abc97a534bb60157b2b5d.patch --reject;
@@ -193,7 +193,7 @@
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'git repo with gem5 cloned on Nov 22 from googlesource (patch applied to support mem vector port)'
+ documentation = 'git repo with gem5 cloned on Nov 22 from github (patch applied to support mem vector port)'
)
gem5_binary = Artifact.registerArtifact(
diff --git a/_pages/documentation/general_docs/apis.md b/_pages/documentation/general_docs/apis.md
index a651221..bf68460 100644
--- a/_pages/documentation/general_docs/apis.md
+++ b/_pages/documentation/general_docs/apis.md
@@ -47,7 +47,7 @@
http://doxygen.gem5.org/release/current/group__api__simobject.html). The
definitions of different API groups can be found in
[`src/doxygen/group_definitions.hh`](
-https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/doxygen/group_definitions.hh).
+https://github.com/gem5/gem5/blob/stable/src/doxygen/group_definitions.hh).
### Notes for developers
@@ -82,7 +82,7 @@
warning will be given at compilation time specifying which API to transition
to. The gem5 deprecated Python parameter APIs are wrapped with our [bespoke
`DeprecatedParam` class](
-https://gem5.googlesource.com/public/gem5/+/bd13e8e206e6c86581cf9afa904ef1060351a4b0/src/python/m5/params.py#2166).
+https://github.com/gem5/gem5/blob/bd13e8e206e6c86581cf9afa904ef1060351a4b0/src/python/m5/params.py#L2166).
Python parameters wrapped in this class will throw an warning when used and
specify which API to transition to.
@@ -167,14 +167,14 @@
```
[In recent revisions](
-https://gem5.googlesource.com/public/gem5/+/392c1ced53827198652f5eda58e1874246b024f4)
+https://github.com/gem5/gem5/tree/392c1ced53827198652f5eda58e1874246b024f4)
the terms `master` and `slave` have been replaced. Though, the `slave` and
`master` terminology are widely used, so much so we consider them part of the
old API. We therefore wish to deprecate this API is a safe manner while
changing `master` and `slave` with `cpu_side_ports` and `mem_side_ports`. To
do so we would maintain the `master` and `slave` variables but utilize our
[`DeprecatedParam` Class](
-https://gem5.googlesource.com/public/gem5/+/bd13e8e206e6c86581cf9afa904ef1060351a4b0/src/python/m5/params.py#2166)
+https://github.com/gem5/gem5/blob/bd13e8e206e6c86581cf9afa904ef1060351a4b0/src/python/m5/params.py#L2166)
to produce warnings when and if these deprecated variables are used. Working on
our example, we would produce the following:
diff --git a/_pages/documentation/general_docs/architecture_support/arm_implementation.md b/_pages/documentation/general_docs/architecture_support/arm_implementation.md
index 8505840..aed4cc9 100644
--- a/_pages/documentation/general_docs/architecture_support/arm_implementation.md
+++ b/_pages/documentation/general_docs/architecture_support/arm_implementation.md
@@ -20,7 +20,7 @@
### From gem5 v21.2
-The best way to get a synced version of Arm architectural features is to have a look at the [ArmExtension](https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/src/arch/arm/ArmSystem.py) enum
+The best way to get a synced version of Arm architectural features is to have a look at the [ArmExtension](https://github.com/gem5/gem5/blob/develop/src/arch/arm/ArmSystem.py) enum
used by the release object and the available example releases provided within the same file.
A user can choose one of the following options:
@@ -33,5 +33,5 @@
The best way to get a synced version of Arm architectural features is to have a look at Arm ID registers and boolean values:
-* [src/arch/arm/ArmISA.py](https://gem5.googlesource.com/public/gem5/+/refs/tags/v21.1.0.2/src/arch/arm/ArmISA.py)
-* [src/arch/arm/ArmSystem.py](https://gem5.googlesource.com/public/gem5/+/refs/tags/v21.1.0.2/src/arch/arm/ArmSystem.py)
+* [src/arch/arm/ArmISA.py](https://github.com/gem5/gem5/blob/v21.1.0.2/src/arch/arm/ArmISA.py)
+* [src/arch/arm/ArmSystem.py](https://github.com/gem5/gem5/blob/v21.1.0.2/src/arch/arm/ArmSystem.py)
diff --git a/_pages/documentation/general_docs/building/extras.md b/_pages/documentation/general_docs/building/extras.md
index 69cd285..0307905 100644
--- a/_pages/documentation/general_docs/building/extras.md
+++ b/_pages/documentation/general_docs/building/extras.md
@@ -12,7 +12,7 @@
The main drawback of the EXTRAS feature is that, by itself, it only supports adding code to gem5, not modifying any of the base gem5 code.
-One use of the EXTRAS feature is to support EIO traces. The trace reader for EIO is licensed under the SimpleScalar license, and due to the incompatibility of that license with gem5's BSD license, the code to read these traces is not included in the gem5 distribution. Instead, the EIO code is distributed via a separate "encumbered" [repository](https://gem5.googlesource.com/public/gem5).
+One use of the EXTRAS feature is to support EIO traces. The trace reader for EIO is licensed under the SimpleScalar license, and due to the incompatibility of that license with gem5's BSD license, the code to read these traces is not included in the gem5 distribution. Instead, the EIO code is distributed via a separate "encumbered" [repository](https://github.com/gem5/gem5).
The following examples show how to compile the EIO code. By adding to or modifying the extras path, any other suitable extra could be compiled in. To compile in code using EXTRAS simply execute the following
diff --git a/_pages/documentation/general_docs/building/index.md b/_pages/documentation/general_docs/building/index.md
index a87b1e0..32e910e 100644
--- a/_pages/documentation/general_docs/building/index.md
+++ b/_pages/documentation/general_docs/building/index.md
@@ -93,22 +93,22 @@
Ubuntu 22.04 with all optional dependencies:
[gcr.io/gem5-test/ubuntu-22.04_all-dependencies:v22-1](
https://gcr.io/gem5-test/ubuntu-22.04_all-dependencies:v22-1) ([source Dockerfile](
-https://gem5.googlesource.com/public/gem5/+/refs/tags/v22.1.0.0/util/dockerfiles/ubuntu-22.04_all-dependencies/Dockerfile)).
+https://github.com/gem5/gem5/blob/v22.1.0.0/util/dockerfiles/ubuntu-22.04_all-dependencies/Dockerfile)).
Ubuntu 22.04 with minimum dependencies:
[gcr.io/gem5-test/ubuntu-22.04_min-dependencies:v22-1](
https://gcr.io/gem5-test/ubuntu-22.04_min-dependencies:v22-1) ([source Dockerfile](
-https://gem5.googlesource.com/public/gem5/+/refs/tags/v22.1.0.0/util/dockerfiles/ubuntu-22.04_min-dependencies/Dockerfile)).
+https://github.com/gem5/gem5/blob/v22.1.0.0/util/dockerfiles/ubuntu-22.04_min-dependencies/Dockerfile)).
Ubuntu 20.04 with all optional dependencies:
[gcr.io/gem5-test/ubuntu-20.04_all-dependencies:v22-1](
https://gcr.io/gem5-test/ubuntu-20.04_all-dependencies:v22-1) ([source Dockerfile](
-https://gem5.googlesource.com/public/gem5/+/refs/tags/v22.1.0.0/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile)).
+https://github.com/gem5/gem5/blob/v22.1.0.0/util/dockerfiles/ubuntu-20.04_all-dependencies/Dockerfile)).
Ubuntu 18.04 with all optional dependencies:
[gcr.io/gem5-test/ubuntu-18.04_all-dependencies:v22-1](
https://gcr.io/gem5-test/ubuntu-18.04_all-dependencies:v22-1) ([source Dockerfile](
-https://gem5.googlesource.com/public/gem5/+/refs/tags/v22.1.0.0/util/dockerfiles/ubuntu-18.04_all-dependencies/Dockerfile)).
+https://github.com/gem5/gem5/blob/v22.1.0.0/util/dockerfiles/ubuntu-18.04_all-dependencies/Dockerfile)).
@@ -140,7 +140,7 @@
## Getting the code
```
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
```
## Building with SCons
diff --git a/_pages/documentation/general_docs/developement/release_procedures.md b/_pages/documentation/general_docs/developement/release_procedures.md
index 3922621..4caa828 100644
--- a/_pages/documentation/general_docs/developement/release_procedures.md
+++ b/_pages/documentation/general_docs/developement/release_procedures.md
@@ -6,12 +6,12 @@
permalink: /documentation/general_docs/development/release_procedures/
---
-Information on when releases are carried out, how the community is notified, versioning information, and how to contribute to a release can be found in our [CONTRIBUTING.md document](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/CONTRIBUTING.md#releases).
+Information on when releases are carried out, how the community is notified, versioning information, and how to contribute to a release can be found in our [CONTRIBUTING.md document](https://github.com/gem5/gem5/blob/stable/CONTRIBUTING.md#releases).
The purpose of this document is to outline specific procedures carried out during a release.
## gem5 repository
-The [gem5 git repository](https://gem5.googlesource.com/public/gem5/) has two branches, [stable](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable) and [develop](https://gem5.googlesource.com/public/gem5/+/refs/heads/develop).
+The [gem5 git repository](https://github.com/gem5/gem5) has two branches, [stable](https://github.com/gem5/gem5/tree/stable) and [develop](https://github.com/gem5/gem5/tree/develop).
The HEAD of the stable branch is the latest official release of gem5 and will be tagged as such.
Users are not permitted to submit patches to the stable branch, and instead submit patches to the develop branch.
At least two weeks prior to a release a staging branch is created from the develop branch.
@@ -22,11 +22,11 @@
* The `-werror` is removed.
This ensures that gem5 compiles on newer compilers as new/stricter compiler warnings are incorporated.
For example: <https://gem5-review.googlesource.com/c/public/gem5/+/43425>.
-* The [Doxygen "Project Number" field](https://gem5.googlesource.com/public/gem5/+/refs/tags/v21.0.1.0/src/Doxyfile#34) is updated to the version ID.
+* The [Doxygen "Project Number" field](https://github.com/gem5/gem5/blob/v21.0.1.0/src/Doxyfile#34) is updated to the version ID.
For example: <https://gem5-review.googlesource.com/c/public/gem5/+/47079>.
-* The [`src/base/version.cc`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/src/base/version.cc) file is updated to state the version ID.
+* The [`src/base/version.cc`](https://github.com/gem5/gem5/blob/stable/src/base/version.cc) file is updated to state the version ID.
For example: <https://gem5-review.googlesource.com/c/public/gem5/+/47079>.
-* The [`ext/testlib/configuration.py`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/ext/testlib/configuration.py) file's `default.resource_url` field is updated to point towards the correct Google Cloud release bucket (see [the Cloud Bucket release procedures](#gem5-resources-google-cloud-bucket)).
+* The [`ext/testlib/configuration.py`](https://github.com/gem5/gem5/blob/stable/ext/testlib/configuration.py) file's `default.resource_url` field is updated to point towards the correct Google Cloud release bucket (see [the Cloud Bucket release procedures](#gem5-resources-google-cloud-bucket)).
For example: <https://gem5-review.googlesource.com/c/public/gem5/+/44725>.
* The Resource downloader, `src/python/gem5/resources/downloader.py`, has a function `def _resources_json_version_required()`. This must be updated to the correct version of the `resources.json` file to use (see the [gem5 resources repository release procedures](#gem5-resources-repository)) for more information on this).
* The `tests/weekly.sh`, `tests/nightly.sh`, `tests/compiler-tests.sh`, and `tests/jenkins/presubmit.sh` should be updated ensure they remain stable across different gem5 releases. This is achieved by:
@@ -43,7 +43,7 @@
2. The stable branch is tagged with the latest release version id at its HEAD.
* For example, `git tag -a v21.1.0.0 -m "gem5 version 21.1.0.0" && git push --tags`
-The [RELEASE-NOTES.md](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/RELEASE-NOTES.md) should be updated to notify the community of the major changes in this release.
+The [RELEASE-NOTES.md](https://github.com/gem5/gem5/blob/stable/RELEASE-NOTES.md) should be updated to notify the community of the major changes in this release.
This can be done on the develop branch prior to the creation of the staging branch, or on the staging branch.
It has been customary to create a blog post on <http://www.gem5.org> outlining the release.
While appreciated, it is not mandatory.
@@ -54,7 +54,7 @@
## gem5 resources repository
-The [gem5 resources git repository](https://gem5.googlesource.com/public/gem5-resources) has two branches, [stable](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable) and [develop](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/develop).
+The [gem5 resources git repository](https://github.com/gem5/gem5-resources) has two branches, [stable](https://github.com/gem5/gem5-resources/tree/stable) and [develop](https://github.com/gem5/gem5-resources/tree/develop).
The HEAD of the stable branch contains the source for resources with known compatibility to the most recently release of gem5.
E.g., if the current release of gem5 is v22.3, the head of gem5 resources repository will contain the source for resources with known compatibility with v22.3.
The develop branch contains sources compatible with the develop branch of the gem5 repository.
@@ -85,7 +85,7 @@
The built gem5 resources are found within the gem5 Google Cloud Bucket.
The [gem5 resources git repository](#gem5-resources-repository) contains sources of the gem5 resources, these are then compiled and stored in the Google Cloud Bucket.
-The gem5 resources repo [README.md](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/README.md) contains links to download the built resources from the Google Cloud Bucket.
+The gem5 resources repo [README.md](https://github.com/gem5/gem5-resources/blob/stable/README.md) contains links to download the built resources from the Google Cloud Bucket.
The Google Cloud Bucket, like the gem5 resources repository, is versioned.
Each resource is stored under `http://dist.gem5.org/dist/{major version}`.
@@ -109,9 +109,9 @@
## The docker images
-Currently hosted in [`util/dockerfiles`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/util/dockerfiles/) in the gem5 repository, we have a series of Dockerfiles which can be built to produce environments in which gem5 can be built and run.
+Currently hosted in [`util/dockerfiles`](https://github.com/gem5/gem5/tree/stable/util/dockerfiles/) in the gem5 repository, we have a series of Dockerfiles which can be built to produce environments in which gem5 can be built and run.
These images are mostly used for testing purposes.
-The [`ubuntu-20.04_all-dependencies`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/util/dockerfiles/ubuntu-20.04_all-dependencies/) Dockerfile is the one most suitable for users who wish to build and execute gem5 in a supported environment.
+The [`ubuntu-20.04_all-dependencies`](https://github.com/gem5/gem5/tree/stable/util/dockerfiles/ubuntu-20.04_all-dependencies/) Dockerfile is the one most suitable for users who wish to build and execute gem5 in a supported environment.
We provide pre-built Docker images, hosted at <gcr.io/gem5-test>.
All the Dockerfiles found in `util/dockerfiles` have been built and stored there.
@@ -132,7 +132,7 @@
## gem5 website repository
-The [gem5 website git repository](https://gem5.googlesource.com/public/gem5-website/) has two branches, [stable](https://gem5.googlesource.com/public/gem5-website/+/refs/heads/stable) and [develop](https://gem5.googlesource.com/public/gem5-website/+/refs/heads/develop).
+The [gem5 website git repository](https://github.com/gem5/website/) has two branches, [stable](https://github.com/gem5/website/tree/stable) and [develop](https://github.com/gem5/website/tree/develop).
The stable branch is what is built and viewable at <http://www.gem5.org>, and is up-to-date with the current gem5 release.
E.g., if the current release of gem5, on its stable branch, is `v20.1`, the documentation on the stable branch will related to `v20.1`.
The develop branch contains the state of the website for the upcoming gem5 release.
@@ -201,7 +201,7 @@
gsutil -m cp -r gs://doxygen.gem5.org/release/current gs://doxygen.gem5.org/release/{version id}
```
-The final step is to add a link to this gem5 Doxygen version on the website, via the [`_data/documentation.yml` file](https://gem5.googlesource.com/public/gem5-website/+/refs/heads/stable/_data/documentation.yml).
+The final step is to add a link to this gem5 Doxygen version on the website, via the [`_data/documentation.yml` file](https://github.com/gem5/website/blob/stable/_data/documentation.yml).
For example: <https://gem5-review.googlesource.com/c/public/gem5-website/+/43385>.
diff --git a/_pages/documentation/general_docs/gpu_models/gcn3.md b/_pages/documentation/general_docs/gpu_models/gcn3.md
index 15c2280..8e4467f 100644
--- a/_pages/documentation/general_docs/gpu_models/gcn3.md
+++ b/_pages/documentation/general_docs/gpu_models/gcn3.md
@@ -20,9 +20,9 @@
Currently, the GCN3 GPU model in gem5 is supported on the stable and develop branch.
-The [gem5 repository](https://gem5.googlesource.com/public/gem5) comes with a dockerfile located in `util/dockerfiles/gcn-gpu/`. This dockerfile contains the drivers and libraries needed to run the GPU model. A pre-built version of the docker image is hosted at `gcr.io/gem5-test/gcn-gpu:v22-0`.
+The [gem5 repository](https://github.com/gem5/gem5) comes with a dockerfile located in `util/dockerfiles/gcn-gpu/`. This dockerfile contains the drivers and libraries needed to run the GPU model. A pre-built version of the docker image is hosted at `gcr.io/gem5-test/gcn-gpu:v22-0`.
-The [gem5-resources repository](https://gem5.googlesource.com/public/gem5-resources/) also comes with a number of sample applications that can be used to verify that the model runs correctly. We recommend users start with [square](https://resources.gem5.org/resources/square), as it is a simple, heavily tested application that should run relatively quickly.
+The [gem5-resources repository](https://github.com/gem5/gem5-resources/) also comes with a number of sample applications that can be used to verify that the model runs correctly. We recommend users start with [square](https://resources.gem5.org/resources/square), as it is a simple, heavily tested application that should run relatively quickly.
#### Using the image
The docker image can either be built or pulled from gcr.io.
@@ -41,10 +41,10 @@
You can also put `gcr.io/gem5-test/gcn-gpu:v22-0` as the image in the docker run command without pulling beforehand and it will be pulled automatically.
#### Building gem5 using the image
-See square in [gem5 resources](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/gpu/square/) for an example of how to build gem5 in the docker. Note: these directions assume you are pulling the latest image automatically.
+See square in [gem5 resources](https://github.com/gem5/gem5-resources/tree/stable/src/gpu/square/) for an example of how to build gem5 in the docker. Note: these directions assume you are pulling the latest image automatically.
#### Building & running a GPU application using the image
-See [gem5 resources](https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/gpu) for examples of how to build and run GPU applications in the docker.
+See [gem5 resources](https://github.com/gem5/gem5-resources/tree/stable/src/gpu/) for examples of how to build and run GPU applications in the docker.
## **ROCm**
diff --git a/_pages/documentation/general_docs/statistics/stats-api.md b/_pages/documentation/general_docs/statistics/stats-api.md
index b9f86bc..540e126 100644
--- a/_pages/documentation/general_docs/statistics/stats-api.md
+++ b/_pages/documentation/general_docs/statistics/stats-api.md
@@ -485,7 +485,7 @@
- Updating the class constructors to initialize `Stats::Group` variable. Usually, it's adding `stats(this)` to the constructors assuming the name of the variable is `stats`.
Some examples,
- - An example of `Stats::Group` declaration is [here](https://gem5.googlesource.com/public/gem5/+/refs/tags/v20.0.0.3/src/cpu/testers/traffic_gen/base.hh#194).
+ - An example of `Stats::Group` declaration is [here](https://github.com/gem5/gem5/blob/v20.0.0.3/src/cpu/testers/traffic_gen/base.hh#L194).
Note that all variables of type starting with `Stats::` have been moved to the struct.
- - An example of a `Stats::Group` constructor that utilizes `ADD_STAT` is [here](https://gem5.googlesource.com/public/gem5/+/refs/tags/v20.0.0.3/src/cpu/testers/traffic_gen/base.cc#332).
- - In the case where a stat variable requiring additional initializations other than `name` and `description`, you can follow [this example](https://gem5.googlesource.com/public/gem5/+/refs/tags/v20.0.0.3/src/mem/comm_monitor.cc#105).
+ - An example of a `Stats::Group` constructor that utilizes `ADD_STAT` is [here](https://github.com/gem5/gem5/blob/v20.0.0.3/src/cpu/testers/traffic_gen/base.cc#L332).
+ - In the case where a stat variable requiring additional initializations other than `name` and `description`, you can follow [this example](https://github.com/gem5/gem5/blob/v20.0.0.3/src/mem/comm_monitor.cc#L105).
diff --git a/_pages/documentation/learning_gem5/part0_introduction.md b/_pages/documentation/learning_gem5/part0_introduction.md
index e90e86c..855e040 100644
--- a/_pages/documentation/learning_gem5/part0_introduction.md
+++ b/_pages/documentation/learning_gem5/part0_introduction.md
@@ -31,7 +31,7 @@
before using it.
You can find the source for this book at
-<https://gem5.googlesource.com/public/gem5-website/+/refs/heads/stable/_pages/documentation/learning_gem5/>.
+<https://github.com/gem5/website/tree/stable/_pages/documentation/learning_gem5/>.
## What is gem5?
diff --git a/_pages/documentation/learning_gem5/part1/part1_1_building.md b/_pages/documentation/learning_gem5/part1/part1_1_building.md
index 5a3a3f9..a94c18b 100644
--- a/_pages/documentation/learning_gem5/part1/part1_1_building.md
+++ b/_pages/documentation/learning_gem5/part1/part1_1_building.md
@@ -95,7 +95,7 @@
to clone the repository, use the `git clone` command.
```
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
```
You can now change directories to `gem5` which contains all of the gem5
diff --git a/_pages/documentation/learning_gem5/part1/part1_2_simple_config.md b/_pages/documentation/learning_gem5/part1/part1_2_simple_config.md
index 4cee564..86a9634 100644
--- a/_pages/documentation/learning_gem5/part1/part1_2_simple_config.md
+++ b/_pages/documentation/learning_gem5/part1/part1_2_simple_config.md
@@ -317,7 +317,7 @@
Now that we've created a simple simulation script (the full version of
which can be found in the gem5 code base at
-[configs/learning\_gem5/part1/simple.py](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part1/simple.py)
+[configs/learning\_gem5/part1/simple.py](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part1/simple.py)
) we're ready to run gem5. gem5 can take many parameters, but requires just
one positional argument, the simulation script. So, we can simply run gem5
from the root gem5 directory as:
diff --git a/_pages/documentation/learning_gem5/part1/part1_3_cache_config.md b/_pages/documentation/learning_gem5/part1/part1_3_cache_config.md
index 9f14eef..b4846f8 100644
--- a/_pages/documentation/learning_gem5/part1/part1_3_cache_config.md
+++ b/_pages/documentation/learning_gem5/part1/part1_3_cache_config.md
@@ -180,7 +180,7 @@
```
The full file can be found in the gem5 source at
-[`configs/learning_gem5/part1/caches.py`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part1/caches.py).
+[`configs/learning_gem5/part1/caches.py`](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part1/caches.py).
Adding caches to the simple config file
------------------------------------
@@ -254,7 +254,7 @@
two-level cache hierarchy. If you run the current file, `hello`
should now finish in 57467000 ticks. The full script can
be found in the gem5 source at
-[`configs/learning_gem5/part1/two_level.py`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part1/two_level.py).
+[`configs/learning_gem5/part1/two_level.py`](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part1/two_level.py).
Adding parameters to your script
--------------------------------
@@ -391,5 +391,5 @@
Exiting @ tick 57467000 because exiting with last active thread context
The full scripts can be found in the gem5 source at
-[`configs/learning_gem5/part1/caches.py`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part1/caches.py) and
-[`configs/learning_gem5/part1/two_level.py`](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part1/two_level.py).
+[`configs/learning_gem5/part1/caches.py`](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part1/caches.py) and
+[`configs/learning_gem5/part1/two_level.py`](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part1/two_level.py).
diff --git a/_pages/documentation/learning_gem5/part3/part3_08_configuration.md b/_pages/documentation/learning_gem5/part3/part3_08_configuration.md
index c6bed44..360a949 100644
--- a/_pages/documentation/learning_gem5/part3/part3_08_configuration.md
+++ b/_pages/documentation/learning_gem5/part3/part3_08_configuration.md
@@ -42,7 +42,7 @@
system and the memory controllers.
You can download the complete run script
-[here](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part3/simple_ruby.py).
+[here](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part3/simple_ruby.py).
### Cache system configuration
@@ -337,4 +337,4 @@
```
You can download the complete `msi_caches.py` file
-[here](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part3/msi_caches.py).
+[here](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part3/msi_caches.py).
diff --git a/_pages/documentation/learning_gem5/part3/part3_11_simple-MI_example.md b/_pages/documentation/learning_gem5/part3/part3_11_simple-MI_example.md
index c11be46..03d1325 100644
--- a/_pages/documentation/learning_gem5/part3/part3_11_simple-MI_example.md
+++ b/_pages/documentation/learning_gem5/part3/part3_11_simple-MI_example.md
@@ -22,7 +22,7 @@
the classes needed for `MI_example`. There are only a couple of changes
from `MSI`, mostly due to different naming schemes. You can download the
file
-[here](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/configs/learning_gem5/part3/ruby_caches_MI_example.py).
+[here](https://github.com/gem5/gem5/blob/stable/configs/learning_gem5/part3/ruby_caches_MI_example.py).
```python
class MyCacheSystem(RubySystem):
diff --git a/_pages/documentation/reporting_problems.md b/_pages/documentation/reporting_problems.md
index f1c7903..83bf15c 100644
--- a/_pages/documentation/reporting_problems.md
+++ b/_pages/documentation/reporting_problems.md
@@ -28,7 +28,7 @@
[Jira Issue Tracking system](https://gem5.atlassian.net).
2. Ensure you're compiling and running the latest version of [gem5](
-https://gem5.googlesource.com). The issue may have already been resolved.
+https://github.com/gem5/gem5). The issue may have already been resolved.
3. Check changes [currently under review on our Gerrit system](
https://gem5-review.googlesource.com/dashboard/self). It's possible a fix to
@@ -77,5 +77,5 @@
If your issue is with the content of a gem5 document/tutorial being incorrect,
then please consider submitting a change. Please consult our [README](
-https://gem5.googlesource.com/public/gem5-website/+/refs/heads/stable/README.md)
+https://github.com/gem5/website/blob/stable/README.md)
for more information on how to make contributions to the gem5 website.
diff --git a/_pages/getting_started.md b/_pages/getting_started.md
index 983639d..0e0c0f7 100644
--- a/_pages/getting_started.md
+++ b/_pages/getting_started.md
@@ -14,12 +14,10 @@
To download gem5, you can use [`git`](https://git-scm.com/) to checkout to current stable branch.
If you're not familiar with version control or git, The [git book](https://git-scm.com/book/en/v2) (available online for free) is a great way to learn more about git and become more comfortable using version control.
-The canonical version of gem5 is hosted by Google on googlesource.com.
-However, there is a [GitHub mirror](https://github.com/gem5/gem5) as well.
-It is strongly suggested to use the googlesource version of gem5, and it is required if you want to [contribute any changes](/contributing) back to the gem5 mainline.
+The canonical version of gem5 is hosted on [GitHub](https://github.com/gem5/gem5).
```
-git clone https://gem5.googlesource.com/public/gem5
+git clone https://github.com/gem5/gem5
```
After cloning the source code, you can build gem5 by using [`scons`](https://scons.org/).
@@ -95,7 +93,7 @@
```
You should also specify the **version** of gem5 you use in your methodology section.
-If you didn't use a specific stable version of gem5 (e.g., gem5-20.1.3), you should state the commit hash *as shown on https:/gem5.googlesource.com/*.
+If you didn't use a specific stable version of gem5 (e.g., gem5-20.1.3), you should state the commit hash *as shown on https://github.com/gem5/gem5*.
If you use the GPU model, the DRAM model, or any of the other models in gem5 that have been [published](/publications/), you're encouraged to cite those works as well.
See [the publications page](/publications/) for a list of models that have been contributed to gem5 beyond the original paper.
diff --git a/_pages/governance.md b/_pages/governance.md
index d6cd03b..9165f7f 100644
--- a/_pages/governance.md
+++ b/_pages/governance.md
@@ -108,7 +108,7 @@
The project management committee consists of those individuals identified as ‘project owners’ on the development site. The PMC has additional responsibilities over and above those of a committer. These responsibilities ensure the smooth running of the project. PMC members are expected to review code contributions, participate in strategic planning, approve changes to the governance model and manage how the software is distributed and licensed.
-Some PMC members are responsible for specific components of the gem5 project. This includes gem5 source modules (e.g., classic caches, O3CPU model, etc.) and project assets (e.g., the website). A list of the current components and the responsible members can be found within the [MAINTAINERS](https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/MAINTAINERS.yaml) document.
+Some PMC members are responsible for specific components of the gem5 project. This includes gem5 source modules (e.g., classic caches, O3CPU model, etc.) and project assets (e.g., the website). A list of the current components and the responsible members can be found within the [MAINTAINERS](https://github.com/gem5/gem5/blob/stable/MAINTAINERS.yaml) document.
Members of the PMC do not have significant authority over other members of the community, although it is the PMC that votes on new committers. It also makes decisions when community consensus cannot be reached. In addition, the PMC has access to the project’s private mailing list. This list is used for sensitive issues, such as votes for new committers and legal matters that cannot be discussed in public. It is never used for project management or planning.
diff --git a/assets/files/gem5art-launch-scripts/launch_boot_tests.py b/assets/files/gem5art-launch-scripts/launch_boot_tests.py
index 24dd837..5fab079 100755
--- a/assets/files/gem5art-launch-scripts/launch_boot_tests.py
+++ b/assets/files/gem5art-launch-scripts/launch_boot_tests.py
@@ -33,12 +33,12 @@
documentation = 'main experiments repo to run full system boot tests with gem5 20.1'
)
gem5_repo = Artifact.registerArtifact(
- command = 'git clone https://gem5.googlesource.com/public/gem5',
+ command = 'git clone https://github.com/gem5/gem5',
typ = 'git repo',
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 from googlesource and checked out release-staging-v20.1.0.0 (Sep 14, 2020)'
+ documentation = 'cloned gem5 from github and checked out release-staging-v20.1.0.0 (Sep 14, 2020)'
)
m5_binary = Artifact.registerArtifact(
diff --git a/assets/files/gem5art-launch-scripts/launch_micro_tests.py b/assets/files/gem5art-launch-scripts/launch_micro_tests.py
index fbca44e..a351832 100755
--- a/assets/files/gem5art-launch-scripts/launch_micro_tests.py
+++ b/assets/files/gem5art-launch-scripts/launch_micro_tests.py
@@ -20,7 +20,7 @@
)
gem5_repo = Artifact.registerArtifact(
- command = '''git clone https://gem5.googlesource.com/public/gem5;
+ command = '''git clone https://github.com/gem5/gem5;
cd gem5;
wget https://github.com/darchr/gem5/commit/38d07ab0251ea8f5181abc97a534bb60157b2b5d.patch;
git am 38d07ab0251ea8f5181abc97a534bb60157b2b5d.patch --reject;
@@ -29,7 +29,7 @@
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'git repo with gem5 cloned on Nov 22 from googlesource (patch applied to support mem vector port)'
+ documentation = 'git repo with gem5 cloned on Nov 22 from github (patch applied to support mem vector port)'
)
gem5_binary = Artifact.registerArtifact(
diff --git a/assets/files/gem5art-launch-scripts/launch_npb_tests.py b/assets/files/gem5art-launch-scripts/launch_npb_tests.py
index 463976c..3c48eb7 100755
--- a/assets/files/gem5art-launch-scripts/launch_npb_tests.py
+++ b/assets/files/gem5art-launch-scripts/launch_npb_tests.py
@@ -29,12 +29,12 @@
)
gem5_repo = Artifact.registerArtifact(
- command = 'git clone https://gem5.googlesource.com/public/gem5',
+ command = 'git clone https://github.com/gem5/gem5',
typ = 'git repo',
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 from googlesource and checked out v20.1.0.0'
+ documentation = 'cloned gem5 from github and checked out v20.1.0.0'
)
m5_binary = Artifact.registerArtifact(
diff --git a/assets/files/gem5art-launch-scripts/launch_parsec_tests.py b/assets/files/gem5art-launch-scripts/launch_parsec_tests.py
index 1c761e8..7e90c3f 100644
--- a/assets/files/gem5art-launch-scripts/launch_parsec_tests.py
+++ b/assets/files/gem5art-launch-scripts/launch_parsec_tests.py
@@ -39,7 +39,7 @@
gem5_repo = Artifact.registerArtifact(
command = '''
- git clone https://gem5.googlesource.com/public/gem5;
+ git clone https://github.com/gem5/gem5;
cd gem5;
git remote add darchr https://github.com/darchr/gem5;
git fetch darchr;
@@ -50,7 +50,7 @@
name = 'gem5',
path = 'gem5/',
cwd = './',
- documentation = 'cloned gem5 master branch from googlesource (Nov 18, 2019) and cherry-picked 2 commits from darchr/gem5'
+ documentation = 'cloned gem5 master branch from github (Nov 18, 2019) and cherry-picked 2 commits from darchr/gem5'
)
m5_binary = Artifact.registerArtifact(
diff --git a/assets/files/gem5art-launch-scripts/launch_spec2006_experiments.py b/assets/files/gem5art-launch-scripts/launch_spec2006_experiments.py
index f8b0ae2..e56db15 100644
--- a/assets/files/gem5art-launch-scripts/launch_spec2006_experiments.py
+++ b/assets/files/gem5art-launch-scripts/launch_spec2006_experiments.py
@@ -17,7 +17,7 @@
gem5_repo = Artifact.registerArtifact(
command = '''
- git clone -b v19.0.0.0 https://gem5.googlesource.com/public/gem5
+ git clone -b v19.0.0.0 https://github.com/gem5/gem5
cd gem5
scons build/X86/gem5.opt -j8
''',
diff --git a/assets/files/gem5art-launch-scripts/launch_spec2017_experiments.py b/assets/files/gem5art-launch-scripts/launch_spec2017_experiments.py
index 16846e0..194a746 100644
--- a/assets/files/gem5art-launch-scripts/launch_spec2017_experiments.py
+++ b/assets/files/gem5art-launch-scripts/launch_spec2017_experiments.py
@@ -18,7 +18,7 @@
gem5_repo = Artifact.registerArtifact(
command = '''
- git clone -b v19.0.0.0 https://gem5.googlesource.com/public/gem5
+ git clone -b v19.0.0.0 https://github.com/gem5/gem5
cd gem5
scons build/X86/gem5.opt -j8
''',
diff --git a/index.html b/index.html
index f0c1a76..ca57364 100755
--- a/index.html
+++ b/index.html
@@ -18,7 +18,7 @@
</p>
<a href="{{ "/getting_started" | prepend: site.baseurl }}"><button type="button" class="btn btn-primary" href="">Get Started</button></a>
- <a href="https://gem5.googlesource.com/public/gem5"><button type="button" class="btn btn-outline-primary">Source</button></a>
+ <a href="https://github.com/gem5/gem5"><button type="button" class="btn btn-outline-primary">Source</button></a>
<a href="https://gem5-review.googlesource.com/"><button type="button" class="btn btn-outline-primary">Code Review</button></a>
<a href="https://arxiv.org/abs/2007.03152"><button type="button" class="btn btn-outline-primary">gem5-20+ paper</button></a>
<a href="https://join.slack.com/t/gem5-workspace/shared_invite/zt-1c8go4yjo-LNb7l~BZ0FagwmVxX08y9g"><button type="button" class="btn btn-outline-primary">Join our Slack</button></a>
