From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id C42024333B;
	Wed, 15 Nov 2023 22:31:19 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 0088D40A71;
	Wed, 15 Nov 2023 22:31:18 +0100 (CET)
Received: from dkmailrelay1.smartsharesystems.com
 (smartserver.smartsharesystems.com [77.243.40.215])
 by mails.dpdk.org (Postfix) with ESMTP id 09009402B2;
 Wed, 15 Nov 2023 22:31:17 +0100 (CET)
Received: from smartserver.smartsharesystems.com
 (smartserver.smartsharesys.local [192.168.4.10])
 by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id CCA7E206C3;
 Wed, 15 Nov 2023 22:31:17 +0100 (CET)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PATCH] eal: fix alignment of RISCV xmm vector type
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 15 Nov 2023 22:31:16 +0100
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F032@smartserver.smartshare.dk>
In-Reply-To: <1700083003-6641-1-git-send-email-roretzla@linux.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PATCH] eal: fix alignment of RISCV xmm vector type
Thread-Index: AdoYCQn+skD2DfrnTWOhweXUQUegbAAAS7xg
References: <1700083003-6641-1-git-send-email-roretzla@linux.microsoft.com>
From: =?iso-8859-1?Q?Morten_Br=F8rup?= <mb@smartsharesystems.com>
To: "Tyler Retzlaff" <roretzla@linux.microsoft.com>, <dev@dpdk.org>,
 "Stanislaw Kardach" <kda@semihalf.com>
Cc: "Michal Mazurek" <maz@semihalf.com>,
	<stable@dpdk.org>
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

> From: Tyler Retzlaff [mailto:roretzla@linux.microsoft.com]
> Sent: Wednesday, 15 November 2023 22.17
>=20
> Fix the alignment for rte_xmm_t it should be 16 instead of 8 bytes.
>=20
> Fixes: f22e705ebf12 ("eal/riscv: support RISC-V architecture")
> Cc: maz@semihalf.com
> Cc: stable@dpdk.org
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> ---

Reviewed-by: Morten Br=F8rup <mb@smartsharesystems.com>

As mentioned in the other thread:

We need to urgently decide if this bug should live on in DPDK 23.11, or =
if the fix should be included although we are very late in the release =
process.

Stanislaw, what do you think?

Furthermore, I wonder if it can be backported to stable, and to what =
extent backporting it would break the ABI/API.