linux-kernel - Re: [EXTERNAL] Re: [PATCH 1/2] x86/Kconfig: Allow CONFIG_X86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 24 May 2023 11:02:42 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Saurabh Singh Sengar <ssengar@...rosoft.com>,
        Saurabh Sengar <ssengar@...ux.microsoft.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "bp@...en8.de" <bp@...en8.de>,
        "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
        "x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
        KY Srinivasan <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        "wei.liu@...nel.org" <wei.liu@...nel.org>,
        Dexuan Cui <decui@...rosoft.com>,
        "Michael Kelley (LINUX)" <mikelley@...rosoft.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH 1/2] x86/Kconfig: Allow CONFIG_X86_MPPARSE
 disable for OF platforms

On 5/24/23 09:23, Saurabh Singh Sengar wrote:
>> Could you please rephrase this to be less confusing?
> 
> Thanks for your review. Currently, in the absence of ACPI, it is impossible to
> disable X86_MPPARSE. In the case of ACPI being enabled, one has the
> option to either enable or disable X86_MPARSE. My intention is to permit
> X86_MPPARSE=n for OF platforms where ACPI=n. To describe the capability
> of choosing any desired value for MPPARSE, I used the term 'selectable.'
> Perhaps 'configurable' would be a more appropriate word in this context?
> I can fix this and include it in V2.

OK, so this particular Hyper-V setup doesn't run normal normal distro
kernels?  It requires a very specialized kernel?  Or it's just _better_
that the kernel is configured this way?

>> This is also one of those patches where I wonder: Why do _you_ care about
>> this?  Are you just trying to be nice?  Is this intended as some kind of cleanup?
> 
> It solves an issue for Hyper-V VBS setup, please refer to the 2/2 of this patch
> series.

Heh, that changelog is even more confusing than _this_ one.  It doesn't
say that there's a problem, only that it removes "not required" code.

I'm still confused by this whole thing.