From: Borislav Petkov <bp@alien8.de>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>
Cc: Vignesh Balasubramanian <vigbalas@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-toolchains@vger.kernel.org"
<linux-toolchains@vger.kernel.org>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"christophe.leroy@csgroup.eu" <christophe.leroy@csgroup.eu>,
"aneesh.kumar@kernel.org" <aneesh.kumar@kernel.org>,
"naveen.n.rao@linux.ibm.com" <naveen.n.rao@linux.ibm.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"x86@kernel.org" <x86@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"jinisusan.george@amd.com" <jinisusan.george@amd.com>,
"matz@suse.de" <matz@suse.de>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"jhb@FreeBSD.org" <jhb@freebsd.org>
Subject: Re: [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
Date: Thu, 14 Mar 2024 17:33:45 +0100 [thread overview]
Message-ID: <20240314163345.GBZfMm6Ve5QMY_xPjl@fat_crate.local> (raw)
In-Reply-To: <MN2PR11MB4566BF54DEFF9B7627B096B78E292@MN2PR11MB4566.namprd11.prod.outlook.com>
On Thu, Mar 14, 2024 at 04:25:44PM +0000, Willgerodt, Felix wrote:
> I am wondering if it wouldn't be easier for everyone if corefiles would just
> contain space for all possible XSAVE components?
You mean we should shuffle out from the kernel 8K of AMX state even if
nothing uses it or the machine doesn't even support it?
That's silly.
Please have a look at this:
+struct xfeat_component {
+ u32 xfeat_type;
+ u32 xfeat_sz;
+ u32 xfeat_off;
+ u32 xfeat_flags;
+} __packed;
What is wrong with having a blob of such xfeat_component things
describing the XSTATE buffer and parsing it in gdb?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-03-14 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 11:23 Vignesh Balasubramanian
2024-03-14 11:23 ` [PATCH 1/1] x86/elf: Add a new .note section containing Xfeatures information to x86 core files Vignesh Balasubramanian
2024-03-14 15:37 ` Dave Hansen
2024-03-14 16:08 ` Borislav Petkov
2024-03-14 16:19 ` Dave Hansen
2024-03-14 16:29 ` Borislav Petkov
2024-03-14 16:39 ` Dave Hansen
2024-03-26 9:59 ` Balasubrmanian, Vignesh
2024-03-15 23:51 ` Thomas Gleixner
2024-03-16 10:29 ` Borislav Petkov
2024-03-14 16:45 ` John Baldwin
2024-03-14 17:10 ` Dave Hansen
2024-03-14 17:36 ` John Baldwin
2024-03-14 17:05 ` John Baldwin
2024-03-14 16:13 ` Kees Cook
2024-03-26 10:06 ` Balasubrmanian, Vignesh
2024-03-14 22:13 ` Michael Ellerman
2024-03-26 10:09 ` Balasubrmanian, Vignesh
2024-03-15 9:59 ` kernel test robot
2024-03-15 12:59 ` kernel test robot
2024-03-14 16:25 ` [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts Willgerodt, Felix
2024-03-14 16:33 ` Borislav Petkov [this message]
2024-03-15 8:43 ` Willgerodt, Felix
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=20240314163345.GBZfMm6Ve5QMY_xPjl@fat_crate.local \
--to=bp@alien8.de \
--cc=aneesh.kumar@kernel.org \
--cc=binutils@sourceware.org \
--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=vigbalas@amd.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