[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v9 1/8] mm: Introduce memfd_restricted system call to create
From: |
Kirill A. Shutemov |
Subject: |
Re: [PATCH v9 1/8] mm: Introduce memfd_restricted system call to create restricted user memory |
Date: |
Thu, 3 Nov 2022 00:14:04 +0300 |
On Mon, Oct 31, 2022 at 12:47:38PM -0500, Michael Roth wrote:
>
> In v8 there was some discussion about potentially passing the page/folio
> and order as part of the invalidation callback, I ended up needing
> something similar for SEV-SNP, and think it might make sense for other
> platforms. This main reasoning is:
>
> 1) restoring kernel directmap:
>
> Currently SNP (and I believe TDX) need to either split or remove kernel
> direct mappings for restricted PFNs, since there is no guarantee that
> other PFNs within a 2MB range won't be used for non-restricted
> (which will cause an RMP #PF in the case of SNP since the 2MB
> mapping overlaps with guest-owned pages)
That's news to me. Where the restriction for SNP comes from? There's no
such limitation on TDX side AFAIK?
Could you point me to relevant documentation if there's any?
--
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH v9 1/8] mm: Introduce memfd_restricted system call to create restricted user memory, Michael Roth, 2022/11/28