All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Chris Metcalf <cmetcalf@ezchip.com>,
	Quentin Casasnovas <quentin.casasnovas@oracle.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Mathias Krause <minipli@googlemail.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	linux-kernel@vger.kernel.org
Cc: Chris Metcalf <cmetcalf@ezchip.com>
Subject: Re: [PATCH] modpost: work correctly with tile coldtext sections
Date: Thu, 09 Jul 2015 07:05:46 +0930	[thread overview]
Message-ID: <87wpyatjrh.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1436390457-14968-1-git-send-email-cmetcalf@ezchip.com>

Chris Metcalf <cmetcalf@ezchip.com> writes:
> The tilegx and tilepro compilers use .coldtext for their unlikely
> executed text section name, so an __attribute__((cold)) function
> will (when compiled with higher optimization levels) land in the
> the .coldtext section.
>
> Modify modpost to add .coldtext to the set of OTHER_TEXT_SECTIONS
> so we don't get warnings about referencing such a section in an
> __ex_table block, and then also modify arch/tile/lib/memcpy_user_64.c
> so that it uses plain ".coldtext" instead of ".coldtext.memcpy".
> The latter naming is a relic of an earlier use of -ffunction-sections,
> which we no longer use by default.
>
> Signed-off-by: Chris Metcalf <cmetcalf@ezchip.com>
> ---
> Since this is a tile issue, should I push this through the tile tree?
> Or does someone want to take it into a tree for modpost?  Thanks.

Tile tree seems suitable, so:

Acked-by: Rusty Russell <rusty@rustcorp.com.au>

Thanks,
Rusty.

>
>  arch/tile/lib/memcpy_user_64.c | 4 ++--
>  scripts/mod/modpost.c          | 3 ++-
>  2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/tile/lib/memcpy_user_64.c b/arch/tile/lib/memcpy_user_64.c
> index 88c7016492c4..97bbb6060b25 100644
> --- a/arch/tile/lib/memcpy_user_64.c
> +++ b/arch/tile/lib/memcpy_user_64.c
> @@ -28,7 +28,7 @@
>  #define _ST(p, inst, v)						\
>  	({							\
>  		asm("1: " #inst " %0, %1;"			\
> -		    ".pushsection .coldtext.memcpy,\"ax\";"	\
> +		    ".pushsection .coldtext,\"ax\";"	\
>  		    "2: { move r0, %2; jrp lr };"		\
>  		    ".section __ex_table,\"a\";"		\
>  		    ".align 8;"					\
> @@ -41,7 +41,7 @@
>  	({							\
>  		unsigned long __v;				\
>  		asm("1: " #inst " %0, %1;"			\
> -		    ".pushsection .coldtext.memcpy,\"ax\";"	\
> +		    ".pushsection .coldtext,\"ax\";"	\
>  		    "2: { move r0, %2; jrp lr };"		\
>  		    ".section __ex_table,\"a\";"		\
>  		    ".align 8;"					\
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 91ee1b2e0f9a..12d3db3bd46b 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -886,7 +886,8 @@ static void check_section(const char *modname, struct elf_info *elf,
>  #define TEXT_SECTIONS ".text", ".text.unlikely", ".sched.text", \
>  		".kprobes.text"
>  #define OTHER_TEXT_SECTIONS ".ref.text", ".head.text", ".spinlock.text", \
> -		".fixup", ".entry.text", ".exception.text", ".text.*"
> +		".fixup", ".entry.text", ".exception.text", ".text.*", \
> +		".coldtext"
>  
>  #define INIT_SECTIONS      ".init.*"
>  #define MEM_INIT_SECTIONS  ".meminit.*"
> -- 
> 2.1.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2015-07-08 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 21:20 [PATCH] modpost: work correctly with tile coldtext sections Chris Metcalf
2015-07-08 21:35 ` Rusty Russell [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=87wpyatjrh.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=cmetcalf@ezchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=minipli@googlemail.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=quentin.casasnovas@oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.