From: Akihiko Odaki <akihiko.odaki@daynix.com>
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 2/2] config/arm: Enable NUMA for generic Arm build
Date: Fri, 14 Apr 2023 21:41:39 +0900 [thread overview]
Message-ID: <20230414124139.66443-3-akihiko.odaki@daynix.com> (raw)
In-Reply-To: <20230414124139.66443-1-akihiko.odaki@daynix.com>
We enable NUMA even if the presence of NUMA is unknown for the other
architectures. Enable NUMA for generic Arm build too.
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
---
config/arm/meson.build | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 724c00ad7e..f8ee7cdafb 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -271,13 +271,15 @@ implementers = {
soc_generic = {
'description': 'Generic un-optimized build for armv8 aarch64 exec mode',
'implementer': 'generic',
- 'part_number': 'generic'
+ 'part_number': 'generic',
+ 'numa': true
}
soc_generic_aarch32 = {
'description': 'Generic un-optimized build for armv8 aarch32 exec mode',
'implementer': 'generic',
- 'part_number': 'generic_aarch32'
+ 'part_number': 'generic_aarch32',
+ 'numa': true
}
soc_armada = {
--
2.40.0
next prev parent reply other threads:[~2023-04-14 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 12:41 [PATCH 0/2] Enable " 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š
2023-04-14 12:41 ` Akihiko Odaki [this message]
2023-04-20 7:20 ` [PATCH 2/2] config/arm: Enable NUMA for generic Arm build 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=20230414124139.66443-3-akihiko.odaki@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ruifeng.wang@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).