From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 2/2] KVM: SEV: Fall back to __vmalloc() for SEV-ES scratch area if necessary
Date: Thu, 11 Nov 2021 13:52:07 +0100 [thread overview]
Message-ID: <e7b2172f-c0d9-41ef-0607-257c3871b376@redhat.com> (raw)
In-Reply-To: <20211109222350.2266045-3-seanjc@google.com>
On 11/9/21 23:23, Sean Christopherson wrote:
> The buffer is purely a KVM software construct, i.e. there's
> no need for it to be physically contiguous, and at a max allowed size of
> 16kb it's just large enough that kzalloc() could feasibly fail due to
> memory fragmentation.
That isn't entirely correct, as kzalloc() won't really fail for requests
up to 32kb, i.e. order <= PAGE_ALLOC_COSTLY_ORDER. However, the
reasoning is correct so I queued the patches.
Paolo
prev parent reply other threads:[~2021-11-11 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 22:23 [PATCH 0/2] KVM: SEV: Fall back to __vmalloc() for SEV-ES scratch Sean Christopherson
2021-11-09 22:23 ` [PATCH 1/2] KVM: SEV: Return appropriate error codes if SEV-ES scratch setup fails Sean Christopherson
2021-11-11 15:14 ` Tom Lendacky
2021-11-11 15:47 ` Paolo Bonzini
2021-11-11 15:56 ` Tom Lendacky
2021-11-09 22:23 ` [PATCH 2/2] KVM: SEV: Fall back to __vmalloc() for SEV-ES scratch area if necessary Sean Christopherson
2021-11-11 12:52 ` Paolo Bonzini [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=e7b2172f-c0d9-41ef-0607-257c3871b376@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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®