From: Zhi Wang <zhi.wang.linux@gmail.com>
To: Sagi Shahar <sagis@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Erdem Aktas <erdemaktas@google.com>,
David Matlack <dmatlack@google.com>,
Kai Huang <kai.huang@intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [RFC PATCH 0/5] Add TDX intra host migration support
Date: Fri, 14 Apr 2023 10:03:50 +0300 [thread overview]
Message-ID: <20230414100350.00000955.zhi.wang.linux@gmail.com> (raw)
In-Reply-To: <20230407201921.2703758-1-sagis@google.com>
On Fri, 7 Apr 2023 20:19:16 +0000
Sagi Shahar <sagis@google.com> wrote:
Hi:
Is there any userspace using these APIs? I cant find them in AMD-QEMU repo
and upstream QEMU repo. It would nice to first take a look on how userspace
is going to use it.
> This patchset adds support for TDX intra host migration using the same
> API which was added for SEV intra host migration here:
> https://lore.kernel.org/all/20211021174303.385706-1-pgonda@google.com/
>
> This patchset relies on the latest TDX patches from Intel:
> - fd-based approach for supporing KVM v10 and
> https://lore.kernel.org/lkml/20221202061347.1070246-1-chao.p.peng@linux.intel.com/
> - TDX host kernel support v10
> https://lore.kernel.org/lkml/cover.1678111292.git.kai.huang@intel.com/
> - KVM TDX basic feature support v13
> https://lore.kernel.org/cover.1678643051.git.isaku.yamahata@intel.com
>
> The tree can be found at https://github.com/googleprodkernel/linux-cc/tree/copyless
> and is based on Intel's tdx tree at https://github.com/intel/tdx/tree/kvm-upstream
>
> In the TDX case, we need to transfer the VM state from multiple sources:
>
> * HKID and encrypted VM state is transfered between the kvm_tdx
> objects.
> * Encrypted and runtime state is transfered between the vcpu_tdx
> objects.
> * The EPT table backing TD's private memory is transfered at the
> kvm-mmu level. This is needed since the secure EPT table managed by
> the TD module remains the same after the migration so moving the
> current private EPT table eliminates the need to rebuild the private
> EPT table to match the secure EPT table on the destination.
> * Information regarding the current shared/private memory is trasfered
> using the mem_attr_array stored at the kvm object.
> * Additional information derived from shared/private memory state is
> trasfered at the memslot level.
>
> Tested with selftests locally. I will attach the self test in the next
> version after we send the new TDX selftest framework patches based on
> KVM TDX basic feature support v13.
>
> Sagi Shahar (5):
> KVM: Split tdp_mmu_pages to private and shared lists
> KVM: SEV: Refactor common code out of sev_vm_move_enc_context_from
> KVM: TDX: Add base implementation for tdx_vm_move_enc_context_from
> KVM: TDX: Implement moving private pages between 2 TDs
> KVM: TDX: Add core logic for TDX intra-host migration
>
> arch/x86/include/asm/kvm_host.h | 5 +-
> arch/x86/kvm/mmu.h | 2 +
> arch/x86/kvm/mmu/mmu.c | 60 ++++++++
> arch/x86/kvm/mmu/tdp_mmu.c | 88 +++++++++++-
> arch/x86/kvm/mmu/tdp_mmu.h | 3 +
> arch/x86/kvm/svm/sev.c | 175 +++--------------------
> arch/x86/kvm/vmx/main.c | 10 ++
> arch/x86/kvm/vmx/tdx.c | 245 ++++++++++++++++++++++++++++++++
> arch/x86/kvm/vmx/tdx.h | 2 +
> arch/x86/kvm/vmx/x86_ops.h | 5 +
> arch/x86/kvm/x86.c | 166 ++++++++++++++++++++++
> arch/x86/kvm/x86.h | 16 +++
> 12 files changed, 613 insertions(+), 164 deletions(-)
>
next prev parent reply other threads:[~2023-04-14 7:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 20:19 [RFC PATCH 0/5] Add TDX intra host migration support Sagi Shahar
2023-04-07 20:19 ` [RFC PATCH 1/5] KVM: Split tdp_mmu_pages to private and shared lists Sagi Shahar
2023-04-17 19:36 ` Zhi Wang
2023-04-18 17:14 ` Sagi Shahar
2023-04-07 20:19 ` [RFC PATCH 2/5] KVM: SEV: Refactor common code out of sev_vm_move_enc_context_from Sagi Shahar
2023-04-17 19:45 ` Zhi Wang
2023-04-18 17:17 ` Sagi Shahar
2023-04-07 20:19 ` [RFC PATCH 3/5] KVM: TDX: Add base implementation for tdx_vm_move_enc_context_from Sagi Shahar
2023-04-18 6:28 ` Zhi Wang
2023-04-18 17:47 ` Sagi Shahar
2023-04-19 6:34 ` Zhi Wang
2023-04-27 21:25 ` Sagi Shahar
2023-04-28 16:08 ` Zhi Wang
2023-04-18 12:11 ` Zhi Wang
2023-04-18 17:51 ` Sagi Shahar
2023-04-07 20:19 ` [RFC PATCH 4/5] KVM: TDX: Implement moving private pages between 2 TDs Sagi Shahar
2023-06-02 7:00 ` Isaku Yamahata
2023-04-07 20:19 ` [RFC PATCH 5/5] KVM: TDX: Add core logic for TDX intra-host migration Sagi Shahar
2023-04-19 7:08 ` Zhi Wang
2023-04-14 7:03 ` Zhi Wang [this message]
2023-04-14 19:09 ` [RFC PATCH 0/5] Add TDX intra host migration support Sagi Shahar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230414100350.00000955.zhi.wang.linux@gmail.com \
--to=zhi.wang.linux@gmail.com \
--cc=bp@alien8.de \
--cc=chao.p.peng@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dmatlack@google.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sagis@google.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox