From: Andi Kleen <ak@linux.intel.com>
To: Christophe de Dinechin <cdupontd@redhat.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
David Hildenbrand <david@redhat.com>,
Dave Hansen <dave.hansen@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <seanjc@google.com>,
Jim Mattson <jmattson@google.com>,
David Rientjes <rientjes@google.com>, "Edgecombe\,
Rick P" <rick.p.edgecombe@intel.com>, "Kleen\,
Andi" <andi.kleen@intel.com>, "Yamahata\,
Isaku" <isaku.yamahata@intel.com>,
x86@kernel.org, kvm@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [RFCv1 7/7] KVM: unmap guest memory using poisoned pages
Date: Wed, 07 Apr 2021 07:09:00 -0700 [thread overview]
Message-ID: <87zgyauqyr.fsf@linux.intel.com> (raw)
In-Reply-To: <C841A818-7BBE-48B5-8CCB-1F8850CA52AD@redhat.com> (Christophe de Dinechin's message of "Wed, 7 Apr 2021 15:31:28 +0200")
Christophe de Dinechin <cdupontd@redhat.com> writes:
> Is there even a theoretical way to restore an encrypted page e.g. from (host)
> swap without breaking the integrity check? Or will that only be possible with
> assistance from within the encrypted enclave?
Only the later.
You would need balloning. It's in principle possible, but currently
not implemented.
In general host swap without balloning is usually a bad idea anyways
because it often just swaps a lot of cache data that could easily be
thrown away instead.
-andi
next prev parent reply other threads:[~2021-04-07 14:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 15:26 [RFCv1 0/7] TDX and guest memory unmapping Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 1/7] x86/mm: Move force_dma_unencrypted() to common code Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 2/7] x86/kvm: Introduce KVM memory protection feature Kirill A. Shutemov
2021-04-08 9:52 ` Borislav Petkov
2021-04-09 13:36 ` Kirill A. Shutemov
2021-04-09 14:37 ` Borislav Petkov
2021-04-02 15:26 ` [RFCv1 3/7] x86/kvm: Make DMA pages shared Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 4/7] x86/kvm: Use bounce buffers for KVM memory protection Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 5/7] x86/kvmclock: Share hvclock memory with the host Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 6/7] x86/realmode: Share trampoline area if KVM memory protection enabled Kirill A. Shutemov
2021-04-02 15:26 ` [RFCv1 7/7] KVM: unmap guest memory using poisoned pages Kirill A. Shutemov
2021-04-06 7:44 ` David Hildenbrand
2021-04-06 10:50 ` Kirill A. Shutemov
2021-04-06 14:33 ` Dave Hansen
2021-04-06 14:57 ` David Hildenbrand
2021-04-07 13:16 ` Kirill A. Shutemov
2021-04-07 13:31 ` Christophe de Dinechin
2021-04-07 14:09 ` Andi Kleen [this message]
2021-04-07 14:09 ` Andi Kleen
2021-04-07 14:09 ` David Hildenbrand
2021-04-07 14:36 ` Kirill A. Shutemov
2021-04-06 17:52 ` Tom Lendacky
2021-04-07 14:55 ` David Hildenbrand
2021-04-07 15:10 ` Andi Kleen
2021-04-07 15:10 ` Andi Kleen
2021-04-09 13:33 ` Kirill A. Shutemov
2021-04-09 13:50 ` David Hildenbrand
2021-04-09 14:12 ` Kirill A. Shutemov
2021-04-09 14:18 ` David Hildenbrand
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=87zgyauqyr.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=andi.kleen@intel.com \
--cc=cdupontd@redhat.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=isaku.yamahata@intel.com \
--cc=jmattson@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rientjes@google.com \
--cc=seanjc@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.