Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

attempt at listing some system rules with examples #401

Merged
merged 9 commits into from
Oct 4, 2024

Conversation

tariqkurd-repo
Copy link
Collaborator

@tariqkurd-repo tariqkurd-repo commented Oct 2, 2024

Something which came up in RVI discussions is how to build CHERI systems, so this section adds some system guidelines.

src/system.adoc Outdated Show resolved Hide resolved
Co-authored-by: Alexander Richardson <[email protected]>
Signed-off-by: Andres Amaya Garcia <[email protected]>
src/system.adoc Outdated Show resolved Hide resolved
andresag01 and others added 2 commits October 4, 2024 14:50
Signed-off-by: Andres Amaya Garcia <[email protected]>
Co-authored-by: Alexander Richardson <[email protected]>
Signed-off-by: Andres Amaya Garcia <[email protected]>
@andresag01 andresag01 merged commit 87e672d into riscv:main Oct 4, 2024
3 checks passed
Copy link
Collaborator

@arichardson arichardson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had some outstanding comments that I forgot to submit but nothing major.


There are two types of bus connections used in chips which contain CHERI CPUs:

. Tag-aware busses, where the bus protocol is extended to carry the tag along with the data. This is typically done using a user defined bit in the protocol.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. Tag-aware busses, where the bus protocol is extended to carry the tag along with the data. This is typically done using a user defined bit in the protocol.
. Tag-aware busses, where the bus protocol is extended to carry the tag along with the data. This is typically done using user defined bits in the protocol.


There are, or will soon be, a wide range of CHERI systems in existence from tiny IoT devices up to server chips.

There are two types of bus connections used in chips which contain CHERI CPUs:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
There are two types of bus connections used in chips which contain CHERI CPUs:
There are two types of bus connections used in SoCs which contain CHERI CPUs:

. Tag-aware busses, where the bus protocol is extended to carry the tag along with the data. This is typically done using a user defined bit in the protocol.
.. These busses will read tags from memory (if tags are present in the target memory) and return them to the requestor.
.. These busses will write the tag to memory as an extension of the data write.
. Non-tag aware busses, i.e. normal non-CHERI aware busses.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. Non-tag aware busses, i.e. normal non-CHERI aware busses.
. Non-tag aware busses, i.e. current non-CHERI aware busses.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've put these into #409

tariqkurd-repo added a commit to tariqkurd-repo/riscv-cheri that referenced this pull request Oct 9, 2024
Something which came up in RVI discussions is how to build CHERI
systems, so this section adds some system guidelines.

---------

Signed-off-by: Andres Amaya Garcia <[email protected]>
Co-authored-by: Andres Amaya Garcia <[email protected]>
Co-authored-by: Alexander Richardson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants