From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: "Beckius, Mikael" <mikael.beckius@windriver.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] lttng-consumerd crash on aarch64 due to x86 arch specific optimization
Date: Thu, 2 Feb 2023 11:26:26 -0500 [thread overview]
Message-ID: <ea3518a5-e539-1616-432c-b7fe7fcada2f@efficios.com> (raw)
In-Reply-To: <d1eb23d9-269f-85ea-0b7a-a3b779ffa843@efficios.com>
Hi Mikael,
I just tried another approach to fix this issue, see:
https://review.lttng.org/c/lttng-ust/+/9413 Fix: use unaligned pointer accesses for lttng_inline_memcpy
It is less intrusive than other approaches, and does not change the generated code on the
most relevant architectures.
Feedback is welcome,
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-02-02 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 6:50 Beckius, Mikael via lttng-dev
2023-01-31 16:08 ` Mathieu Desnoyers via lttng-dev
2023-01-31 16:18 ` Mathieu Desnoyers via lttng-dev
2023-01-31 16:32 ` Mathieu Desnoyers via lttng-dev
2023-02-02 16:26 ` Mathieu Desnoyers via lttng-dev [this message]
2023-02-06 15:21 ` Beckius, Mikael via lttng-dev
2023-02-06 16:15 ` Beckius, Mikael via lttng-dev
2023-02-06 16:39 ` Mathieu Desnoyers via lttng-dev
[not found] <CAF2baFfZ+sxAGfxGY_or7=JJMxDngZTtfrzruUC5=RnZFD4tvA@mail.gmail.com>
[not found] ` <954909194.21985.1511551181212.JavaMail.zimbra@efficios.com>
[not found] ` <CAF2baFecVMCenooHSMcNChMEkevz1taF0VWUxWAyxbUq8kVXSg@mail.gmail.com>
2023-01-25 12:25 ` Mathieu Desnoyers via lttng-dev
2023-01-26 19:32 ` Anders Wallin via lttng-dev
2023-01-26 19:47 ` Mathieu Desnoyers via lttng-dev
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=ea3518a5-e539-1616-432c-b7fe7fcada2f@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mikael.beckius@windriver.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