From: Ge Yang <yangge1116@126.com>
To: David Hildenbrand <david@redhat.com>, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
michael.roth@amd.com, 21cnbao@gmail.com,
baolin.wang@linux.alibaba.com, liuzixing@hygon.cn
Subject: Re: [PATCH] KVM: SEV: Pin SEV guest memory out of CMA area
Date: Fri, 10 Jan 2025 17:40:23 +0800 [thread overview]
Message-ID: <abfd37b9-335d-4af9-b593-7dcf4db98a26@126.com> (raw)
In-Reply-To: <26fe43db-b122-40e0-a05a-81b11b89ef46@redhat.com>
在 2025/1/10 16:58, David Hildenbrand 写道:
> On 10.01.25 09:48, yangge1116@126.com wrote:
>> From: yangge <yangge1116@126.com>
>
> I would suggest the title to be something like
>
> "KVM: SEV: fix wrong pinning of pages"
>
> Then you can describe that without FOLL_LONGTERM, the pages will not get
> migrated out of MIGRATE_CMA/ZONE_MOVABLE, violating these mechanisms to
> avoid fragmentation with unmovable pages, for example making CMA
> allocations fail.
>
> (CMA allocations failing is only one symptom of the missed usage of
> FOLL_LONGTERM)
>
>>
>> When pin_user_pages_fast() pins SEV guest memory without the
>> FOLL_LONGTERM flag, the pinned pages may inadvertently end up in the
>> CMA (Contiguous Memory Allocator) area. This can subsequently cause
>> cma_alloc() to fail in allocating these pages, due to the fact that
>> the pinned pages are not migratable.
>>
>> To address the aforementioned problem, we propose adding the
>> FOLL_LONGTERM flag to the pin_user_pages_fast() function. By doing
>> so, we ensure that the pages allocated will not occupy space within
>> the CMA area, thereby preventing potential allocation failures.
>>
>> Signed-off-by: yangge <yangge1116@126.com>
>> ---
>> arch/x86/kvm/svm/sev.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
>> index 943bd07..35d0714 100644
>> --- a/arch/x86/kvm/svm/sev.c
>> +++ b/arch/x86/kvm/svm/sev.c
>> @@ -630,6 +630,7 @@ static struct page **sev_pin_memory(struct kvm
>> *kvm, unsigned long uaddr,
>> unsigned long locked, lock_limit;
>> struct page **pages;
>> unsigned long first, last;
>> + unsigned int flags = 0;
>
> Why not set
>
> unsigned int flags = FOLL_LONGTERM;
>
>> int ret;
>> lockdep_assert_held(&kvm->lock);
>> @@ -662,8 +663,10 @@ static struct page **sev_pin_memory(struct kvm
>> *kvm, unsigned long uaddr,
>> if (!pages)
>> return ERR_PTR(-ENOMEM);
>> + flags = write ? FOLL_WRITE : 0;
>
>
> and here do
>
> flags |= write ? FOLL_WRITE : 0;
>
>> +
>> /* Pin the user virtual address. */
>> - npinned = pin_user_pages_fast(uaddr, npages, write ? FOLL_WRITE :
>> 0, pages);
>> + npinned = pin_user_pages_fast(uaddr, npages, flags |
>> FOLL_LONGTERM, pages);
>> if (npinned != npages) {
>> pr_err("SEV: Failure locking %lu pages.\n", npages);
>> ret = -ENOMEM;
>
>
Ok, thanks.
prev parent reply other threads:[~2025-01-10 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:48 yangge1116
2025-01-10 8:58 ` David Hildenbrand
2025-01-10 9:40 ` Ge Yang [this message]
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=abfd37b9-335d-4af9-b593-7dcf4db98a26@126.com \
--to=yangge1116@126.com \
--cc=21cnbao@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzixing@hygon.cn \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
/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
all inboxes | Powered by JetHome®