From: David Marchand <david.marchand@redhat.com>
To: Phil Yang <phil.yang@arm.com>
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
dev <dev@dpdk.org>, Olivier Matz <olivier.matz@6wind.com>,
Dharmik Thakkar <dharmik.thakkar@arm.com>,
Gavin Hu <gavin.hu@arm.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] ring: fix unaligned memory access on aarch32
Date: Thu, 19 Mar 2020 16:56:11 +0100 [thread overview]
Message-ID: <CAJFAV8xD=44x7-QX6BoDA1gEKtmGLa=YZ1g6Rb6xYLAk1DaPAA@mail.gmail.com> (raw)
In-Reply-To: <1583774395-10233-1-git-send-email-phil.yang@arm.com>
On Mon, Mar 9, 2020 at 6:20 PM Phil Yang <phil.yang@arm.com> wrote:
>
> The 32-bit arm machine doesn't support unaligned memory access. It
> will cause a bus error on aarch32 with the custom element size ring.
>
> Thread 1 "test" received signal SIGBUS, Bus error.
> __rte_ring_enqueue_elems_64 (n=1, obj_table=0xf5edfe41, prod_head=0, \
> r=0xf5edfb80) at /build/dpdk/build/include/rte_ring_elem.h:177
> 177 ring[idx++] = obj[i++];
>
> Fixes: cc4b218790f6 ("ring: support configurable element size")
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Applied, thanks.
--
David Marchand
next prev parent reply other threads:[~2020-03-19 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:19 Phil Yang
2020-03-19 15:56 ` David Marchand [this message]
2023-11-04 0:04 ` Morten Brørup
2023-11-04 16:32 ` Honnappa Nagarahalli
2023-11-04 16:54 ` Morten Brørup
2023-11-10 8:39 ` Ruifeng Wang
2023-11-10 9:34 ` Morten Brørup
2023-11-10 9:44 ` Konstantin Ananyev
2023-11-10 10:43 ` Morten Brørup
2023-11-10 13:18 ` Morten Brørup
2023-11-13 6:39 ` Ruifeng Wang
2023-11-10 19:05 ` Konstantin Ananyev
2023-11-13 1:53 ` Honnappa Nagarahalli
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='CAJFAV8xD=44x7-QX6BoDA1gEKtmGLa=YZ1g6Rb6xYLAk1DaPAA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=phil.yang@arm.com \
--cc=ruifeng.wang@arm.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;
as well as URLs for NNTP newsgroup(s).