From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 123F5467A0; Tue, 20 May 2025 19:20:17 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CA1E640DD5; Tue, 20 May 2025 19:20:16 +0200 (CEST) Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) by mails.dpdk.org (Postfix) with ESMTP id 91F3E40DD5 for ; Tue, 20 May 2025 19:20:15 +0200 (CEST) Received: by mail-pg1-f179.google.com with SMTP id 41be03b00d2f7-af59c920d32so3794277a12.0 for ; Tue, 20 May 2025 10:20:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1747761614; x=1748366414; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TPdTVn2OvQhd/R2haD/e5W2a66WJHaNJ5qnizNUMJ4g=; b=FzFjcwN+opQylmKB0DXYUnGWWLim1ZLMtRPGSjBg5D96RIjvjSBpklRJWUg8+9fNfd P+laWhym62ceuuLhvV+g1PZU3KmlILuv5zwTkO5phUkug+rEzJzLZHXQLc8YnoUJUxiN 6axnMYtFs5+r7+bBSAgbMigpGurBUw6PpMMgg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747761614; x=1748366414; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TPdTVn2OvQhd/R2haD/e5W2a66WJHaNJ5qnizNUMJ4g=; b=RZg+0IYCDMljY828SGR2kE6nJbFkJZEUsyP1D5MOlizIteNN3Q67abjdrqrpphDKLu fqaoSM2Ngun09jYQOfD/hvufgIu7j9WtZz4KWzluWpA72HQjd2n9YwrYdekIVOrVOVnJ cJSRGQaCOd0TK5FHugMdZQALi1dY/bNBoWA++TU6zT9P78+S2LSlMxWEmUEfdGQeefMM rXve0bg+PnD7sVy8kCDeHF1Go55fEtPJRjTOiqOUZcWECbLPsWM5tPOJcKPWN/8cf0co EJY3zQvcKK+2hAzjDp1x7sWc/kwkLFDfe+u6wkdIb+R/sjHCWM9pk0Zw2reiXnIqGMbl IZOQ== X-Forwarded-Encrypted: i=1; AJvYcCXvTHL1gt8uDusYynvB1BB9LIT1ICiRGqn8qHgqTFO1G4j6aSnabi+uo7vFHGZUP8SbJHE=@dpdk.org X-Gm-Message-State: AOJu0YylAF20NCwsBkqRImt/6f/QLExc+9VP+qg23zwOHnk5p4StfcjI k+98ziAvGNdsXvaUptx0QwZxkq75oe/OWlnoVyi1sl69sj3BWQ6U/1wZ3lkMklNGG8m0Hsm+gFC r/x0wY/isgKGCNL6w31zTb7pcUFxDCe5MCQP0PERgPA== X-Gm-Gg: ASbGncukz5PSaFlYGSECyZwmJXE2EI7r+f2BRaTopTlpkfMv5g5b5RQ6JO2NEyTCA+S q6l1oUahYxxKmll1EXFwUV1R/56lIasZGGBsr97Mtz/irzhcsrsEtz7vR+ylp70J982CKYo23WB yWhPiO/0nlknsikPwbZdtT7UqX1wiuf1fLegOxfcavyh4FBwy+zF5illSN0dJaZSuRMA== X-Google-Smtp-Source: AGHT+IG5WMrMHXrckWVeS5rC2jfs4FduFIHSsziGVvSBeTYPkhKZDMhz0yVrB/qoXPzSwG22BeTbqFU+lXBor5Jgl3w= X-Received: by 2002:a17:903:41cc:b0:223:325c:89de with SMTP id d9443c01a7336-231d43d9c96mr244563675ad.1.1747761614504; Tue, 20 May 2025 10:20:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Robb Date: Tue, 20 May 2025 13:15:27 -0400 X-Gm-Features: AX0GCFuPuqUnkBAjWXhXZOtPzf-ck_fwqFc0ekoabksQDXuoog2MT5eplK4bMXQ Message-ID: Subject: Re: meson error on ARM Grace server 23.11/22.11 To: Doug Foster Cc: "ci@dpdk.org" , dev , Honnappa Nagarahalli , "stable@dpdk.org" , nd , Wathsala Wathawana Vithanage Content-Type: multipart/alternative; boundary="0000000000002f65590635947668" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000002f65590635947668 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Doug, Without overburdening you with details, at the CI lab we have some tests which run with werror=3Dtrue (treat warnings as errors) and some which run without it. The tests which I'm currently trying to extend to LTS for Grace do not have this flag included, i.e. they are tolerant to warnings. So, we should be good to proceed with your patch. Although no warnings on 22.11 and 23.11 would open us up to adding werror=3Dtrue build tests directly on Grace in the future, there isn't an a= sk for this right now and I don't think we will need to support it. So, again I think we can proceed with your patch as is. Thanks for handling this. On Tue, May 20, 2025 at 1:00=E2=80=AFPM Doug Foster w= rote: > Hi Patrick, > > While building 22.11 and 23.11 with GCC 13.3, I noticed compiler warnings > related to memcpy usage, specifically involving __builtin___memcpy_chk > failures. > Would these warnings be a concern for CI test runs, or are they generally > tolerated? > > From: Doug Foster > Sent: Friday, May 16, 2025 12:16 AM > To: Patrick Robb ; Wathsala Wathawana Vithanage < > wathsala.vithanage@arm.com> > Cc: ci@dpdk.org; dev ; Honnappa Nagarahalli < > Honnappa.Nagarahalli@arm.com>; stable@dpdk.org; nd > Subject: RE: meson error on ARM Grace server 23.11/22.11 > > Hi Patrick, > > I will produce the patches with necessary changes to build on Grace for > 22.11 and 23.11. > > From: Patrick Robb > Sent: Thursday, May 15, 2025 3:59 PM > To: Wathsala Wathawana Vithanage > Cc: mailto:ci@dpdk.org; dev ; Honnappa Nagarahalli > ; mailto:stable@dpdk.org; Doug > Foster ; nd > Subject: Re: meson error on ARM Grace server 23.11/22.11 > > Thanks Wathsala, > > How can we help on the UNH side? Do you want us to produce the 22.11 and > 23.11 diffs/patches, which would be based on d007038, with some > modifications based on what you had said to Doug? > > I'm not sure what the process looks like exactly for providing backports > to LTS maintainers. > > On Tue, Apr 29, 2025 at 12:00=E2=80=AFPM Wathsala Wathawana Vithanage wathsala.vithanage@arm.com> wrote: > > Hi, > > > > At the DPDK Community Lab we have been running CI tests with a new ARM > > Grace server for the past couple of months on main and next-* branches. > I am > > trying to add LTS runs now, and ran into a snag with 23.11 and 22.11 fo= r > this > > system. Stable maintainers I'm not sure whether this should be addresse= d > or not > > for hardware which is new and didn't exist when 22.11 and 23.11 were > > released... but I figured I'd make the tickets and find out. I attached > the meson > > logs to the tickets and if for whatever reason you guys want to remote > into this > > machine, I'm happy to setup the VPN and SSH access. > > > > 22.11: https://bugs.dpdk.org/show_bug.cgi?id=3D1703 > > 23.11: https://bugs.dpdk.org/show_bug.cgi?id=3D1702 > > +doug > > neoverse-v2 is supported in the GCC 13.3 used for this build although > -mtune/-mcpu > for grace is not available in that version. > Adding neoverse-v2 and soc_grace with crypto extension should bring these > releases > on par with latest. > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy th= e > information in any medium. Thank you. > --0000000000002f65590635947668 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Doug,=C2=A0

Without overburdening yo= u with details, at the CI lab we have some tests which run with werror=3Dtr= ue (treat warnings as errors) and some which run without it. The tests whic= h I'm currently trying to extend to LTS for Grace do not have this flag= included, i.e. they are tolerant to warnings. So, we should be good to pro= ceed with your patch.

Although no warnings on 22.1= 1 and 23.11 would open us up to adding werror=3Dtrue build tests directly o= n Grace in the future, there isn't an=C2=A0ask for this right now and I= don't think we will need to support it. So, again I think we can proce= ed with your patch as is.

Thanks for handling this= .=C2=A0

On Tue, May 20, 2025 at 1:00=E2=80=AFPM Doug Foster <Doug.Foster@arm.com&= gt; wrote:
Hi Pa= trick,

While building 22.11 and 23.11 with GCC 13.3, I noticed compiler warnings r= elated to memcpy usage, specifically involving __builtin___memcpy_chk failu= res.
Would these warnings be a concern for CI test runs, or are they generally t= olerated?

From: Doug Foster
Sent: Friday, May 16, 2025 12:16 AM
To: Patrick Robb <probb@iol.unh.edu>; Wathsala Wathawana Vithanage <wathsala.vithanage@arm.co= m>
Cc: ci@dpdk.org; dev &= lt;dev@dpdk.org>; = Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; stable@dpdk.org; nd <nd@arm.com>
Subject: RE: meson error on ARM Grace server 23.11/22.11

Hi Patrick,

I will produce the patches with necessary changes to build on Grace for 22.= 11 and 23.11.

From: Patrick Robb <mailto:probb@iol.unh.edu>
Sent: Thursday, May 15, 2025 3:59 PM
To: Wathsala Wathawana Vithanage <mailto:wathsala.vithanage@arm.com>
Cc: mailto:ci@dpdk.org= ; dev <mailto:dev@dpdk= .org>; Honnappa Nagarahalli <mailto:Honnappa.Nagarahalli@arm.com>; = mailto:stable@dpdk.org= ; Doug Foster <mailto:Doug.Foster@arm.com>; nd <mailto:nd@arm.com>
Subject: Re: meson error on ARM Grace server 23.11/22.11

Thanks Wathsala,

How can we help on the UNH side? Do you want us to produce the 22.11 and 23= .11 diffs/patches, which would be based on d007038, with some modifications= based on what you had said to Doug?

I'm not sure what the process looks like exactly for providing backport= s to LTS maintainers.

On Tue, Apr 29, 2025 at 12:00=E2=80=AFPM Wathsala Wathawana Vithanage <m= ailto:waths= ala.vithanage@arm.com> wrote:
> Hi,
>
> At the DPDK Community Lab we have been running CI tests with a new ARM=
> Grace server for the past couple of months on main and next-* branches= . I am
> trying to add LTS runs now, and ran into a snag with 23.11 and 22.11 f= or this
> system. Stable maintainers I'm not sure whether this should be add= ressed or not
> for hardware which is new and didn't exist when 22.11 and 23.11 we= re
> released... but I figured I'd make the tickets and find out. I att= ached the meson
> logs to the tickets and if for whatever reason you guys want to remote= into this
> machine, I'm happy to setup the VPN and SSH access.
>
> 22.11: https://bugs.dpdk.org/show_bug.cgi?id=3D1703=
> 23.11: https://bugs.dpdk.org/show_bug.cgi?id=3D1702=

+doug

neoverse-v2 is supported in the GCC 13.3 used for this build although -mtun= e/-mcpu
for grace is not available in that version.
Adding neoverse-v2 and soc_grace with crypto extension should bring these r= eleases
on par with latest.
IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you.
--0000000000002f65590635947668--