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

Uos cs limit from dm #1689

Merged
merged 3 commits into from
Nov 1, 2018
Merged

Commits on Nov 1, 2018

  1. DM: set cs_limit from DM side for UOS

    For CS of UOS, we would like to pass all related info (cs attribute,
    limit, base) from DM.
    
    Tracked-On: projectacrn#1231
    Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
    Acked-by: Eddie Dong <Eddie.dong@intel.com>
    fyin1 committed Nov 1, 2018
    Configuration menu
    Copy the full SHA
    e347b0e View commit details
    Browse the repository at this point in the history
  2. HV: save the cs limit field for SOS

    Save the native cs limit and reuse it for SOS cs limit. To remove
    the hardcode of cs limit for guest in hypervisor.
    
    Tracked-On: projectacrn#1231
    Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
    Acked-by: Eddie Dong <Eddie.dong@intel.com>
    fyin1 committed Nov 1, 2018
    Configuration menu
    Copy the full SHA
    84c942f View commit details
    Browse the repository at this point in the history
  3. hv: avoid hardcode cs.limit in set_vcpu_regs()

    For SOS BSP, we reuse native saved cs.limit
    For UOS BSP, we set cs.limit in DM
    For AP, we use initialized data from realmode_init_regs.
    
    Tracked-On: projectacrn#1231
    Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
    Acked-by: Eddie Dong <Eddie.dong@intel.com>
    fyin1 committed Nov 1, 2018
    Configuration menu
    Copy the full SHA
    794157c View commit details
    Browse the repository at this point in the history