From: Steven Rostedt <rostedt@goodmis.org>
To: Alan Kao <nonerkao@gmail.com>
Cc: Palmer Dabbelt <palmer@sifive.com>, Jim Wilson <jimw@sifive.com>,
albert@sifive.com, mingo@redhat.com, patches@groups.riscv.org,
linux-kernel@vger.kernel.org, greentime@andestech.com,
alankao@andestech.com, pombredanne@nexb.com, kito@andestech.com
Subject: Re: [PATCH v2] riscv/ftrace: Add basic support
Date: Tue, 12 Dec 2017 19:34:20 -0500 [thread overview]
Message-ID: <20171212193420.3ba4e6d9@gandalf.local.home> (raw)
In-Reply-To: <20171212070758.GA26787@1a3c108b4593>
On Tue, 12 Dec 2017 15:08:00 +0800
Alan Kao <nonerkao@gmail.com> wrote:
> > It's not a big deal, though -- we can fix these later. The more interesting
> > thing here is that this code means our `-pg` stuff is now part of the GCC
> > ABI, which is something I'd never though of before. I've added Jim, our GCC
> > guy.
> >
> > Jim: do you mind checking to make sure the GCC profiling support is sane?
> > Specifically, I'm thinking:
> >
> > * Are there any profiling features we don't support that would require an
> > ABI break?
> > * Is there a way to add future ISA extensions without breaking the ABI?
> > * Should we document this as part of the ELF psABI specification?
> >
> > Even though this isn't user-visible as far an Linux is concerned, it'd be a
> > bit of a pain to have to break this ABI because we did something brain-dead.
> > Since there's a bit of time before 7.3.0, I think it'd be OK to consider
> > breaking the profiling ABI if there's a good reason.
> >
>
> As far as I can tell, the `-pg` flag only inserts the _mcount call after every
> valid function prologue and seems breaking no existing ABI. But indeed
> it would be good if compiler guys can take a look at the gcc profiling
> features.
This is an interesting discussion, although I'm a bit confused. What
ABI are you worried about breaking?
-- Steve
next prev parent reply other threads:[~2017-12-13 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 2:31 [PATCH v2] riscv/ftrace: Add basic support Alan Kao
2017-12-11 18:15 ` [patches] " Palmer Dabbelt
2017-12-12 7:08 ` Alan Kao
2017-12-12 17:47 ` Jim Wilson
2017-12-13 0:37 ` Steven Rostedt
2017-12-13 0:34 ` Steven Rostedt [this message]
2017-12-13 0:57 ` [patches] " Alan Kao
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=20171212193420.3ba4e6d9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alankao@andestech.com \
--cc=albert@sifive.com \
--cc=greentime@andestech.com \
--cc=jimw@sifive.com \
--cc=kito@andestech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nonerkao@gmail.com \
--cc=palmer@sifive.com \
--cc=patches@groups.riscv.org \
--cc=pombredanne@nexb.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