From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [PATCH 1/2] config/arm: Do not require processor information
Date: Mon, 29 May 2023 09:37:40 +0200 [thread overview]
Message-ID: <CAOb5WZbvhyr10JkoYAJLpv+eJhxZQ=uUbid+VR8xuUKtSfMzsA@mail.gmail.com> (raw)
In-Reply-To: <0a075993-b671-89aa-871f-2317cc65faee@daynix.com>
[-- Attachment #1: Type: text/plain, Size: 3982 bytes --]
+ Lijuan
Hi Lijuan, Akihiko wonders whether it's possible to add the ability to do a
generic build in DTS. If I understand correctly, we don't pass -Dplatform
to meson build which results in native build which in turn is not supported
on all arm microarchitectures, resulting in failing builds. Adding the
ability to specify the value of -Dplatform would address this issue.
On Thu, May 4, 2023 at 5:08 PM Akihiko Odaki <akihiko.odaki@daynix.com>
wrote:
> On 2023/05/04 18:43, Ruifeng Wang wrote:
> >> -----Original Message-----
> >> From: Akihiko Odaki <akihiko.odaki@daynix.com>
> >> Sent: Thursday, May 4, 2023 3:47 PM
> >> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; Bruce Richardson <
> bruce.richardson@intel.com>;
> >> Juraj Linkeš <juraj.linkes@pantheon.tech>
> >> Cc: dev@dpdk.org; nd <nd@arm.com>
> >> Subject: Re: [PATCH 1/2] config/arm: Do not require processor
> information
> >>
> >> On 2023/04/20 16:12, Akihiko Odaki wrote:
> >>> On 2023/04/20 16:10, Ruifeng Wang wrote:
> >>>>> -----Original Message-----
> >>>>> From: Akihiko Odaki <akihiko.odaki@daynix.com>
> >>>>> Sent: Thursday, April 20, 2023 9:40 AM
> >>>>> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; Bruce Richardson
> >>>>> <bruce.richardson@intel.com>; Juraj Linkeš
> >>>>> <juraj.linkes@pantheon.tech>
> >>>>> Cc: dev@dpdk.org; nd <nd@arm.com>
> >>>>> Subject: Re: [PATCH 1/2] config/arm: Do not require processor
> >>>>> information
> >>>>>
> >>>>> On 2023/04/17 16:41, Ruifeng Wang wrote:
> >>>>>>> -----Original Message-----
> >>>>>>> From: Akihiko Odaki <akihiko.odaki@daynix.com>
> >>>>>>> Sent: Friday, April 14, 2023 8:42 PM
> >>>>>>> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; Bruce Richardson
> >>>>>>> <bruce.richardson@intel.com>
> >>>>>>> Cc: dev@dpdk.org; Akihiko Odaki <akihiko.odaki@daynix.com>
> >>>>>>> Subject: [PATCH 1/2] config/arm: Do not require processor
> >>>>>>> information
> >>>>>>>
> >>>>>>> DPDK can be built even without exact processor information for x86
> >>>>>>> and ppc so allow to build for Arm even if we don't know the
> >>>>>>> targeted processor is
> >>>>> unknown.
> >>>>>>
> >>>>>> Hi Akihiko,
> >>>>>>
> >>>>>> The design idea was to require an explicit generic build.
> >>>>>> Default/native build doesn't fall back to generic build when SoC
> >>>>>> info is not on the list.
> >>>>>> So the user has less chance to generate a suboptimal binary by
> >>>>>> accident.
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> It is true that the suboptimal binary can result, but the rationale
> >>>>> here is that we tolerate that for x86 and ppc so it should not
> >>>>> really matter for Arm too. On x86 and ppc you don't need to modify
> >>>>> meson.build just to run dts on a development machine.
> >>>>
> >>>> What modification do you need for a development machine?
> >>>> I suppose "meson setup build -Dplatform=generic" will generate a
> >>>> binary that can run on your development machine.
> >>>
> >>> I didn't describe the situation well. I use DPDK Test Suite for
> >>> testing and it determines what flags to be passed to Meson. You need
> >>> to modify DPDK's meson.build or DTS to get it built.
> >>>
> >>>>
> >>>>>
> >>>>> Regards,
> >>>>> Akihiko Odaki
> >>
> >> Hi,
> >>
> >> Can you have a look at this again?
> >
> > Thanks for the clarification of your use case.
> > Changes to DTS are in planning. It will allow the user to choose
> > the type of the build.
> > Your use case will be fulfilled then.
>
> Such a feature indeed satisfies my requirement. Thanks in advance,
> Akihiko Odaki
>
Hello Akihiko,
Sorry for the long delay in responding. I'm involved (I'm part of
Ruifeng's team) in refactoring/rewriting DTS which is where the support you
need is planned to be implemented, but that'll take a long time (this is
what Ruifeng meant). I've added Lijuan who may add the feature to the
original DTS. You can also add the feature yourself.
Regards,
Juraj
[-- Attachment #2: Type: text/html, Size: 6491 bytes --]
next prev parent reply other threads:[~2023-05-29 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 12:41 [PATCH 0/2] Enable generic Arm build Akihiko Odaki
2023-04-14 12:41 ` [PATCH 1/2] config/arm: Do not require processor information Akihiko Odaki
2023-04-17 7:41 ` Ruifeng Wang
2023-04-20 1:40 ` Akihiko Odaki
2023-04-20 7:10 ` Ruifeng Wang
2023-04-20 7:12 ` Akihiko Odaki
2023-05-04 7:47 ` Akihiko Odaki
2023-05-04 9:43 ` Ruifeng Wang
2023-05-04 15:08 ` Akihiko Odaki
2023-05-29 7:37 ` Juraj Linkeš [this message]
2023-04-14 12:41 ` [PATCH 2/2] config/arm: Enable NUMA for generic Arm build Akihiko Odaki
2023-04-20 7:20 ` Ruifeng Wang
2023-04-22 5:26 ` Akihiko Odaki
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='CAOb5WZbvhyr10JkoYAJLpv+eJhxZQ=uUbid+VR8xuUKtSfMzsA@mail.gmail.com' \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=akihiko.odaki@daynix.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=nd@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).