Skip to content

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

Open
@476997779

Description

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: newThe issue status: new for creation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions