DPDK patches and discussions
 help / color / mirror / Atom feed
From: Doug Foster <Doug.Foster@arm.com>
To: Patrick Robb <probb@iol.unh.edu>,
	Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, dev <dev@dpdk.org>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>
Subject: RE: meson error on ARM Grace server 23.11/22.11
Date: Fri, 16 May 2025 05:16:10 +0000	[thread overview]
Message-ID: <AS8PR08MB73396AB179C12ACDCBA214B5E593A@AS8PR08MB7339.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUD6tKB8xjiSMD7Ompy4TMGL__X682z_pNDbKAK54Vv+Lw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

Hi Patrick,

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

From: Patrick Robb <probb@iol.unh.edu>
Sent: Thursday, May 15, 2025 3:59 PM
To: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Cc: ci@dpdk.org; dev <dev@dpdk.org>; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; 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

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 PM Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com<mailto: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 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.

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 the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 5666 bytes --]

      reply	other threads:[~2025-05-16  5:17 UTC|newest]

Thread overview: 6+ 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
2025-05-15 20:59   ` Patrick Robb
2025-05-16  5:16     ` Doug Foster [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=AS8PR08MB73396AB179C12ACDCBA214B5E593A@AS8PR08MB7339.eurprd08.prod.outlook.com \
    --to=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 \
    --cc=wathsala.vithanage@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).