From: Feng Tang <feng.tang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
kernel test robot <lkp@intel.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Guo Ren <guoren@kernel.org>
Subject: Re: [PATCH] lib/Kconfig.debug: add ARCH dependency for FUNCTION_ALIGN option
Date: Fri, 4 Mar 2022 10:11:00 +0800 [thread overview]
Message-ID: <20220304021100.GN4548@shbuild999.sh.intel.com> (raw)
In-Reply-To: <20220303174550.4baa4d6d228320f09807c987@linux-foundation.org>
On Thu, Mar 03, 2022 at 05:45:50PM -0800, Andrew Morton wrote:
> On Thu, 3 Mar 2022 16:20:48 +0800 Feng Tang <feng.tang@intel.com> wrote:
>
> > 0Day robots reported there is compiling issue for 'csky' ARCH
> > when CONFIG_DEBUG_FORCE_DATA_SECTION_ALIGNED is enabled [1]:
> >
> > ...
> >
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -401,8 +401,8 @@ config SECTION_MISMATCH_WARN_ONLY
> > If unsure, say Y.
> >
> > config DEBUG_FORCE_FUNCTION_ALIGN_64B
> > - bool "Force all function address 64B aligned" if EXPERT
> > - depends on PPC || ARM || X86
>
> I cannot find a kernel which contains the above line?
Sorry. I generated the patch while forgetting to revert the older version
https://lore.kernel.org/lkml/20220228022022.GG4548@shbuild999.sh.intel.com/
Here is the correct versin, thanks!
---
From 817dca1a74778979ba71ed362eac36feab5ac112 Mon Sep 17 00:00:00 2001
From: Feng Tang <feng.tang@intel.com>
Date: Fri, 4 Mar 2022 10:03:40 +0800
Subject: [PATCH] lib/Kconfig.debug: add ARCH dependency for FUNCTION_ALIGN
option
0Day robots reported there is compiling issue for 'csky' ARCH
when CONFIG_DEBUG_FORCE_DATA_SECTION_ALIGNED is enabled [1]:
"
All errors (new ones prefixed by >>):
{standard input}: Assembler messages:
>> {standard input}:2277: Error: pcrel offset for branch to .LS000B too far (0x3c)
"
Which has been discussed in [2]. And as there is no solution for csky
yet, add some dependency for this config to limit it to several ARCHs
which have no compiling issue so far.
[1]. https://lore.kernel.org/lkml/202202271612.W32UJAj2-lkp@intel.com/
[2]. https://www.spinics.net/lists/linux-kbuild/msg30298.html
Reported-by: kernel test robot <lkp@intel.com>
Cc: Guo Ren <guoren@kernel.org>
Signed-off-by: Feng Tang <feng.tang@intel.com>
---
lib/Kconfig.debug | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 14b89aa37c5c..440fd666c16d 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -416,7 +416,8 @@ config SECTION_MISMATCH_WARN_ONLY
If unsure, say Y.
config DEBUG_FORCE_FUNCTION_ALIGN_64B
- bool "Force all function address 64B aligned" if EXPERT
+ bool "Force all function address 64B aligned"
+ depends on EXPERT && (X86_64 || ARM64 || PPC32 || PPC64 || ARC)
help
There are cases that a commit from one domain changes the function
address alignment of other domains, and cause magic performance
--
2.27.0
prev parent reply other threads:[~2022-03-04 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 8:20 Feng Tang
2022-03-04 1:45 ` Andrew Morton
2022-03-04 2:11 ` Feng Tang [this message]
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=20220304021100.GN4548@shbuild999.sh.intel.com \
--to=feng.tang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=guoren@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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
all inboxes | Powered by JetHome®