[PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
Borislav Petkov
bp@alien8.de
Thu Mar 14 16:33:45 GMT 2024
More information about the Binutils mailing list
Thu Mar 14 16:33:45 GMT 2024
- Previous message (by thread): [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
- Next message (by thread): [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
- Next message (by thread): [PATCH 0/1] Add XSAVE layout description to Core files for debuggers to support varying XSAVE layouts
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list