From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw130307-130313 [PATCH] [v1, 7/7] eal: initialize worker threads once
Date: Mon, 14 Aug 2023 19:00:21 -0700 (PDT) [thread overview]
Message-ID: <64dadc35.630a0220.28ea8.b53aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/130307
_apply patch failure_
Submitter: Sinan Kaya <okaya@kernel.org>
Date: Tuesday, August 15 2023 01:38:26
Applied on: CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81
Apply patch set 130307-130313 failed:
Checking patch lib/eal/common/eal_common_options.c...
Hunk #1 succeeded at 1981 (offset -2 lines).
Checking patch lib/eal/linux/eal.c...
Hunk #1 succeeded at 79 (offset 1 line).
Hunk #2 succeeded at 507 (offset 1 line).
error: while searching for:
rte_eal_init(int argc, char **argv)
{
int i, fctret, ret;
static uint32_t run_once;
uint32_t has_run = 0;
const char *p;
static char logid[PATH_MAX];
error: patch failed: lib/eal/linux/eal.c:960
Applied patch lib/eal/common/eal_common_options.c cleanly.
Applying patch lib/eal/linux/eal.c with 1 reject...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Rejected hunk #3.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c (rejected hunks)
@@ -960,7 +963,6 @@ int
rte_eal_init(int argc, char **argv)
{
int i, fctret, ret;
- static uint32_t run_once;
uint32_t has_run = 0;
const char *p;
static char logid[PATH_MAX];
Checking patch lib/eal/common/eal_common_memory.c...
error: while searching for:
int retval;
RTE_LOG(DEBUG, EAL, "Setting up physically contiguous memory...\n");
if (!mcfg)
return -1;
/* lock mem hotplug here, to prevent races while we init */
rte_mcfg_mem_read_lock();
error: patch failed: lib/eal/common/eal_common_memory.c:1084
error: while searching for:
if (internal_conf->no_shconf == 0 && rte_eal_memdevice_init() < 0)
goto fail;
return 0;
fail:
rte_mcfg_mem_read_unlock();
error: patch failed: lib/eal/common/eal_common_memory.c:1106
Checking patch lib/eal/common/malloc_heap.c...
Hunk #1 succeeded at 1409 (offset 4 lines).
Hunk #2 succeeded at 1453 (offset 6 lines).
Applying patch lib/eal/common/eal_common_memory.c with 2 rejects...
Rejected hunk #1.
Rejected hunk #2.
Applied patch lib/eal/common/malloc_heap.c cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/lib/eal/common/eal_common_memory.c b/lib/eal/common/eal_common_memory.c (rejected hunks)
@@ -1084,10 +1084,14 @@ rte_eal_memory_init(void)
int retval;
RTE_LOG(DEBUG, EAL, "Setting up physically contiguous memory...\n");
+ static int initialized = 0;
if (!mcfg)
return -1;
+ if (initialized)
+ return 0;
+
/* lock mem hotplug here, to prevent races while we init */
rte_mcfg_mem_read_lock();
@@ -1106,6 +1110,7 @@ rte_eal_memory_init(void)
if (internal_conf->no_shconf == 0 && rte_eal_memdevice_init() < 0)
goto fail;
+ initialized = true;
return 0;
fail:
rte_mcfg_mem_read_unlock();
Checking patch lib/eal/linux/eal.c...
error: lib/eal/linux/eal.c: does not match index
hint: Use 'git am --show-current-patch' to see the failed patch
https://lab.dpdk.org/results/dashboard/patchsets/27337/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-08-15 2:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=64dadc35.630a0220.28ea8.b53aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).