From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: KVM <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kvm-fixes tree
Date: Thu, 24 Apr 2025 19:38:21 +0200 [thread overview]
Message-ID: <df3b44a7-70b8-4952-a7d7-231e69c8d3eb@redhat.com> (raw)
In-Reply-To: <aAeg8A7DMvTAjqVO@google.com>
On 4/22/25 16:00, Sean Christopherson wrote:
> On Tue, Apr 22, 2025, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Tue, 22 Apr 2025 12:43:10 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>
>>> After merging the kvm-fixes tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
>>> ERROR: modpost: "kvm_arch_has_irq_bypass" [arch/x86/kvm/kvm-amd.ko] undefined!
>>>
>>> Caused by commit
>>>
>>> 73e0c567c24a ("KVM: SVM: Don't update IRTEs if APICv/AVIC is disabled")
>>>
>>> I have used the kvm-fixes tree from next-20250417 for today.
>>
>> I also had to use the kvm tree from next-20250417.
>
> It's a known issue[*], just waiting on Paolo to resurface. :-/
*bubbles noise*
Done, pushed to kvm/master and will resend the PR to Linus as soon as
Stephen updates linux-next.
Paolo
> [*] https://lore.kernel.org/all/20250418171609.231588-1-pbonzini@redhat.com
>
next prev parent reply other threads:[~2025-04-24 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 2:43 linux-next: build failure after merge of the kvm-fixes tree Stephen Rothwell
2025-04-22 7:33 ` Stephen Rothwell
2025-04-22 14:00 ` Sean Christopherson
2025-04-24 17:38 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-26 22:43 Stephen Rothwell
2021-05-27 4:56 ` Wanpeng Li
2021-05-27 11:44 ` Paolo Bonzini
2021-05-24 23:32 Stephen Rothwell
2021-05-24 23:55 ` Wanpeng Li
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=df3b44a7-70b8-4952-a7d7-231e69c8d3eb@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seanjc@google.com \
--cc=sfr@canb.auug.org.au \
/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