From: Sean Christopherson <seanjc@google.com>
To: Jim Mattson <jmattson@google.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc Orr" <marcorr@google.com>, "kvm list" <kvm@vger.kernel.org>,
"David Rientjes" <rientjes@google.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
linux-mm <linux-mm@kvack.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Wanpeng Li" <kernellwp@gmail.com>
Subject: Re: [kvm PATCH v6 0/2] shrink vcpu_vmx down to order 2
Date: Tue, 25 May 2021 00:00:57 +0000 [thread overview]
Message-ID: <YKw+OenKB/X0amvm@google.com> (raw)
In-Reply-To: <CALMp9eQsTBp8D_Vtv4CFPzhb+QODDHjTH2aG8s-YSM_cgCEtVQ@mail.gmail.com>
On Mon, May 24, 2021, Jim Mattson wrote:
> On Mon, May 24, 2021 at 3:44 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > On Mon, May 24, 2021, Paolo Bonzini wrote:
> > > On 21/05/21 22:58, Jim Mattson wrote:
> > > > On Wed, Oct 31, 2018 at 4:49 PM Marc Orr <marcorr@google.com> wrote:
> > > > >
> > > > > 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(-)
> > > > >
> > > > > --
> > > >
> > > > Whatever happened to this series?
> > >
> > > There was a question about the usage of kmem_cache_create_usercopy, and a v7
> > > was never sent.
> >
> > What's that go to do with anything? :-D
> >
> > b666a4b69739 ("kvm: x86: Dynamically allocate guest_fpu")
> > 240c35a3783a ("kvm: x86: Use task structs fpu field for user")
>
> So, that's what the series was trimmed down to. Thanks!
>
> Did we still manage to get down to order 2?
Yep, almost made it to order-1!
Current size (without 8 bytes from CONFIG_HYPERV=y) is 9728.
prev parent reply other threads:[~2021-05-25 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 23:49 [kvm PATCH v6 0/2] shrink vcpu_vmx down to order 2 Marc Orr
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 ` [kvm] ac347c1bc8: WARNING:at_mm/slab_common.c:#kmem_cache_create_usercopy kernel test robot
2018-11-05 5:04 ` [LKP] " 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 [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=YKw+OenKB/X0amvm@google.com \
--to=seanjc@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=marcorr@google.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.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 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.