From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Sean Christopherson <seanjc@google.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH 0/2] KVM: PPC: e500: Fix build error due to crappy KVM code
Date: Fri, 6 Mar 2026 09:32:42 +0530 [thread overview]
Message-ID: <06e74ae1-f2ad-44b9-943e-d81f6e9a638f@linux.ibm.com> (raw)
In-Reply-To: <177272543796.1535167.14939828079649935273.b4-ty@google.com>
On 3/5/26 10:37 PM, Sean Christopherson wrote:
> On Tue, 03 Mar 2026 11:03:37 -0800, Sean Christopherson wrote:
>> 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.
>>
>> [...]
> Applied to kvm-x86 fixes, thanks!
>
> [1/2] KVM: PPC: e500: Fix build error due to using kmalloc_obj() with wrong type
> https://github.com/kvm-x86/linux/commit/a223ccf0af6e
> [2/2] KVM: PPC: e500: Rip out "struct tlbe_ref"
> https://github.com/kvm-x86/linux/commit/3271085a7f10
I added this to my fixes-test, will pull it since you are taking it.
Maddy
> --
> https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2026-03-06 4:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 19:03 [PATCH 0/2] KVM: PPC: e500: Fix build error due to crappy KVM code Sean Christopherson
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 [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=06e74ae1-f2ad-44b9-943e-d81f6e9a638f@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=kees@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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