1. 11 Jun, 2020 6 commits
  2. 09 Jun, 2020 9 commits
  3. 08 Jun, 2020 8 commits
  4. 05 Jun, 2020 2 commits
    • Igor Druzhinin's avatar
      x86/svm: do not try to handle recalc NPT faults immediately · 51ca66c3
      Igor Druzhinin authored
      A recalculation NPT fault doesn't always require additional handling
      in hvm_hap_nested_page_fault(), moreover in general case if there is no
      explicit handling done there - the fault is wrongly considered fatal.
      
      This covers a specific case of migration with vGPU assigned which
      uses direct MMIO mappings made by XEN_DOMCTL_memory_mapping hypercall:
      at a moment log-dirty is enabled globally, recalculation is requested
      for the whole guest memory including those mapped MMIO regions
      which causes a page fault being raised at the first access to them;
      but due to MMIO P2M type not having any explicit handling in
      hvm_hap_nested_page_fault() a domain is erroneously crashed with unhandled
      SVM violation.
      
      Instead of trying to be opportunistic - use safer approach and handle
      P2M recalculation in a separate NPT fault by attempting to retry after
      making the necessary adjustments. This is aligned with Intel behavior
      where there are separate VMEXITs for recalculation and EPT violations
      (faults) and only faults are handled in hvm_hap_nested_page_fault().
      Do it by also unifying do_recalc return code with Intel implementation
      where returning 1 means P2M was actually changed.
      
      Since there was no case previously where p2m_pt_handle_deferred_changes()
      could return a positive value - it's safe to replace ">= 0" with just "== 0"
      in VMEXIT_NPF handler. finish_type_change() is also not affected by the
      change as being able to deal with >0 return value of p2m->recalc from
      EPT implementation.
      Signed-off-by: default avatarIgor Druzhinin <igor.druzhinin@citrix.com>
      Reviewed-by: default avatarRoger Pau Monné <roger.pau@citrix.com>
      Reviewed-by: default avatarJan Beulich <jbeulich@suse.com>
      Release-acked-by: default avatarPaul Durrant <paul@xen.org>
      51ca66c3
    • Wei Liu's avatar
      libs/hypfs: use correct zlib name in pc file · 81da3f2b
      Wei Liu authored
      Its name is "zlib" not "z".
      Reported-by: default avatarOlaf Hering <olaf@aepfle.de>
      Fixes: 86234eaf ("libs: add libxenhypfs")
      Signed-off-by: default avatarWei Liu <wl@xen.org>
      Reviewed-by: default avatarJuergen Gross <jgross@suse.com>
      Acked-by: default avatarIan Jackson <ian.jackson@eu.citrix.com>
      Release-acked-by: default avatarPaul Durrant <paul@xen.org>
      81da3f2b
  5. 04 Jun, 2020 1 commit
    • Andrew Cooper's avatar
      x86/shim: Fix defconfig selection and trim the build further · 780aba27
      Andrew Cooper authored
      Several options (TBOOT, XENOPROF, Scheduler) depend on EXPERT to be able to
      deselect/configure.
      
      Enabling EXPERT now causes the request of the Credit1 scheduler to be honoured
      (rather than giving us Credit2), but take this opportunity to switch to Null,
      as the previously problematic issues are now believed to be fixed.
      
      Enabling EXPERT also allows XEN_SHSTK to be selected, and we don't want this
      being built for shim.  We also don't want TRACEBUFFER or GDBSX either.
      
      Take this oppotunity to swap the disable of HVM_FEP for a general disable of
      HVM (likely to have wider impliciations in the future), and disable ARGO (will
      necesserily need plumbing work to function in shim).
      Signed-off-by: default avatarAndrew Cooper <andrew.cooper3@citrix.com>
      Reviewed-by: default avatarJan Beulich <jbeulich@suse.com>
      Release-acked-by: default avatarPaul Durrant <paul@xen.org>
      780aba27
  6. 03 Jun, 2020 2 commits
  7. 02 Jun, 2020 12 commits