From: Steven Rostedt <rostedt@goodmis.org>
To: Will Deacon <will@kernel.org>
Cc: Joel Fernandes <joel@joelfernandes.org>,
Jiping Ma <jiping.ma2@windriver.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
takahiro.akashi@linaro.org
Subject: Re: [PATCH v3] tracing: Function stack size and its name mismatch in arm64
Date: Mon, 5 Aug 2019 09:59:18 -0400 [thread overview]
Message-ID: <20190805095918.3942c45b@gandalf.local.home> (raw)
In-Reply-To: <20190805112524.ajlmouutqckwpqyd@willie-the-truck>
On Mon, 5 Aug 2019 12:25:25 +0100
Will Deacon <will@kernel.org> wrote:
> So, I completely agree with Steve that we shouldn't be littering the core code
> with #ifdef CONFIG_ARM64, but we probably do need something in the arch backend
> if we're going to do this properly, and that in turn is likely to need a very
> different algorithm from the one currently in use.
And I'm perfectly fine if someone wants to tear up the current
implementation, and make one that has callbacks to arch code (with
defaults for those that don't need it).
But it has to be clean. We worked hard to get rid of most "#ifdef"
being scattered in the kernel, and I'm not bringing it back in my code.
-- Steve
next prev parent reply other threads:[~2019-08-05 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 9:41 [PATCH v3] tracing: Function stack size and its name mismatch in arm64 Jiping Ma
2019-08-02 15:22 ` Steven Rostedt
2019-08-02 16:09 ` Steven Rostedt
2019-08-02 16:11 ` Steven Rostedt
2019-08-06 15:48 ` Joel Fernandes
2019-08-06 16:34 ` Steven Rostedt
2019-08-06 17:03 ` Steven Rostedt
2019-08-06 17:25 ` Joel Fernandes
2019-08-06 6:01 ` Jiping Ma
2019-08-03 8:26 ` Joel Fernandes
2019-08-03 8:32 ` Joel Fernandes
2019-08-05 11:25 ` Will Deacon
2019-08-05 13:59 ` Steven Rostedt [this message]
2019-08-06 13:00 ` Steven Rostedt
2019-08-06 14:47 ` Joel Fernandes
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=20190805095918.3942c45b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=catalin.marinas@arm.com \
--cc=jiping.ma2@windriver.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
--cc=will@kernel.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).