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

WaaG can not reboot or poweroff when cpu-sharing is enabled. #5115

Closed
conghuic23 opened this issue Jul 30, 2020 · 1 comment
Closed

WaaG can not reboot or poweroff when cpu-sharing is enabled. #5115

conghuic23 opened this issue Jul 30, 2020 · 1 comment
Labels
status: new The issue status: new for creation

Comments

@conghuic23
Copy link
Contributor

On WHL, when Waag share CPU with other VMs, there would be problem with reboot or poweroff.

@conghuic23 conghuic23 added the status: new The issue status: new for creation label Jul 30, 2020
@conghuic23
Copy link
Contributor Author

[External_System_ID]ACRN-6587

conghuic23 added a commit to conghuic23/acrn-hypervisor that referenced this issue Jul 30, 2020
As we only set BLOCKED status in context switch_out, which means, only
running thread can be changed to BLOCKED, but runnable thread can not.
This lead to the deadloop in sleep_thread_sync.

To solve the problem, in sleep_thread, we set the status to BLOCKED
directly when the original thread status is RUNNABLE.

Tracked-On: projectacrn#5115
Signed-off-by: Conghui Chen <conghui.chen@intel.com>
conghuic23 added a commit to conghuic23/acrn-hypervisor that referenced this issue Jul 30, 2020
As we only set BLOCKED status in context switch_out, which means, only
running thread can be changed to BLOCKED, but runnable thread can not.
This lead to the deadloop in sleep_thread_sync.

To solve the problem, in sleep_thread, we set the status to BLOCKED
directly when the original thread status is RUNNABLE.

Tracked-On: projectacrn#5115
Signed-off-by: Conghui Chen <conghui.chen@intel.com>
wenlingz pushed a commit that referenced this issue Jul 30, 2020
As we only set BLOCKED status in context switch_out, which means, only
running thread can be changed to BLOCKED, but runnable thread can not.
This lead to the deadloop in sleep_thread_sync.

To solve the problem, in sleep_thread, we set the status to BLOCKED
directly when the original thread status is RUNNABLE.

Tracked-On: #5115
Signed-off-by: Conghui Chen <conghui.chen@intel.com>
wenlingz pushed a commit that referenced this issue Jul 31, 2020
As we only set BLOCKED status in context switch_out, which means, only
running thread can be changed to BLOCKED, but runnable thread can not.
This lead to the deadloop in sleep_thread_sync.

To solve the problem, in sleep_thread, we set the status to BLOCKED
directly when the original thread status is RUNNABLE.

Tracked-On: #5115
Signed-off-by: Conghui Chen <conghui.chen@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: new The issue status: new for creation
Projects
None yet
Development

No branches or pull requests

2 participants