From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: dev@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Lewis Donzis <lew@perftech.com>,
Dmitry Kozlyuk <kozlyuk@bifit.com>
Subject: [PATCH v2 0/2] Hugepage inclusion in core dump
Date: Fri, 25 Oct 2024 23:26:13 +0300 [thread overview]
Message-ID: <20241025202615.2581513-1-dmitry.kozliuk@gmail.com> (raw)
In-Reply-To: <20241023231859.1323727-1-kozlyuk@bifit.com>
From: Dmitry Kozlyuk <kozlyuk@bifit.com>
Hugepages often contain information useful for debugging
and thus desired for inclusion in core dumps.
However, including them has implications and drawbacks,
so it must be an opt-in at user's discretion.
This patchset add the ability to do so for FreeBSD
and for Linux it just documents existing settings.
v2: * Make it work for FreeBSD (thanks Lewis for testing).
* Drop all EAL code, document required user actions.
Dmitry Kozlyuk (2):
contigmem: support including mapped buffers in core dump
doc: add instruction for including hugepages in core dump
doc/guides/freebsd_gsg/build_dpdk.rst | 26 ++++++++++++++++------
doc/guides/linux_gsg/build_sample_apps.rst | 17 ++++++++++++++
kernel/freebsd/contigmem/contigmem.c | 8 +++++++
3 files changed, 44 insertions(+), 7 deletions(-)
--
2.38.4
next prev parent reply other threads:[~2024-10-25 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 23:18 [PATCH] eal: support including mapped memory " Dmitry Kozlyuk
2024-10-24 2:19 ` Stephen Hemminger
2024-10-24 2:31 ` Stephen Hemminger
2024-10-24 7:07 ` Morten Brørup
2024-10-24 7:22 ` Morten Brørup
2024-10-24 8:25 ` Dmitry Kozlyuk
2024-10-24 12:55 ` Lewis Donzis
2024-10-24 16:38 ` Stephen Hemminger
2024-10-24 20:54 ` Dmitry Kozlyuk
2024-10-25 0:22 ` Dmitry Kozlyuk
2024-10-25 20:26 ` Dmitry Kozlyuk [this message]
2024-10-25 20:26 ` [PATCH v2 1/2] contigmem: support including mapped buffers " Dmitry Kozlyuk
2024-10-25 20:26 ` [PATCH v2 2/2] doc: add instruction for including hugepages " Dmitry Kozlyuk
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=20241025202615.2581513-1-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kozlyuk@bifit.com \
--cc=lew@perftech.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).