From: Marc Orr <marcorr@google.com>
To: kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
David Rientjes <rientjes@google.com>,
konrad.wilk@oracle.com, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [kvm PATCH 0/2] kvm: vmalloc vmx vcpus
Date: Tue, 23 Oct 2018 17:13:05 -0400 [thread overview]
Message-ID: <CAA03e5F9qAB6AyZ=XPcfPapqQOn3rad_PUydZvFjDj3Md9pWEA@mail.gmail.com> (raw)
In-Reply-To: <20181020211200.255171-1-marcorr@google.com>
Adding everyone that's cc'd on [kvm PATCH 1/2] mm: export
__vmalloc_node_range().
Thanks,
MarcOn Sat, Oct 20, 2018 at 5:12 PM Marc Orr <marcorr@google.com> wrote:
>
> Patch series to allocate vmx vcpus with vmalloc() instead of kalloc().
> This enables vendors to pack more VMs on a single host.
>
> Marc Orr (2):
> mm: export __vmalloc_node_range()
> kvm: vmx: use vmalloc() to allocate vcpus
>
> arch/x86/kvm/vmx.c | 98 +++++++++++++++++++++++++++++++++++++++++----
> mm/vmalloc.c | 1 +
> virt/kvm/kvm_main.c | 28 +++++++------
> 3 files changed, 107 insertions(+), 20 deletions(-)
>
> --
> 2.19.1.568.g152ad8e336-goog
>
next prev parent reply other threads:[~2018-10-23 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181020211200.255171-1-marcorr@google.com>
[not found] ` <20181020211200.255171-2-marcorr@google.com>
2018-10-22 20:06 ` [kvm PATCH 1/2] mm: export __vmalloc_node_range() Konrad Rzeszutek Wilk
2018-10-23 12:33 ` Michal Hocko
2018-10-23 21:10 ` Marc Orr
2018-10-24 6:16 ` Michal Hocko
2018-10-24 8:12 ` Marc Orr
2018-10-24 8:22 ` Michal Hocko
2018-10-23 21:13 ` Marc Orr [this message]
[not found] ` <20181020211200.255171-3-marcorr@google.com>
2018-10-23 21:13 ` [kvm PATCH 2/2] kvm: vmx: use vmalloc() to allocate vcpus Marc Orr
2018-10-24 11:41 ` Matthew Wilcox
2018-10-24 18:05 ` Marc Orr
2018-10-25 12:58 ` Michal Hocko
2018-10-24 22:31 ` Sean Christopherson
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='CAA03e5F9qAB6AyZ=XPcfPapqQOn3rad_PUydZvFjDj3Md9pWEA@mail.gmail.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=rientjes@google.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 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.