From: Vignesh Balasubramanian <vigbalas@amd.com>
To: <linux-kernel@vger.kernel.org>, <linux-toolchains@vger.kernel.org>
Cc: <mpe@ellerman.id.au>, <npiggin@gmail.com>,
<christophe.leroy@csgroup.eu>, <aneesh.kumar@kernel.org>,
<naveen.n.rao@linux.ibm.com>, <ebiederm@xmission.com>,
<keescook@chromium.org>, <x86@kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-mm@kvack.org>,
<bpetkov@amd.com>, <jinisusan.george@amd.com>, <matz@suse.de>,
<binutils@sourceware.org>, <jhb@FreeBSD.org>,
<felix.willgerodt@intel.com>,
Vignesh Balasubramanian <vigbalas@amd.com>
Subject: [PATCH v2 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
Date: Tue, 7 May 2024 15:23:29 +0530 [thread overview]
Message-ID: <20240507095330.2674-1-vigbalas@amd.com> (raw)
This patch proposes to add an extra .note section in the corefile to dump the CPUID information of a machine. This is being done to solve the issue of tools like the debuggers having to deal with coredumps from machines with varying XSAVE layouts in spite of having the same XCR0 bits. The new proposed .note section, at this point, consists of an array of records containing the information of each extended feature that is present. This provides details about the offsets and the sizes of the various extended save state components of the machine where the application crash occurred. Requesting a review for this patch.
Please NOTE that this patch has to be applied on top of the patch (https://lore.kernel.org/lkml/874jbt7qz3.fsf@oldenburg3.str.redhat.com/T/).
Vignesh Balasubramanian (1):
x86/elf: Add a new .note section containing Xfeatures information to
x86 core files
arch/x86/Kconfig | 1 +
arch/x86/include/asm/elf.h | 34 +++++++++
arch/x86/kernel/fpu/xstate.c | 141 +++++++++++++++++++++++++++++++++++
fs/binfmt_elf.c | 4 +-
include/uapi/linux/elf.h | 1 +
5 files changed, 179 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-05-07 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 9:53 Vignesh Balasubramanian [this message]
2024-05-07 9:53 ` [PATCH v2 1/1] x86/elf: Add a new .note section containing Xfeatures information to x86 core files Vignesh Balasubramanian
2024-05-07 23:40 ` kernel test robot
2024-05-08 0:13 ` kernel test robot
2024-05-08 8:04 ` Kees Cook
2024-05-08 13:02 ` Thomas Gleixner
2024-05-22 13:12 ` Balasubrmanian, Vignesh
2024-05-22 15:34 ` Borislav Petkov
[not found] ` <902b1bf0-15e6-42df-8f86-21387deef437@amd.com>
2024-05-23 14:45 ` Borislav Petkov
2024-05-26 4:54 ` Balasubrmanian, Vignesh
2024-05-26 9:05 ` Borislav Petkov
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=20240507095330.2674-1-vigbalas@amd.com \
--to=vigbalas@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=binutils@sourceware.org \
--cc=bpetkov@amd.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ebiederm@xmission.com \
--cc=felix.willgerodt@intel.com \
--cc=jhb@FreeBSD.org \
--cc=jinisusan.george@amd.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matz@suse.de \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=x86@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).