From: Shuah Khan <skhan@linuxfoundation.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, hpa@zytor.com,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] x86/Kconfig: Fix dependency for X86_DEBUG_FPU
Date: Thu, 10 Apr 2025 15:18:30 -0600 [thread overview]
Message-ID: <a874a35f-b63a-4e7b-8d5a-3696b7f39b74@linuxfoundation.org> (raw)
In-Reply-To: <Z_dl0HhwMOBkVTFH@gmail.com>
On 4/10/25 00:31, Ingo Molnar wrote:
>
> * Shuah Khan <skhan@linuxfoundation.org> wrote:
>
>> Yes it is vanilla
>
> Thx.
>
>>> More importantly, X86_REQUIRED_FEATURE_FPU *does not exist* in the
>>> vanilla v6.14 kernel, it's a new v6.15 feature. So this part of
>>> your changelog totally doesn't apply to a v6.14 kernel:
>>
>> I started with vanilla 6.14 kernel running oldconfig on it. In this
>> case if X86_DEBUG_FPU is enabled in the oldconfig, should the config
>> generated for 6.15 add X86_REQUIRED_FEATURE_FPU.
>>
>> It appears there is a dependency between X86_DEBUG_FPU and the newly
>> added X86_REQUIRED_FEATURE_FPU
>
> Could you send the v6.15-rc1 config that has this missing dependency?
>
> Because if I put the config you sent through 'make oldconfig' and
> accept all default suggestions, the X86_REQUIRED_FEATURE_FPU dependency
> is present:
>
> starship:~/tip> grep _FPU .config
> CONFIG_X86_REQUIRED_FEATURE_FPU=y
> CONFIG_ARCH_HAS_KERNEL_FPU_SUPPORT=y
> CONFIG_X86_DEBUG_FPU=y
> # CONFIG_TEST_FPU is not set
>
> ... and the build succeeds:
>
> OBJCOPY arch/x86/boot/setup.bin
> BUILD arch/x86/boot/bzImage
> Kernel: arch/x86/boot/bzImage is ready (#4)
>
> Ie. I cannot reproduce the build failure with the config you provided.
>
Okay. I ran a few more experiments with a fresh repo. I can't reproduce
the problem.
The only thing I can think of is somehow make didn't run oldconfig or
if it did didn't pick up the right the first time around ... Not sure.
You can ignore this patch. Sorry for the noise.
thanks,
-- Shuah
next prev parent reply other threads:[~2025-04-10 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 23:10 [PATCH] x86/Kconfig: Fix dependency for X86_DEBUG_FPU Shuah Khan
2025-04-08 6:54 ` Ingo Molnar
2025-04-08 16:51 ` Shuah Khan
2025-04-09 21:34 ` Ingo Molnar
2025-04-09 21:41 ` Shuah Khan
2025-04-10 6:31 ` Ingo Molnar
2025-04-10 21:18 ` Shuah Khan [this message]
2025-04-13 19:04 ` Ingo Molnar
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=a874a35f-b63a-4e7b-8d5a-3696b7f39b74@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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