From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw61898[v5, 2/2] eal: use base address hint to reserve space for mem config
Date: 25 Oct 2019 06:42:30 -0700 [thread overview]
Message-ID: <ee68f5$8d5vp5@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/61898
_apply issues_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: 2019-10-24 12:36:50
Reply_mail: e8d1128c93881950d23d44913ebec32cf3e5313e.1571920604.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 927a0e20e2415f718ceb346cd94bbf930ad9f29a
*Repo: dpdk
}
rte_mem_cfg_addr = mmap(NULL, sizeof(*rte_config.mem_config),
PROT_READ | PROT_WRITE, MAP_SHARED, mem_cfg_fd, 0);
if (rte_mem_cfg_addr == MAP_FAILED){
RTE_LOG(ERR, EAL, "Cannot mmap memory for rte_config\n");
close(mem_cfg_fd);
mem_cfg_fd = -1;
return -1;
}
memcpy(rte_mem_cfg_addr, &early_mem_config, sizeof(early_mem_config));
rte_config.mem_config = rte_mem_cfg_addr;
error: patch failed: lib/librte_eal/freebsd/eal/eal.c:253
error: lib/librte_eal/freebsd/eal/eal.c: patch does not apply
Checking patch lib/librte_eal/linux/eal/eal.c...
DPDK STV team
reply other threads:[~2019-10-25 13:42 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='ee68f5$8d5vp5@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--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).