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

QEMUv8: ftrace: xtest regression_1021 hang #6375

Closed
jforissier opened this issue Oct 12, 2023 · 5 comments
Closed

QEMUv8: ftrace: xtest regression_1021 hang #6375

jforissier opened this issue Oct 12, 2023 · 5 comments
Labels

Comments

@jforissier
Copy link
Contributor

$ make CFG_FTRACE_SUPPORT=y CFG_SYSCALL_FTRACE=y CFLAGS_ta_arm64=-pg run
$ xtest regression_1021
[...]
o regression_1021.2 Single Instance Multi Sessions
[   38.313976] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[   38.315378] rcu:     0-...0: (1 GPs behind) idle=94ec/1/0x4000000000000000 softirq=582/583 fqs=2625
[   38.316345]  (detected by 1, t=5252 jiffies, g=109, q=8 ncpus=2)
[   38.317222] Task dump for CPU 0:
[   38.317546] task:xtest           state:R  running task     stack:0     pid:135   ppid:133    flags:0x00000002
[   38.318960] Call trace:
[   38.319257]  __switch_to+0xe4/0x160
[   38.320355]  irqtime_account_irq+0x64/0x17c
[   38.320624]  __irq_exit_rcu+0x20/0xf4
[   38.320991]  irq_exit_rcu+0x10/0x20
[   38.321274]  el1_interrupt+0x58/0x70
[   38.321539]  el1h_64_irq_handler+0x18/0x2c
[   38.321783]  el1h_64_irq+0x64/0x68
[   38.321968]  __arm_smccc_smc+0x14/0x40
@jforissier
Copy link
Contributor Author

Bisected to c10e3fa.

@jenswi-linaro
Copy link
Contributor

Thanks, I'll take a look.

@jenswi-linaro
Copy link
Contributor

#6378 should take care of this.

By the way, passing CFLAGS_ta_arm64=-pg seems quite inconvenient. Couldn't that be done automatically with CFG_FTRACE_SUPPORT=y or something?

@jforissier
Copy link
Contributor Author

jforissier commented Oct 13, 2023

By the way, passing CFLAGS_ta_arm64=-pg seems quite inconvenient. Couldn't that be done automatically with CFG_FTRACE_SUPPORT=y or something?

The purpose of each flag is different. CFG_FTRACE_SUPPORT enables ftrace support in the TEE core, while CFLAGS selects which TA we want to trace. With CFLAGS_ta_arm64=-pg all TAs are traced, but -pg could as well be added more selectively to a single TA or even a single source file in a TA.

Copy link

This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants