> On May 28, 2019, at 11:16 AM, Michał Górny <[email protected]> wrote: > >> We already have very strange ones (XMMREGS and VECREGS). Maybe we should just >> have one ALLREGS thing (identical to the core note) and then discuss how >> to properly make that sanely versioned and self describing? >> > > That is somewhat the idea of option b., and what Intel&co seem to be > aiming it. With the exception of the two old register groups being left > separate, PT_*XSTATE would cover everything else. At the very least, the #ifdef around FP regs in the core dump code should probably be made into a proper MD hook in any case, so that the individual platform can decide which and how many of such notes to write out. -- thorpej
- Re: [RFC] Design considerations for XSAVE Extended A... Kamil Rytarowski
- Re: [RFC] Design considerations for XSAVE Extend... Michał Górny
- Re: [RFC] Design considerations for XSAVE Extended A... Martin Husemann
- Re: [RFC] Design considerations for XSAVE Extend... Jason Thorpe
- Re: [RFC] Design considerations for XSAVE Ex... Martin Husemann
- Re: [RFC] Design considerations for XSAV... Jason Thorpe
- Re: [RFC] Design considerations for... Martin Husemann
- Re: [RFC] Design considerations for XSAVE Extend... Michał Górny
- Re: [RFC] Design considerations for XSAVE Ex... Martin Husemann
- Re: [RFC] Design considerations for XSAV... Michał Górny
- Re: [RFC] Design considerations for... Jason Thorpe
- Re: [RFC] Design considerations for XSAV... Kamil Rytarowski
- Re: [RFC] Design considerations for XSAVE Extended Area g... Paul Goyette
