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

arch: cleanup EXCEPTION_STACK_TRACE dependencies #73376

Conversation

ycsin
Copy link
Member

@ycsin ycsin commented May 28, 2024

Note

Please review #73288 instead, thanks.

Move X86's dependencies from EXCEPTION_STACK_TRACE to X86_EXCEPTION_STACK_TRACE

@ycsin ycsin force-pushed the pr/exception_stack_trace_cleanup_x86 branch from 98a524a to 56478ed Compare May 29, 2024 15:42
arch/x86/core/Kconfig.intel64 Outdated Show resolved Hide resolved
@ycsin ycsin requested a review from dcpleung May 29, 2024 15:43
ycsin added 4 commits May 30, 2024 10:24
The `PRINTK` was required for `EXCEPTION_STACK_TRACE` because
it's initial implementation for x86 in zephyrproject-rtos#6653 uses `printk()`.
We are using `LOG_ERR()` now, so this is not required anymore.

Signed-off-by: Yong Cong Sin <[email protected]>
The `DEBUG_INFO` in the `EXCEPTION_STACK_TRACE` is only
required by x86. Move that to `X86_EXCEPTION_STACK_TRACE`
instead.

Signed-off-by: Yong Cong Sin <[email protected]>
Not all stack trace implementation requires frame pointer, move
that dependency to architecture Kconfig.

Signed-off-by: Yong Cong Sin <[email protected]>
Select `DEBUG_INFO` instead of depending on it.

Signed-off-by: Yong Cong Sin <[email protected]>
@ycsin ycsin force-pushed the pr/exception_stack_trace_cleanup_x86 branch from 56478ed to 92daf5c Compare May 30, 2024 02:24
@ycsin ycsin marked this pull request as draft May 30, 2024 09:56
@ycsin ycsin closed this Jun 5, 2024
@ycsin ycsin deleted the pr/exception_stack_trace_cleanup_x86 branch June 5, 2024 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants