From: Greg KH <gregkh@linuxfoundation.org>
To: acme@kernel.org
Cc: stable@vger.kernel.org, Jesper Dangaard Brouer <hawk@kernel.org>,
Artem Savkov <asavkov@redhat.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Milian Wolff <milian.wolff@kdab.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 6.4.y 1/1] Revert "perf report: Append inlines to non-DWARF callchains"
Date: Mon, 21 Aug 2023 18:42:43 +0200 [thread overview]
Message-ID: <2023082133-humility-quack-3c9c@gregkh> (raw)
In-Reply-To: <20230815180342.274263-1-acme@kernel.org>
On Tue, Aug 15, 2023 at 03:03:42PM -0300, acme@kernel.org wrote:
> From: Arnaldo Carvalho de Melo <acme@kernel.org>
>
> This reverts commit 46d21ec067490ab9cdcc89b9de5aae28786a8b8e.
>
> The tests were made with a specific workload, further tests on a
> recently updated fedora 38 system with a system wide perf.data file
> shows 'perf report' taking excessive time resolving inlines in vmlinux,
> so lets revert this until a full investigation and improvement on the
> addr2line support code is made.
>
> Reported-by: Jesper Dangaard Brouer <hawk@kernel.org>
> Acked-by: Artem Savkov <asavkov@redhat.com>
> Tested-by: Jesper Dangaard Brouer <hawk@kernel.org>
> Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Ian Rogers <irogers@google.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Milian Wolff <milian.wolff@kdab.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Link: https://lore.kernel.org/r/ZMl8VyhdwhClTM5g@kernel.org
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> (cherry picked from commit c0b067588a4836b762cfc6a4c83f122ca1dbb93a)
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-08-21 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 16:50 FAILED: patch "[PATCH] Revert "perf report: Append inlines to non-DWARF callchains"" failed to apply to 6.4-stable tree gregkh
2023-08-15 18:03 ` [PATCH 6.4.y 1/1] Revert "perf report: Append inlines to non-DWARF callchains" acme
2023-08-21 16:42 ` Greg KH [this message]
2023-08-15 18:04 ` FAILED: patch "[PATCH] Revert "perf report: Append inlines to non-DWARF callchains"" failed to apply to 6.4-stable tree Arnaldo Carvalho de Melo
2023-08-21 16:41 ` Greg KH
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=2023082133-humility-quack-3c9c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=asavkov@redhat.com \
--cc=hawk@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=milian.wolff@kdab.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.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