Skip to content

Expose AK_ifetch / AK_ttw at the concurrency interface - #1911

Open
Nickolai Zeldovich (zeldovich) wants to merge 1 commit into
riscv:masterfrom
zeldovich:load-types
Open

Expose AK_ifetch / AK_ttw at the concurrency interface#1911
Nickolai Zeldovich (zeldovich) wants to merge 1 commit into
riscv:masterfrom
zeldovich:load-types

Conversation

@zeldovich

Copy link
Copy Markdown

The concurrency interface defines AK_ifetch and AK_ttw, but the current Sail model does not carry the information about the reason for a memory load through to the MemRead event. This change propagates the memory read type all the way through to the MemRead event. This makes it possible to implement memory models where instruction or page-table reads are treated differently (e.g., RISC-V's non-coherent icache).

This patch is the result of a verification project on top of the Sail model using Claude Code, and the patch itself was also co-developed together with Claude Code.

The concurrency interface defines AK_ifetch and AK_ttw, but the current
Sail model does not carry the information about the reason for a memory
load through to the MemRead event.  This change propagates the memory read
type all the way through to the MemRead event.  This makes it possible
to implement memory models where instruction or page-table reads are
treated differently (e.g., RISC-V's non-coherent icache).

This patch is the result of a verification project on top of the Sail
model using Claude Code, and the patch itself was also co-developed
together with Claude Code.
@pmundkur

Copy link
Copy Markdown
Collaborator

I think this is handled in #1871, which is moving to a new version of this interface.

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.

2 participants