From: Sean Christopherson <seanjc@google.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
Sean Christopherson <seanjc@google.com>
Subject: [PATCH 0/2] KVM: PPC: e500: Fix build error due to crappy KVM code
Date: Tue, 3 Mar 2026 11:03:37 -0800 [thread overview]
Message-ID: <20260303190339.974325-1-seanjc@google.com> (raw)
Fix an e500 build error that was introduced by the recent kmalloc_obj()
conversion, but in reality is due to crappy KVM code that has existed for
~13 years.
I'm taking this through kvm-x86 fixes, because it's breaking my testing setup,
and obviously no one cares about KVM e500 since PPC_WERROR is default 'y' and
needs to be explicitly disabled via PPC_DISABLE_WERROR.
Sean Christopherson (2):
KVM: PPC: e500: Fix build error due to using kmalloc_obj() with wrong
type
KVM: PPC: e500: Rip out "struct tlbe_ref"
arch/powerpc/kvm/e500.h | 6 +--
arch/powerpc/kvm/e500_mmu.c | 4 +-
arch/powerpc/kvm/e500_mmu_host.c | 91 +++++++++++++++-----------------
3 files changed, 47 insertions(+), 54 deletions(-)
base-commit: 11439c4635edd669ae435eec308f4ab8a0804808
--
2.53.0.473.g4a7958ca14-goog
next reply other threads:[~2026-03-03 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 19:03 Sean Christopherson [this message]
2026-03-03 19:03 ` [PATCH 1/2] KVM: PPC: e500: Fix build error due to using kmalloc_obj() with wrong type Sean Christopherson
2026-03-03 19:34 ` Christophe Leroy (CS GROUP)
2026-03-03 19:03 ` [PATCH 2/2] KVM: PPC: e500: Rip out "struct tlbe_ref" Sean Christopherson
2026-03-05 17:07 ` [PATCH 0/2] KVM: PPC: e500: Fix build error due to crappy KVM code Sean Christopherson
2026-03-06 4:02 ` Madhavan Srinivasan
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=20260303190339.974325-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kees@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.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