public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Houghton <jthoughton@google.com>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the kvm-x86 tree
Date: Fri, 14 Feb 2025 06:55:32 -0800	[thread overview]
Message-ID: <Z69ZZI0Cxljc4qi4@google.com> (raw)
In-Reply-To: <20250214181401.4e7dd91d@canb.auug.org.au>

On Fri, Feb 14, 2025, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the kvm-x86 tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
> 
> virt/kvm/Kconfig:103:warning: config symbol defined without type
> 
> Introduced by commit
> 
>   5eec660014bf ("KVM: Allow lockless walk of SPTEs when handing aging mmu_notifier event")

Gah, obvious once you see it.   KVM_MMU_NOTIFIER_AGING_LOCKLESS steals the "bool"
from KVM_ELIDE_TLB_FLUSH_IF_YOUNG.  I'll fixup and force push.

Thanks Stephen!

diff --git a/virt/kvm/Kconfig b/virt/kvm/Kconfig
index 54e959e7d68f..9356f4e4e255 100644
--- a/virt/kvm/Kconfig
+++ b/virt/kvm/Kconfig
@@ -102,6 +102,8 @@ config KVM_GENERIC_MMU_NOTIFIER
 
 config KVM_ELIDE_TLB_FLUSH_IF_YOUNG
        depends on KVM_GENERIC_MMU_NOTIFIER
+
+config KVM_MMU_NOTIFIER_AGING_LOCKLESS
        bool
 
 config KVM_GENERIC_MEMORY_ATTRIBUTES


  reply	other threads:[~2025-02-14 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  7:14 linux-next: build warning after merge of the kvm-x86 tree Stephen Rothwell
2025-02-14 14:55 ` Sean Christopherson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-26  7:10 Stephen Rothwell
2025-06-26 15:56 ` Sean Christopherson
2025-06-27  7:51   ` Stephen Rothwell
2023-01-20  2:09 Stephen Rothwell

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=Z69ZZI0Cxljc4qi4@google.com \
    --to=seanjc@google.com \
    --cc=jthoughton@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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