From: Sean Christopherson <seanjc@google.com>
To: Mathias Krause <minipli@grsecurity.net>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 2/2] KVM: Shrink struct kvm_mmu_memory_cache
Date: Fri, 17 Mar 2023 15:45:33 -0700 [thread overview]
Message-ID: <ZBTtjTFPCRtK0Cy8@google.com> (raw)
In-Reply-To: <20230217193336.15278-3-minipli@grsecurity.net>
On Fri, Feb 17, 2023, Mathias Krause wrote:
> Move the 'capacity' member around to make use of the padding hole on 64
Nit, 'nobjs' is the field that gets moved in this version. No need for another
version, I can fix up when applying.
If no one objects, I'll plan on taking this through kvm-x86/generic.
next prev parent reply other threads:[~2023-03-17 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 19:33 [PATCH v2 0/2] KVM: Minor structure layout changes Mathias Krause
2023-02-17 19:33 ` [PATCH v2 1/2] KVM: x86: Shrink struct kvm_pmu Mathias Krause
2023-02-17 19:33 ` [PATCH v2 2/2] KVM: Shrink struct kvm_mmu_memory_cache Mathias Krause
2023-03-17 22:45 ` Sean Christopherson [this message]
2023-03-20 21:37 ` Mathias Krause
2023-03-24 23:37 ` [PATCH v2 0/2] KVM: Minor structure layout changes 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=ZBTtjTFPCRtK0Cy8@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@grsecurity.net \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox