From: Li Feng <fengli@smartx.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Li Feng <fengli@smartx.com>
Subject: [PATCH v2] eal/linux: enable the hugepage mem dump
Date: Fri, 1 Apr 2022 17:10:04 +0800 [thread overview]
Message-ID: <20220401091004.3227117-1-fengli@smartx.com> (raw)
In-Reply-To: <20220308094125.2716847-1-fengli@smartx.comOD>
These hugepages include important structures. we should dump these
hugepages into a coredump file for debugging when generating a coredump.
Signed-off-by: Li Feng <fengli@smartx.com>
---
lib/eal/linux/eal_memalloc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/eal/linux/eal_memalloc.c b/lib/eal/linux/eal_memalloc.c
index f8b1588cae..93c4f396cf 100644
--- a/lib/eal/linux/eal_memalloc.c
+++ b/lib/eal/linux/eal_memalloc.c
@@ -677,6 +677,8 @@ alloc_seg(struct rte_memseg *ms, void *addr, int socket_id,
__func__);
#endif
+ eal_mem_set_dump(addr, alloc_sz, true);
+
huge_recover_sigbus();
ms->addr = addr;
--
2.35.1
next parent reply other threads:[~2022-04-01 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220308094125.2716847-1-fengli@smartx.comOD>
2022-04-01 9:10 ` Li Feng [this message]
2022-04-05 22:46 ` Stephen Hemminger
2022-04-05 23:14 ` Dmitry Kozlyuk
2023-07-05 23:19 ` Stephen Hemminger
2022-04-06 2:11 ` Li Feng
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=20220401091004.3227117-1-fengli@smartx.com \
--to=fengli@smartx.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).