From: Andi Kleen <ak@linux.intel.com>
To: Chun-Tse Shao <ctshao@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, terrelln@fb.com, leo.yan@arm.com,
dvyukov@google.com, james.clark@linaro.org,
christophe.leroy@csgroup.eu, ben.gainey@arm.com,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 1/2] perf record: Add 8-byte aligned event type PERF_RECORD_COMPRESSED2
Date: Wed, 26 Feb 2025 22:04:33 -0800 [thread overview]
Message-ID: <Z8AAcZXtuD7O3TAV@tassilo> (raw)
In-Reply-To: <20250227053738.788153-1-ctshao@google.com>
On Wed, Feb 26, 2025 at 09:34:06PM -0800, Chun-Tse Shao wrote:
> The original PERF_RECORD_COMPRESS is not 8-byte aligned, which can cause
> asan runtime error:
It seems pointless. Most architectures have cheap unaligned accesses
these days.
Just disable that error?
-Andi
next prev parent reply other threads:[~2025-02-27 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 5:34 [PATCH v1 1/2] perf record: Add 8-byte aligned event type PERF_RECORD_COMPRESSED2 Chun-Tse Shao
2025-02-27 5:34 ` [PATCH v1 2/2] perf record: Fix a asan runtime error in util/maps.c Chun-Tse Shao
2025-02-27 5:58 ` Ian Rogers
2025-02-27 5:57 ` [PATCH v1 1/2] perf record: Add 8-byte aligned event type PERF_RECORD_COMPRESSED2 Ian Rogers
2025-02-27 6:04 ` Andi Kleen [this message]
2025-02-27 6:20 ` Ian Rogers
2025-02-27 8:20 ` Namhyung Kim
2025-02-27 7:12 ` Ian Rogers
2025-02-27 8:35 ` Namhyung Kim
2025-02-27 18:21 ` Chun-Tse Shao
2025-03-01 0:32 ` Namhyung Kim
2025-03-03 5:13 ` Chun-Tse Shao
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=Z8AAcZXtuD7O3TAV@tassilo \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.gainey@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ctshao@google.com \
--cc=dvyukov@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=terrelln@fb.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