From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 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: Tue, 22 Apr 2025 07:00:16 -0700 [thread overview]
Message-ID: <aAeg8A7DMvTAjqVO@google.com> (raw)
In-Reply-To: <20250422173341.0901ebaf@canb.auug.org.au>
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. :-/
[*] https://lore.kernel.org/all/20250418171609.231588-1-pbonzini@redhat.com
next prev parent reply other threads:[~2025-04-22 14:00 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 [this message]
2025-04-24 17:38 ` Paolo Bonzini
-- 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=aAeg8A7DMvTAjqVO@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.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