From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: David Aldrich <david.aldrich.ntml@gmail.com>,
users <users@dpdk.org>,
Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>,
nd <nd@arm.com>
Subject: Re: Arm Neoverse-V2 support?
Date: Wed, 6 Nov 2024 03:26:41 +0000 [thread overview]
Message-ID: <46EC6E62-D83D-4E22-A97E-FE9172074CF7@arm.com> (raw)
In-Reply-To: <CAJFAV8zueoYV+R93-tpdWkRW2PmXi3EOvkpDU58oqTjOTHK+PQ@mail.gmail.com>
> On Nov 5, 2024, at 1:50 PM, David Marchand <david.marchand@redhat.com> wrote:
>
> Hello,
>
> On Tue, Nov 5, 2024 at 7:08 PM David Aldrich
> <david.aldrich.ntml@gmail.com> wrote:
>>
>> Hi, we want to run DPDK on a NVIDIA Grace cpu. I tried building DPDK
>> v.23.11.1 with gcc 14.2 but got:
>>
>> Message: Arm implementer: Arm
>> Message: Arm part number: 0xd4f
>>
>> config/arm/meson.build:687:8: ERROR: Problem encountered: Unsupported
>> part number 0xd4f of implementer 0x41. Please add support for it or
>> use the generic (-Dplatform=generic) build.
>>
>> I think part number 0xd4f is ARM Neoverse-V2.
>>
>> I have seen some dpdk patch emails about support for Neoverse-V2 but I
>> don't know how to interpret them. Can anyone please tell me the dpdk
>> support status for this cpu, or tell me what we can do to workaround
>> this?
>
> IIUC, this was added in v24.03 in commit d007038c0121 ("config/arm:
> add NVIDIA Grace CPU").
> Cc: Honnappa.
It is not back ported. You can use the latest release or back port the patch.
>
> --
> David Marchand
>
prev parent reply other threads:[~2024-11-06 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:08 David Aldrich
2024-11-05 19:50 ` David Marchand
2024-11-06 3:26 ` Honnappa Nagarahalli [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=46EC6E62-D83D-4E22-A97E-FE9172074CF7@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=david.aldrich.ntml@gmail.com \
--cc=david.marchand@redhat.com \
--cc=nd@arm.com \
--cc=users@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).