From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: Patrick Robb <probb@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>
Cc: dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Doug Foster <Doug.Foster@arm.com>, nd <nd@arm.com>
Subject: RE: meson error on ARM Grace server 23.11/22.11
Date: Tue, 29 Apr 2025 15:59:49 +0000 [thread overview]
Message-ID: <PAWPR08MB89094F996EAC0988995DE9899F802@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUBzSvUbrTMmMDhX0+QUY7nCsW0rVBnv+q6aEB3LZQ3SSw@mail.gmail.com>
> 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 for this
> system. Stable maintainers I'm not sure whether this should be addressed 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=1703
> 23.11: https://bugs.dpdk.org/show_bug.cgi?id=1702
+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.
prev parent reply other threads:[~2025-04-29 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:43 Patrick Robb
2025-04-29 8:30 ` Kevin Traynor
2025-04-29 11:03 ` Luca Boccassi
2025-04-29 15:59 ` Wathsala Wathawana Vithanage [this message]
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=PAWPR08MB89094F996EAC0988995DE9899F802@PAWPR08MB8909.eurprd08.prod.outlook.com \
--to=wathsala.vithanage@arm.com \
--cc=Doug.Foster@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=probb@iol.unh.edu \
--cc=stable@dpdk.org \
/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).