linux-kernel - [RFC PATCH v2 0/2] KVM: x86: Allow Qemu/KVM to use PVH entry point

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1512686715-11488-1-git-send-email-maran.wilson@oracle.com>
Date:   Thu,  7 Dec 2017 14:45:13 -0800
From:   Maran Wilson <maran.wilson@...cle.com>
To:     pbonzini@...hat.com, jgross@...e.com, boris.ostrovsky@...cle.com,
        roger.pau@...rix.com, andrew.cooper3@...rix.com, hch@...radead.org,
        x86@...nel.org, xen-devel@...ts.xenproject.org,
        linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc:     tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
        rkrcmar@...hat.com, JBeulich@...e.com
Subject: [RFC PATCH v2 0/2] KVM: x86: Allow Qemu/KVM to use PVH entry point

Changes from v1:

 * Adopted Paolo's suggestion for defining a v2 PVH ABI that includes the
   e820 map instead of using the second module entry to pass the table.

 * Cleaned things up a bit to reduce the number of xen vs non-xen special
   cases.

Juergen also had a suggestion to split the different hypervisor types
early and use a common set of service functions instead of special casing
xen_guest everywhere.

There are certainly less special cases in this version of the patch, but
if we still think it's important to split things up between common, Xen,
and KVM components, then I would appreciate a suggestion on how best that
can be done. Are we talking about just re-factoring functions in the
existing file? Or do we need to go all the way and pull all the PVH entry
code out of xen directories and find a home for it somewhere else so that
we can use kernels built without CONFIG_XEN to start KVM guests via the
PVH entry point. If the latter, any suggestions for which common files or
directories I can move this stuff to?

Maran Wilson (2):
      xen/pvh: Add memory map pointer to hvm_start_info struct
      KVM: x86: Allow Qemu/KVM to use PVH entry point

 arch/x86/xen/enlighten_pvh.c           | 48 +++++++++++++++++++++++++++++++++---------------
 include/xen/interface/hvm/start_info.h | 34 +++++++++++++++++++++++++++++++---
 2 files changed, 64 insertions(+), 18 deletions(-)