From: Marc Orr <marcorr@google.com>
To: kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
David Rientjes <rientjes@google.com>,
Konrad Rzeszutek Wilk <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, dave.hansen@linux.intel.com,
Wanpeng Li <kernellwp@gmail.com>
Subject: Re: [kvm PATCH v8 0/2] shrink vcpu_vmx down to order 2
Date: Thu, 29 Nov 2018 13:51:28 -0800 [thread overview]
Message-ID: <CAA03e5Hzu1gVffVRy70BtrGeo4wj25DtYH6Y34N2BZoiSJTviQ@mail.gmail.com> (raw)
In-Reply-To: <20181106225356.119901-1-marcorr@google.com>
On Tue, Nov 6, 2018 at 2:53 PM Marc Orr <marcorr@google.com> wrote:
>
> Compared to the last version, I've:
> (0) Actually update the patches, as explained below.
> (1) Added a comment to explain the FPU checks in kvm_arch_init()
> (2) Changed the kmem_cache_create_usercopy() to kmem_cache_create()
>
> Marc Orr (2):
> kvm: x86: Use task structs fpu field for user
> kvm: x86: Dynamically allocate guest_fpu
>
> arch/x86/include/asm/kvm_host.h | 10 +++---
> arch/x86/kvm/svm.c | 10 ++++++
> arch/x86/kvm/vmx.c | 10 ++++++
> arch/x86/kvm/x86.c | 55 ++++++++++++++++++++++++---------
> 4 files changed, 65 insertions(+), 20 deletions(-)
>
> --
> 2.19.1.930.g4563a0d9d0-goog
>
Ping.
next prev parent reply other threads:[~2018-11-29 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 22:53 [kvm PATCH v8 0/2] shrink vcpu_vmx down to order 2 Marc Orr
2018-11-06 22:53 ` [kvm PATCH v8 1/2] kvm: x86: Use task structs fpu field for user Marc Orr
2018-11-06 22:53 ` [kvm PATCH v8 2/2] kvm: x86: Dynamically allocate guest_fpu Marc Orr
2018-11-29 21:51 ` Marc Orr [this message]
2018-12-14 11:25 ` [kvm PATCH v8 0/2] shrink vcpu_vmx down to order 2 Paolo Bonzini
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=CAA03e5Hzu1gVffVRy70BtrGeo4wj25DtYH6Y34N2BZoiSJTviQ@mail.gmail.com \
--to=marcorr@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=jmattson@google.com \
--cc=kernellwp@gmail.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).