Skip to content

WFI: Reacquire control of the core in the debugger after it executes a WFI instruction#11

Merged
eyck merged 1 commit intoMinres:mainfrom
quic-prateek:wfi_debugger_stop_issue
Mar 6, 2026
Merged

WFI: Reacquire control of the core in the debugger after it executes a WFI instruction#11
eyck merged 1 commit intoMinres:mainfrom
quic-prateek:wfi_debugger_stop_issue

Conversation

@quic-prateek
Copy link
Contributor

Issue: When the core executes a WFI instruction we cannot regain the core from the debugger

Fix: A new gdb_stop_evt event was added, triggered when the debugger issues a stop request. For more details, refer to this Minres/DBT-RISE-RISCV#43 PR.

/**
* @brief trigger gdb stop event to resume fetch instruction thread
*/
virtual void trigger_debugger_stop_event() {}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you rename it to cancel_wait() as the function triggering the state is wait_until(). I'd like to avoid bring notions of SystemC into the C++ ISS part

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

…a WFI instruction.

A new gdb_stop_evt event was added, triggered when the debugger issues
a stop request.
@quic-prateek quic-prateek force-pushed the wfi_debugger_stop_issue branch from 233e567 to 743b4d3 Compare March 2, 2026 18:43
Copy link
Contributor

@eyck eyck left a comment

Choose a reason for hiding this comment

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

LGTM

@eyck eyck merged commit 5d1ab03 into Minres:main Mar 6, 2026
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