From: Kairui Song <kasong@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Dave Young <dyoung@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [RFC PATCH] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER
Date: Fri, 5 Apr 2019 23:21:03 +0800 [thread overview]
Message-ID: <CACPcB9eV37uuXyKw6KrJhpZM6j4OtjrW1JUixpaS=KpvG41NYQ@mail.gmail.com> (raw)
In-Reply-To: <20190405071704.GC4038@hirez.programming.kicks-ass.net>
On Fri, Apr 5, 2019 at 3:17 PM Peter Zijlstra <peterz@infradead.org> wrote:
>
> And you forgot to Cc Josh..
>
Hi, thanks for the reply and Cc more people, I just copies the list
from ./scripts/get_maintainer.pl, will pay more attention next time.
> >
> > Just found with ORC unwinder the perf callchain is unusable, and this
> > seems fixes it well, any suggestion is welcome, thanks!
>
> That whole .direct stuff is horrible crap.
>
Sorry if I did anything dumb, but I didn't find a better way to make
it work so sent this RFC... Would you mind tell me what I'm doing
wrong, or give any suggestion about how should I improve it?
--
Best Regards,
Kairui Song
next prev parent reply other threads:[~2019-04-05 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 17:25 [RFC PATCH] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER Kairui Song
2019-04-05 7:17 ` Peter Zijlstra
2019-04-05 15:21 ` Kairui Song [this message]
2019-04-05 14:09 ` Josh Poimboeuf
2019-04-05 15:13 ` Kairui Song
2019-04-05 16:57 ` Josh Poimboeuf
2019-04-05 17:05 ` Kairui Song
2019-04-05 17:26 ` Josh Poimboeuf
2019-04-05 18:55 ` Kairui Song
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='CACPcB9eV37uuXyKw6KrJhpZM6j4OtjrW1JUixpaS=KpvG41NYQ@mail.gmail.com' \
--to=kasong@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).