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

acrn does not handle per_cpu_data[(pcpu_id)].scheduler perfectly during initialization #8749

Open
476997779 opened this issue Dec 6, 2024 · 0 comments
Labels
status: new The issue status: new for creation

Comments

@476997779
Copy link
Contributor

Describe the bug
acrn does not handle per_cpu_data[(pcpu_id)].scheduler perfectly during initialization

When the number of PCPUs set by BIOS is less than vm_config->cpu_affinity, acrn will give a page fault error when initializing sos,
The reason for the error is that per_cpu_data[(num)].scheduler is not set in init_sched ( vm_config->cpu_affinity > num > bios set cpu num )

When init_thread_data is executed, scheduler->init_data is a null pointer, if (scheduler->init_data != NULL) a page fault will occur

Platform
Describe the platform information,

Codebase
Describe which codebase is used.

Scenario
Describe the scenario: Hybrid, Industry or logical_partition

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Attach the following logs if available:

  • native Linux boot kernel message log
  • ACRN serial port log (when issues happens)
  • Service VM kernel message when issue happens
  • acrn-dm log: all files in /var/log/acrn-tm
  • console log when running script to launch guest VM
@476997779 476997779 added the status: new The issue status: new for creation label Dec 6, 2024
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

1 participant