On Mon, Nov 04, 2019 at 09:47:52AM +0530, Bharata B Rao wrote: > Hi, > > This is the next version of the patchset that adds required support > in the KVM hypervisor to run secure guests on PEF-enabled POWER platforms. > > The major change in this version is about not using kvm.arch->rmap[] > array to store device PFNs, thus not depending on the memslot availability > to reach to the device PFN from the fault path. Instead of rmap[], we > now have a different array which gets created and destroyed along with > memslot creation and deletion. These arrays hang off from kvm.arch and > are arragned in a simple linked list for now. We could move to some other > data structure in future if walking of linked list becomes an overhead > due to large number of memslots. Thanks. This is looking really close now. > Other changes include: > > - Rearranged/Merged/Cleaned up patches, removed all Acks/Reviewed-by since > all the patches have changed. > - Added a new patch to support H_SVM_INIT_ABORT hcall (From Suka) > - Added KSM unmerge support so that VMAs that have device PFNs don't > participate in KSM merging and eventually crash in KSM code. > - Release device pages during unplug (Paul) and ensure that memory > hotplug and unplug works correctly. > - Let kvm-hv module to load on PEF-disabled platforms (Ram) when > CONFIG_PPC_UV is enabled allowing regular non-secure guests > to still run. > - Support guest reset when swithing to secure is in progress. > - Check if page is already secure in kvmppc_send_page_to_uv() before > sending it to UV. > - Fixed sentinal for header file kvm_book3s_uvmem.h (Jason) > > Now, all the dependencies required by this patchset are in powerpc/next > on which this patchset is based upon. Can you tell me what patches that are in powerpc/next but not upstream this depends on? Paul.
