* [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT @ 2023-05-30 20:19 Florian Fainelli 2023-05-30 21:39 ` Conor Dooley 2023-06-01 10:25 ` Greg Kroah-Hartman 0 siblings, 2 replies; 10+ messages in thread From: Florian Fainelli @ 2023-05-30 20:19 UTC (permalink / raw) To: stable Cc: Pierre Gondois, Conor Dooley, Sudeep Holla, Florian Fainelli, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY [-- Attachment #1: Type: text/plain, Size: 1743 bytes --] From: Pierre Gondois <pierre.gondois@arm.com> commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream fetch_cache_info() tries to get the number of cache leaves/levels for each CPU in order to pre-allocate memory for cacheinfo struct. Allocating this memory later triggers a: 'BUG: sleeping function called from invalid context' in PREEMPT_RT kernels. If there is no cache related information available in DT or ACPI, fetch_cache_info() fails and an error message is printed: 'Early cacheinfo failed, ret = ...' Not having cache information should be a valid configuration. Remove the error message if fetch_cache_info() fails with -ENOENT. Suggested-by: Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> --- Changes in v2: - Added missing upstream commit reference - Added missing S-o-b drivers/base/arch_topology.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c index 147fb7d4af96..b741b5ba82bd 100644 --- a/drivers/base/arch_topology.c +++ b/drivers/base/arch_topology.c @@ -843,10 +843,11 @@ void __init init_cpu_topology(void) for_each_possible_cpu(cpu) { ret = fetch_cache_info(cpu); - if (ret) { + if (!ret) + continue; + else if (ret != -ENOENT) pr_err("Early cacheinfo failed, ret = %d\n", ret); - break; - } + return; } } -- 2.25.1 [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4221 bytes --] ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-30 20:19 [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT Florian Fainelli @ 2023-05-30 21:39 ` Conor Dooley 2023-05-30 22:42 ` Florian Fainelli 2023-06-01 10:25 ` Greg Kroah-Hartman 1 sibling, 1 reply; 10+ messages in thread From: Conor Dooley @ 2023-05-30 21:39 UTC (permalink / raw) To: Florian Fainelli Cc: stable, Pierre Gondois, Conor Dooley, Sudeep Holla, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY Yo Florian, On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > From: Pierre Gondois <pierre.gondois@arm.com> > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > fetch_cache_info() tries to get the number of cache leaves/levels > for each CPU in order to pre-allocate memory for cacheinfo struct. > Allocating this memory later triggers a: > 'BUG: sleeping function called from invalid context' > in PREEMPT_RT kernels. > > If there is no cache related information available in DT or ACPI, > fetch_cache_info() fails and an error message is printed: > 'Early cacheinfo failed, ret = ...' > > Not having cache information should be a valid configuration. > Remove the error message if fetch_cache_info() fails with -ENOENT. > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> How come this now needs a backport? Did the rest of the series get backported, but not this one since it has no fixes tag? Cheers, Conor. ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-30 21:39 ` Conor Dooley @ 2023-05-30 22:42 ` Florian Fainelli 2023-05-31 8:53 ` Sudeep Holla 0 siblings, 1 reply; 10+ messages in thread From: Florian Fainelli @ 2023-05-30 22:42 UTC (permalink / raw) To: Conor Dooley Cc: stable, Pierre Gondois, Conor Dooley, Sudeep Holla, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY [-- Attachment #1: Type: text/plain, Size: 2008 bytes --] Hi Conor, On 5/30/23 14:39, Conor Dooley wrote: > Yo Florian, > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: >> From: Pierre Gondois <pierre.gondois@arm.com> >> >> commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream >> >> fetch_cache_info() tries to get the number of cache leaves/levels >> for each CPU in order to pre-allocate memory for cacheinfo struct. >> Allocating this memory later triggers a: >> 'BUG: sleeping function called from invalid context' >> in PREEMPT_RT kernels. >> >> If there is no cache related information available in DT or ACPI, >> fetch_cache_info() fails and an error message is printed: >> 'Early cacheinfo failed, ret = ...' >> >> Not having cache information should be a valid configuration. >> Remove the error message if fetch_cache_info() fails with -ENOENT. >> >> Suggested-by: Conor Dooley <conor.dooley@microchip.com> >> Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ >> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> >> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> >> Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com >> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> >> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > How come this now needs a backport? Did the rest of the series get > backported, but not this one since it has no fixes tag? Humm, indeed, this has been present in v6.3.2 since I requested it to be included. The error that I saw this morning was not -ENOENT, but -EINVAL. With those patches applied, no more -EINVAL: cacheinfo: Allow early level detection when DT/ACPI info is missing/broken cacheinfo: Add arm64 early level initializer implementation cacheinfo: Add arch specific early level initializer cacheinfo: Add use_arch[|_cache]_info field/function I will submit those shortly unless we think they better not be in 6.3, in which case it would be nice to silence those -EINVAL errors. -- Florian [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4221 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-30 22:42 ` Florian Fainelli @ 2023-05-31 8:53 ` Sudeep Holla 2023-05-31 9:26 ` Conor Dooley 2023-05-31 15:28 ` Florian Fainelli 0 siblings, 2 replies; 10+ messages in thread From: Sudeep Holla @ 2023-05-31 8:53 UTC (permalink / raw) To: Florian Fainelli Cc: Conor Dooley, stable, Pierre Gondois, Sudeep Holla, Conor Dooley, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > Hi Conor, > > On 5/30/23 14:39, Conor Dooley wrote: > > Yo Florian, > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > From: Pierre Gondois <pierre.gondois@arm.com> > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > Allocating this memory later triggers a: > > > 'BUG: sleeping function called from invalid context' > > > in PREEMPT_RT kernels. > > > > > > If there is no cache related information available in DT or ACPI, > > > fetch_cache_info() fails and an error message is printed: > > > 'Early cacheinfo failed, ret = ...' > > > > > > Not having cache information should be a valid configuration. > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > > > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > > > How come this now needs a backport? Did the rest of the series get > > backported, but not this one since it has no fixes tag? > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > With those patches applied, no more -EINVAL: > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > cacheinfo: Add arm64 early level initializer implementation > cacheinfo: Add arch specific early level initializer > cacheinfo: Add use_arch[|_cache]_info field/function > > I will submit those shortly unless we think they better not be in 6.3, in > which case it would be nice to silence those -EINVAL errors. I prefer this option instead of back porting all the above 4 as there are some pending fixes for the issues found in those patches. I am fine if Greg is happy with the backport, so no strong rejection from my side :). -- Regards, Sudeep ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-31 8:53 ` Sudeep Holla @ 2023-05-31 9:26 ` Conor Dooley 2023-05-31 15:28 ` Florian Fainelli 1 sibling, 0 replies; 10+ messages in thread From: Conor Dooley @ 2023-05-31 9:26 UTC (permalink / raw) To: Sudeep Holla Cc: Florian Fainelli, stable, Pierre Gondois, Conor Dooley, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY [-- Attachment #1: Type: text/plain, Size: 2671 bytes --] On Wed, May 31, 2023 at 09:53:56AM +0100, Sudeep Holla wrote: > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > > Hi Conor, > > > > On 5/30/23 14:39, Conor Dooley wrote: > > > Yo Florian, > > > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > > From: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > > Allocating this memory later triggers a: > > > > 'BUG: sleeping function called from invalid context' > > > > in PREEMPT_RT kernels. > > > > > > > > If there is no cache related information available in DT or ACPI, > > > > fetch_cache_info() fails and an error message is printed: > > > > 'Early cacheinfo failed, ret = ...' > > > > > > > > Not having cache information should be a valid configuration. > > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > > > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > > > > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > > > > > How come this now needs a backport? Did the rest of the series get > > > backported, but not this one since it has no fixes tag? > > > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > > > With those patches applied, no more -EINVAL: > > > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > > cacheinfo: Add arm64 early level initializer implementation > > cacheinfo: Add arch specific early level initializer > > cacheinfo: Add use_arch[|_cache]_info field/function > > > > I will submit those shortly unless we think they better not be in 6.3, in > > which case it would be nice to silence those -EINVAL errors. > > I prefer this option instead of back porting all the above 4 as there are > some pending fixes for the issues found in those patches. I am fine if Greg > is happy with the backport, so no strong rejection from my side :). Just to be clear, I was not objecting, just curious! [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-31 8:53 ` Sudeep Holla 2023-05-31 9:26 ` Conor Dooley @ 2023-05-31 15:28 ` Florian Fainelli 2023-05-31 15:43 ` Sudeep Holla 1 sibling, 1 reply; 10+ messages in thread From: Florian Fainelli @ 2023-05-31 15:28 UTC (permalink / raw) To: Sudeep Holla Cc: Conor Dooley, stable, Pierre Gondois, Conor Dooley, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY [-- Attachment #1: Type: text/plain, Size: 2637 bytes --] On 5/31/2023 1:53 AM, Sudeep Holla wrote: > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: >> Hi Conor, >> >> On 5/30/23 14:39, Conor Dooley wrote: >>> Yo Florian, >>> >>> On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: >>>> From: Pierre Gondois <pierre.gondois@arm.com> >>>> >>>> commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream >>>> >>>> fetch_cache_info() tries to get the number of cache leaves/levels >>>> for each CPU in order to pre-allocate memory for cacheinfo struct. >>>> Allocating this memory later triggers a: >>>> 'BUG: sleeping function called from invalid context' >>>> in PREEMPT_RT kernels. >>>> >>>> If there is no cache related information available in DT or ACPI, >>>> fetch_cache_info() fails and an error message is printed: >>>> 'Early cacheinfo failed, ret = ...' >>>> >>>> Not having cache information should be a valid configuration. >>>> Remove the error message if fetch_cache_info() fails with -ENOENT. >>>> >>>> Suggested-by: Conor Dooley <conor.dooley@microchip.com> >>>> Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ >>>> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> >>>> Reviewed-by: Conor Dooley <conor.dooley@microchip.com> >>>> Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com >>>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> >>>> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> >>> >>> How come this now needs a backport? Did the rest of the series get >>> backported, but not this one since it has no fixes tag? >> >> Humm, indeed, this has been present in v6.3.2 since I requested it to be >> included. The error that I saw this morning was not -ENOENT, but -EINVAL. >> >> With those patches applied, no more -EINVAL: >> >> cacheinfo: Allow early level detection when DT/ACPI info is missing/broken >> cacheinfo: Add arm64 early level initializer implementation >> cacheinfo: Add arch specific early level initializer >> cacheinfo: Add use_arch[|_cache]_info field/function >> >> I will submit those shortly unless we think they better not be in 6.3, in >> which case it would be nice to silence those -EINVAL errors. > > I prefer this option instead of back porting all the above 4 as there are > some pending fixes for the issues found in those patches. I am fine if Greg > is happy with the backport, so no strong rejection from my side :). OK, so are you suggesting that we specific check for -EINVAL and -ENOENT rather than take all of the 4 above patches, if so, any preference on how to do it given the state of 6.3 stable? -- Florian [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4221 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-31 15:28 ` Florian Fainelli @ 2023-05-31 15:43 ` Sudeep Holla [not found] ` <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com> 0 siblings, 1 reply; 10+ messages in thread From: Sudeep Holla @ 2023-05-31 15:43 UTC (permalink / raw) To: Florian Fainelli Cc: Conor Dooley, stable, Pierre Gondois, Sudeep Holla, Conor Dooley, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY On Wed, May 31, 2023 at 08:28:26AM -0700, Florian Fainelli wrote: > > > On 5/31/2023 1:53 AM, Sudeep Holla wrote: > > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > > > Hi Conor, > > > > > > On 5/30/23 14:39, Conor Dooley wrote: > > > > Yo Florian, > > > > > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > > > From: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > > > Allocating this memory later triggers a: > > > > > 'BUG: sleeping function called from invalid context' > > > > > in PREEMPT_RT kernels. > > > > > > > > > > If there is no cache related information available in DT or ACPI, > > > > > fetch_cache_info() fails and an error message is printed: > > > > > 'Early cacheinfo failed, ret = ...' > > > > > > > > > > Not having cache information should be a valid configuration. > > > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > > > > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > > > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > > > > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > > > > > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > > > > > > > How come this now needs a backport? Did the rest of the series get > > > > backported, but not this one since it has no fixes tag? > > > > > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > > > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > > > > > With those patches applied, no more -EINVAL: > > > > > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > > > cacheinfo: Add arm64 early level initializer implementation > > > cacheinfo: Add arch specific early level initializer > > > cacheinfo: Add use_arch[|_cache]_info field/function > > > > > > I will submit those shortly unless we think they better not be in 6.3, in > > > which case it would be nice to silence those -EINVAL errors. > > > > I prefer this option instead of back porting all the above 4 as there are > > some pending fixes for the issues found in those patches. I am fine if Greg > > is happy with the backport, so no strong rejection from my side :). > > OK, so are you suggesting that we specific check for -EINVAL and -ENOENT > rather than take all of the 4 above patches, Yes that is my preference ATM or if possible to wait until all the fixes are sorted for the bugs associated with above 4 commits [1] and [2]. I have queued [1] but waiting for response/patch on [2] and hence not yet bothered Greg. > if so, any preference on how to do it given the state of 6.3 stable? I don't understand what exactly do you mean ? -- Regards, Sudeep [1] https://lore.kernel.org/all/20230508084115.1157-1-kprateek.nayak@amd.com [2] https://lore.kernel.org/all/20230518012703.GA19967@ranerica-svr.sc.intel.com ^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com>]
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT [not found] ` <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com> @ 2023-06-01 6:32 ` Sudeep Holla 2023-06-01 10:25 ` Greg Kroah-Hartman 0 siblings, 1 reply; 10+ messages in thread From: Sudeep Holla @ 2023-06-01 6:32 UTC (permalink / raw) To: Florian Fainelli Cc: Conor Dooley, stable, Pierre Gondois, Conor Dooley, Greg Kroah-Hartman, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY On Wed, May 31, 2023 at 12:52:22PM -0700, Florian Fainelli wrote: > > > On 5/31/2023 8:43 AM, Sudeep Holla wrote: > > On Wed, May 31, 2023 at 08:28:26AM -0700, Florian Fainelli wrote: > > > > > > > > > On 5/31/2023 1:53 AM, Sudeep Holla wrote: > > > > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > > > > > Hi Conor, > > > > > > > > > > On 5/30/23 14:39, Conor Dooley wrote: > > > > > > Yo Florian, > > > > > > > > > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > > > > > From: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > > > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > > > > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > > > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > > > > > Allocating this memory later triggers a: > > > > > > > 'BUG: sleeping function called from invalid context' > > > > > > > in PREEMPT_RT kernels. > > > > > > > > > > > > > > If there is no cache related information available in DT or ACPI, > > > > > > > fetch_cache_info() fails and an error message is printed: > > > > > > > 'Early cacheinfo failed, ret = ...' > > > > > > > > > > > > > > Not having cache information should be a valid configuration. > > > > > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > > > > > > > > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > > > > > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > > > > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > > > > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > > > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > > > > > > > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > > > > > > > > > > > How come this now needs a backport? Did the rest of the series get > > > > > > backported, but not this one since it has no fixes tag? > > > > > > > > > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > > > > > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > > > > > > > > > With those patches applied, no more -EINVAL: > > > > > > > > > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > > > > > cacheinfo: Add arm64 early level initializer implementation > > > > > cacheinfo: Add arch specific early level initializer > > > > > cacheinfo: Add use_arch[|_cache]_info field/function > > > > > > > > > > I will submit those shortly unless we think they better not be in 6.3, in > > > > > which case it would be nice to silence those -EINVAL errors. > > > > > > > > I prefer this option instead of back porting all the above 4 as there are > > > > some pending fixes for the issues found in those patches. I am fine if Greg > > > > is happy with the backport, so no strong rejection from my side :). > > > > > > OK, so are you suggesting that we specific check for -EINVAL and -ENOENT > > > rather than take all of the 4 above patches, > > > > Yes that is my preference ATM or if possible to wait until all the fixes > > are sorted for the bugs associated with above 4 commits [1] and [2]. > > I have queued [1] but waiting for response/patch on [2] and hence not yet > > bothered Greg. > > > > > if so, any preference on how to do it given the state of 6.3 stable? > > > > I don't understand what exactly do you mean ? > > Linux 6.3.y currently contains: > > cacheinfo: Check sib_leaf in cache_leaves_are_shared() > cacheinfo: Check cache properties are present in DT > arch_topology: Remove early cacheinfo error message if -ENOENT > > however my logs are full of: > > [ 0.001484] Early cacheinfo failed, ret = -22 > > reverting these 3 patches mentioned above does not eliminate the error. > > What I am asking is if we need a targeted fix for 6.3 like this: > I am fine with that. Please note Greg has now pulled the fixes I pointed. So I am fine if you want to backport the 4 patches discussed earlier as the stable will get the fixes soon which was my main concern earlier. The other issue I pointed should also be resolved soon based on [1] -- Regards, Sudeep [1] https://lore.kernel.org/all/20230531170336.GA22753@ranerica-svr.sc.intel.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-06-01 6:32 ` Sudeep Holla @ 2023-06-01 10:25 ` Greg Kroah-Hartman 0 siblings, 0 replies; 10+ messages in thread From: Greg Kroah-Hartman @ 2023-06-01 10:25 UTC (permalink / raw) To: Sudeep Holla Cc: Florian Fainelli, Conor Dooley, stable, Pierre Gondois, Conor Dooley, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY On Thu, Jun 01, 2023 at 07:32:31AM +0100, Sudeep Holla wrote: > On Wed, May 31, 2023 at 12:52:22PM -0700, Florian Fainelli wrote: > > > > > > On 5/31/2023 8:43 AM, Sudeep Holla wrote: > > > On Wed, May 31, 2023 at 08:28:26AM -0700, Florian Fainelli wrote: > > > > > > > > > > > > On 5/31/2023 1:53 AM, Sudeep Holla wrote: > > > > > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > > > > > > Hi Conor, > > > > > > > > > > > > On 5/30/23 14:39, Conor Dooley wrote: > > > > > > > Yo Florian, > > > > > > > > > > > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > > > > > > From: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > > > > > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > > > > > > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > > > > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > > > > > > Allocating this memory later triggers a: > > > > > > > > 'BUG: sleeping function called from invalid context' > > > > > > > > in PREEMPT_RT kernels. > > > > > > > > > > > > > > > > If there is no cache related information available in DT or ACPI, > > > > > > > > fetch_cache_info() fails and an error message is printed: > > > > > > > > 'Early cacheinfo failed, ret = ...' > > > > > > > > > > > > > > > > Not having cache information should be a valid configuration. > > > > > > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > > > > > > > > > > > Suggested-by: Conor Dooley <conor.dooley@microchip.com> > > > > > > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > > > > > > Signed-off-by: Pierre Gondois <pierre.gondois@arm.com> > > > > > > > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > > > > > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > > > > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> > > > > > > > > Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com> > > > > > > > > > > > > > > How come this now needs a backport? Did the rest of the series get > > > > > > > backported, but not this one since it has no fixes tag? > > > > > > > > > > > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > > > > > > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > > > > > > > > > > > With those patches applied, no more -EINVAL: > > > > > > > > > > > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > > > > > > cacheinfo: Add arm64 early level initializer implementation > > > > > > cacheinfo: Add arch specific early level initializer > > > > > > cacheinfo: Add use_arch[|_cache]_info field/function > > > > > > > > > > > > I will submit those shortly unless we think they better not be in 6.3, in > > > > > > which case it would be nice to silence those -EINVAL errors. > > > > > > > > > > I prefer this option instead of back porting all the above 4 as there are > > > > > some pending fixes for the issues found in those patches. I am fine if Greg > > > > > is happy with the backport, so no strong rejection from my side :). > > > > > > > > OK, so are you suggesting that we specific check for -EINVAL and -ENOENT > > > > rather than take all of the 4 above patches, > > > > > > Yes that is my preference ATM or if possible to wait until all the fixes > > > are sorted for the bugs associated with above 4 commits [1] and [2]. > > > I have queued [1] but waiting for response/patch on [2] and hence not yet > > > bothered Greg. > > > > > > > if so, any preference on how to do it given the state of 6.3 stable? > > > > > > I don't understand what exactly do you mean ? > > > > Linux 6.3.y currently contains: > > > > cacheinfo: Check sib_leaf in cache_leaves_are_shared() > > cacheinfo: Check cache properties are present in DT > > arch_topology: Remove early cacheinfo error message if -ENOENT > > > > however my logs are full of: > > > > [ 0.001484] Early cacheinfo failed, ret = -22 > > > > reverting these 3 patches mentioned above does not eliminate the error. > > > > What I am asking is if we need a targeted fix for 6.3 like this: > > > > I am fine with that. Please note Greg has now pulled the fixes I pointed. > So I am fine if you want to backport the 4 patches discussed earlier as > the stable will get the fixes soon which was my main concern earlier. > > The other issue I pointed should also be resolved soon based on [1] Ok, I don't know what to do here. I think I'll take this simple patch, and not the longer series as that seems to be too much for 6.3.y now, especially as the fixes for it are not in Linus's tree yet. If, after a bit, all of those need to go to 6.3.y, can someone please send them here for inclusion? thanks, greg k-h ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT 2023-05-30 20:19 [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT Florian Fainelli 2023-05-30 21:39 ` Conor Dooley @ 2023-06-01 10:25 ` Greg Kroah-Hartman 1 sibling, 0 replies; 10+ messages in thread From: Greg Kroah-Hartman @ 2023-06-01 10:25 UTC (permalink / raw) To: Florian Fainelli Cc: stable, Pierre Gondois, Conor Dooley, Sudeep Holla, Rafael J. Wysocki, open list:GENERIC ARCHITECTURE TOPOLOGY On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > From: Pierre Gondois <pierre.gondois@arm.com> > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream Wait, this is already in 6.3.2, so why add it again? totally confused, greg k-h ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-06-01 10:27 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-05-30 20:19 [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT Florian Fainelli
2023-05-30 21:39 ` Conor Dooley
2023-05-30 22:42 ` Florian Fainelli
2023-05-31 8:53 ` Sudeep Holla
2023-05-31 9:26 ` Conor Dooley
2023-05-31 15:28 ` Florian Fainelli
2023-05-31 15:43 ` Sudeep Holla
[not found] ` <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com>
2023-06-01 6:32 ` Sudeep Holla
2023-06-01 10:25 ` Greg Kroah-Hartman
2023-06-01 10:25 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox