From: Mathias Krause <minipli@grsecurity.net>
To: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Mathias Krause <minipli@grsecurity.net>
Subject: [PATCH v2 0/2] KVM: Minor structure layout changes
Date: Fri, 17 Feb 2023 20:33:34 +0100 [thread overview]
Message-ID: <20230217193336.15278-1-minipli@grsecurity.net> (raw)
v1: https://lore.kernel.org/kvm/20230213163351.30704-1-minipli@grsecurity.net/
This used to be a more exhaustive patch set shrinking kvm_vcpu's size.
But we concluded that this would be too fragile to maintain and would
require a more radical layout change to group often used members
together instead of chopping off individual padding bytes.
The remaining two patches are nonetheless useful, as they either make
the structure layout a more natural fit (as for kvm_pmu, putting the
version atop) or removing pointless padding (kvm_mmu_memory_cache).
Please apply!
Thanks,
Mathias Krause (2):
KVM: x86: Shrink struct kvm_pmu
KVM: Shrink struct kvm_mmu_memory_cache
arch/x86/include/asm/kvm_host.h | 2 +-
include/linux/kvm_types.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-17 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 19:33 Mathias Krause [this message]
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
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=20230217193336.15278-1-minipli@grsecurity.net \
--to=minipli@grsecurity.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@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 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).