[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yv4pOz01nAkafiwd@zn.tnic>
Date: Thu, 18 Aug 2022 13:57:47 +0200
From: Borislav Petkov <bp@...en8.de>
To: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
Cc: ssengar@...rosoft.com, mikelley@...rosoft.com, tglx@...utronix.de,
mingo@...hat.com, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, peterz@...radead.org, tim.c.chen@...ux.intel.com,
will@...nel.org, song.bao.hua@...ilicon.com,
suravee.suthikulpanit@....com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/cacheinfo: Don't use cpu_llc_shared_map for
!CONFIG_SMP
On Wed, Aug 17, 2022 at 09:52:25PM -0700, Saurabh Singh Sengar wrote:
> Shall I mention here "Non-SMP AMD processor" instead ?
You should explain what that is.
Is that a CONFIG_SMP=n kernel which you boot on a AMD CPU?
IOW, how do I reproduce the issue you're describing below, here locally?
Send dmesg pls.
Also, what is the use case?
Why would you even build with SMP off?
Feel free to explain more verbosely what you're trying to accomplish.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists