| commit | c7a5044e87da31cf4b4d8bb62a9c0f7ac639bdab | [log] [tgz] |
|---|---|---|
| author | Srikrishna Iyer <sriyer@google.com> | Thu Mar 25 21:47:56 2021 -0700 |
| committer | Srikrishna Iyer <46467186+sriyerg@users.noreply.github.com> | Fri Mar 26 11:46:58 2021 -0700 |
| tree | e3f4f33e0fb964e4f69f6062aef3af8da34aa1b0 | |
| parent | 4af433f77d4c5f3a5afe207e0909c89c3ad53ea0 [diff] |
[dvsim] Keep dependencies list This set of changes is aimed at retaining the dependency order across targets, even if the dependency is not scheduled to be run. The Deploy::dependencies list once constructed, remains untouched. We instead change the way the FlowCfg::deploy list is created - if targets are not required to run (for example, when --build-only or --run-only switch is passed), then they are not added to the deploy list. This means that the deploy list needs to be constructed correctly - the scheduler relies on it to know what to run. The scheduler previously recursively went through the dependencies to determine what all needed to be run - this required the FlowCfg to delete dependencies after the fact, if flow modifier switches were passed. This is no longer needed because we now explicitly provide it the list of things to run instead. This also means when checking an item's eligibility to be enqueued based on its dependencies' statuses, it needs to ignore the deps that were not a part of the original deploy list. The reason for this change is our internal Google Cloud based launching system, which runs each job (input -> process -> output) in an isolated VM instance. The job's input and output are tarballs that flit between the user's workstation, Google Cloud storage, and the VM instance. To support --run-only for example, in our environment, the run deploy object needs to be able to provide a pointer to its build dependency (which would have run in the past) so that the built simulation executable can be tarballed and uploaded as the run-job's input. Signed-off-by: Srikrishna Iyer <sriyer@google.com>
OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.
This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.
The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.
Have a look at CONTRIBUTING for guidelines on how to contribute code to this repository.
Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).