From: hpa@zytor.com
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jessica Yu <jeyu@redhat.com>
Subject: Re: [PATCH] objtool, module: discard __unreachable section for modules
Date: Wed, 01 Mar 2017 09:22:42 -0800 [thread overview]
Message-ID: <85EDC892-F417-4191-BFCD-F2B84A2125C8@zytor.com> (raw)
In-Reply-To: <CA+55aFxLpj2x+VP5DE-N+x6stfMtfZ7ayzCnZhwyuVSEgmj5-w@mail.gmail.com>
On March 1, 2017 9:01:54 AM PST, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>On Wed, Mar 1, 2017 at 8:44 AM, <hpa@zytor.com> wrote:
>>
>> I would like to see a name like, say, ".annot.unreachable", since is
>odds are pretty high we are going to need more annotations in the
>future.
>
>Why not just make it ".discard.unreachable", and then make the discard
>pattern be ".discard*".
>
>We already have .discard.text for some trace hackery, so it follows a
>pattern.
>
>And that's what we do for things like .rodata.* etc.
>
>In fact, we already have a pattern for '.discard.*' in the main
>vmlinux.lds.h file exactly for the .discard.text case (but not for
>modules, it looks like).
>
> Linus
I was assuming it would be used for more than just discarding.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-03-01 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 15:20 [PATCH] objtool, module: discard __unreachable section for modules Josh Poimboeuf
2017-03-01 16:44 ` hpa
2017-03-01 17:01 ` Linus Torvalds
2017-03-01 17:22 ` hpa [this message]
2017-03-01 18:04 ` [PATCH v2] objtool, module: discard objtool annotation sections " Josh Poimboeuf
2017-03-01 19:37 ` [tip:core/urgent] objtool, modules: Discard " tip-bot for Josh Poimboeuf
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=85EDC892-F417-4191-BFCD-F2B84A2125C8@zytor.com \
--to=hpa@zytor.com \
--cc=jeyu@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).