All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Khoronzhuk <ivan.khoronzhuk@gmail.com>
To: k-hagio-ab@nec.com, kexec@lists.infradead.org
Cc: Ivan Khoronzhuk <ikhoronz@cisco.com>
Subject: [RFC PATCH] makedumpfile: add userinfo elf section 0/4]
Date: Wed,  1 Dec 2021 15:47:26 +0200	[thread overview]
Message-ID: <20211201134730.15943-1-ikhoronz@cisco.com> (raw)

These patchset suggests feature to add user specific information along
with dumpfile. One of usecases could be a platform build information
containing dubug file addresses, sources of daily build, some
platform related information and more, it's gracefully simplifies
debugging process, since an engineer doesn't need to spend time on
finding to which platform this core file is related, where to get
debugging counter part and so on. As user info can be added along with
dumpfile it frees platform from creating tar achieve spending doubled
space or using specific tools. Since this information is sorted and
selected by user it can't be standardized and should be placed in some
special generic section. This patchset roughly proposes the variant when
user information is placed/retrieved as subsection of note elf
section.

Ivan Khoronzhuk (4):
  makedumpfile: rename check_dump_file() on check_file_is_writable()
  elf: add new "userinfo" ELF section to traverse debug information
  elf_info: make int note_descsz() and offset_next_note() public
  elf: add ability to read the userinfo data from note segment

 elf_info.c     |   4 +-
 elf_info.h     |   5 +
 makedumpfile.c | 393 ++++++++++++++++++++++++++++++++++++++++++++++++-
 makedumpfile.h |  12 ++
 4 files changed, 404 insertions(+), 10 deletions(-)

-- 
2.20.1


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2021-12-01 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 13:47 Ivan Khoronzhuk [this message]
2021-12-01 13:47 ` [RFC makedumpfile: add userinfo elf section 1/4] makedumpfile: rename check_dump_file() on check_file_is_writable() Ivan Khoronzhuk
2021-12-01 13:47 ` [RFC makedumpfile: add userinfo elf section 2/4] elf: add new "userinfo" ELF section to traverse debug information Ivan Khoronzhuk
2021-12-01 13:47 ` [RFC makedumpfile: add userinfo elf section 3/4] elf_info: make int note_descsz() and offset_next_note() public Ivan Khoronzhuk
2021-12-01 13:47 ` [RFC makedumpfile: add userinfo elf section 4/4] elf: add ability to read the userinfo data from note segment Ivan Khoronzhuk
2021-12-15  0:58 ` [RFC PATCH] makedumpfile: add userinfo elf section 0/4] HAGIO KAZUHITO(萩尾 一仁)

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=20211201134730.15943-1-ikhoronz@cisco.com \
    --to=ivan.khoronzhuk@gmail.com \
    --cc=ikhoronz@cisco.com \
    --cc=k-hagio-ab@nec.com \
    --cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.