From: Omer Shpigelman <oshpigelman@habana.ai>
To: Oded Gabbay <oded.gabbay@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
SW_Drivers <SW_Drivers@habana.ai>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: RE: [PATCH 6/7] habanalabs: align armcp_packet structure to 8 bytes
Date: Thu, 18 Jun 2020 10:58:23 +0000 [thread overview]
Message-ID: <AM0PR02MB5523406D1B3BF4A17B392A4EB89B0@AM0PR02MB5523.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20200616061327.12006-6-oded.gabbay@gmail.com>
On Tue, Jun 13, 2020 at 09:13 AM, Oded Gabbay <oded.gabbay@gmail.com> wrote:
> Once there is a 64-bit field in a structure, GCC compiler for ARM aligns the
> structure to 8 bytes. In order to avoid confusion when these structures are
> being passed between CPUs from different architectures, we explicitly align
> the structure to 8 bytes.
>
> Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>
Reviewed-by: Omer Shpigelman <oshpigelman@habana.ai>
next prev parent reply other threads:[~2020-06-18 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 6:13 [PATCH 1/7] habanalabs: remove rate limiters from GAUDI Oded Gabbay
2020-06-16 6:13 ` [PATCH 2/7] habanalabs: Use pending CS amount per ASIC Oded Gabbay
2020-06-16 6:13 ` [PATCH 3/7] habanalabs: sync stream generic functionality Oded Gabbay
2020-06-16 6:13 ` [PATCH 4/7] habanalabs: Use mask instead of shift in sync stream registers Oded Gabbay
2020-06-16 6:13 ` [PATCH 5/7] uapi/habanalabs: fix some comments Oded Gabbay
2020-06-18 10:53 ` Omer Shpigelman
2020-06-16 6:13 ` [PATCH 6/7] habanalabs: align armcp_packet structure to 8 bytes Oded Gabbay
2020-06-18 10:58 ` Omer Shpigelman [this message]
2020-06-16 6:13 ` [PATCH 7/7] habanalabs: calculate trace frequency from PLL Oded Gabbay
2020-06-18 10:50 ` [PATCH 1/7] habanalabs: remove rate limiters from GAUDI Omer Shpigelman
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=AM0PR02MB5523406D1B3BF4A17B392A4EB89B0@AM0PR02MB5523.eurprd02.prod.outlook.com \
--to=oshpigelman@habana.ai \
--cc=SW_Drivers@habana.ai \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.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).