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, dave.hansen@linux.intel.com,
kernellwp@gmail.com
Cc: Marc Orr <marcorr@google.com>
Subject: [kvm PATCH v6 0/2] shrink vcpu_vmx down to order 2
Date: Wed, 31 Oct 2018 16:49:26 -0700 [thread overview]
Message-ID: <20181031234928.144206-1-marcorr@google.com> (raw)
Compared to the last version, I've:
(1) dropped the vmalloc patches
(2) updated the kmem cache for the guest_fpu field in the kvm_vcpu_arch
struct to be sized according to fpu_kernel_xstate_size
(3) Added minimum FPU checks in KVM's x86 init logic to avoid memory
corruption issues.
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.568.g152ad8e336-goog
next reply other threads:[~2018-10-31 23:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 23:49 Marc Orr [this message]
2018-10-31 23:49 ` [kvm PATCH v6 1/2] kvm: x86: Use task structs fpu field for user Marc Orr
2018-10-31 23:49 ` [kvm PATCH v6 2/2] kvm: x86: Dynamically allocate guest_fpu Marc Orr
2018-11-01 17:09 ` Dave Hansen
2018-11-01 17:35 ` Marc Orr
2018-11-05 10:08 ` Paolo Bonzini
2018-11-05 5:04 ` [LKP] [kvm] ac347c1bc8: WARNING:at_mm/slab_common.c:#kmem_cache_create_usercopy kernel test robot
2021-05-21 20:58 ` [kvm PATCH v6 0/2] shrink vcpu_vmx down to order 2 Jim Mattson
2021-05-24 12:50 ` Paolo Bonzini
2021-05-24 22:44 ` Sean Christopherson
2021-05-24 23:01 ` Jim Mattson
2021-05-25 0:00 ` 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=20181031234928.144206-1-marcorr@google.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