mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
Cc: Arnd Bergmann <arnd@arndb.de>, <linux-kernel@vger.kernel.org>,
	Michal Marek <mmarek@suse.com>
Subject: Re: [PATCH RESEND 0/2] kbuild: dead code elimination: ftrace fixes
Date: Thu, 22 Dec 2016 19:08:54 +1000	[thread overview]
Message-ID: <20161222190854.6604e386@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1482396707-14349-1-git-send-email-marcin.nowakowski@imgtec.com>

On Thu, 22 Dec 2016 09:51:45 +0100
Marcin Nowakowski <marcin.nowakowski@imgtec.com> wrote:

> Enabling dead code & data elimination currently breaks ftrace operation,
> as the __mcount_loc section is removed (as it is not referenced directly
> anywhere in the code).
> Moreover, there are a lot of entries missing in the __mcount_loc section
> as the recordmcount tool doesn't currently properly handle the section
> names as created by the use of -ffunction-sections.

Thanks for keeping on top of these. I didn't have any objections, so
if you would send them to Michal Marek for merge and cc linux-kbuild
that would be appreciated.

Thanks,
Nick

  parent reply	other threads:[~2016-12-22  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22  8:51 Marcin Nowakowski
2016-12-22  8:51 ` [PATCH 1/2] kbuild: keep __mcount_loc table through dead code elimination Marcin Nowakowski
2016-12-22  8:51 ` [PATCH 2/2] recordmcount: fix mcount recording with -ffunction-sections Marcin Nowakowski
2016-12-22  9:08 ` Nicholas Piggin [this message]
2016-12-22  9:15   ` [PATCH RESEND 0/2] kbuild: dead code elimination: ftrace fixes Marcin Nowakowski

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=20161222190854.6604e386@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.nowakowski@imgtec.com \
    --cc=mmarek@suse.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 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®