From: Marc Orr <marcorr@google.com>
To: kvm@vger.kernel.org, jmattson@google.com, rientjes@google.com,
konrad.wilk@oracle.com, linux-mm@kvack.org,
akpm@linux-foundation.org, pbonzini@redhat.com,
rkrcmar@redhat.com, willy@infradead.org,
sean.j.christopherson@intel.com
Cc: Marc Orr <marcorr@google.com>
Subject: [kvm PATCH v4 0/2] use vmalloc to allocate vmx vcpus
Date: Fri, 26 Oct 2018 00:58:58 -0700 [thread overview]
Message-ID: <20181026075900.111462-1-marcorr@google.com> (raw)
A couple of patches to allocate vmx vcpus with vmalloc instead of
kalloc, which enables vcpu allocation to succeeed when contiguous
physical memory is sparse.
Compared to the last version of these patches, this version:
1. Splits out the refactoring of the vmx_msrs struct into it's own
patch, as suggested by Sean Christopherson <sean.j.christopherson@intel.com>.
2. Leverages the __vmalloc() API rather than introducing a new vzalloc()
API, as suggested by Michal Hocko <mhocko@kernel.org>.
Marc Orr (2):
kvm: vmx: refactor vmx_msrs struct for vmalloc
kvm: vmx: use vmalloc() to allocate vcpus
arch/x86/kvm/vmx.c | 92 +++++++++++++++++++++++++++++++++++++++++----
virt/kvm/kvm_main.c | 28 ++++++++------
2 files changed, 100 insertions(+), 20 deletions(-)
--
2.19.1.568.g152ad8e336-goog
next reply other threads:[~2018-10-26 7:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:58 Marc Orr [this message]
2018-10-26 7:58 ` [kvm PATCH v4 1/2] kvm: vmx: refactor vmx_msrs struct for vmalloc Marc Orr
2018-10-26 11:02 ` Sean Christopherson
2018-10-26 7:59 ` [kvm PATCH v4 2/2] kvm: vmx: use vmalloc() to allocate vcpus Marc Orr
2018-10-26 12:29 ` [kvm PATCH v4 0/2] use vmalloc to allocate vmx vcpus Matthew Wilcox
2018-10-26 14:45 ` Matthew Wilcox
2018-10-26 14:49 ` Dave Hansen
2018-10-31 13:06 ` Marc Orr
2018-10-29 1:58 ` Wanpeng Li
2018-10-29 16:25 ` Jim Mattson
2018-10-29 16:48 ` Matthew Wilcox
2018-10-29 18:12 ` Jim Mattson
2018-10-29 19:16 ` Marc Orr
2018-10-29 19:22 ` Marc Orr
2018-10-31 13:17 ` Marc Orr
2018-10-31 13:27 ` Matthew Wilcox
2018-10-31 13:48 ` Marc Orr
2018-10-31 14:21 ` Matthew Wilcox
2018-10-31 21:19 ` Marc Orr
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=20181026075900.111462-1-marcorr@google.com \
--to=marcorr@google.com \
--cc=akpm@linux-foundation.org \
--cc=jmattson@google.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).