Re: [PATCH] x86, fpu: correct XSAVE xstate size calculation

[Dave Hansen]

On 08/08/2015 02:06 AM, Ingo Molnar wrote:
>>> What sense does it make to have a blob we don't know the exact layout of? How will 
>>> > > debuggers or user-space in general be able to print (and change) the register 
>>> > > values if they don't know the layout?
>> > 
>> > Ingo, we know the layout.  We know where every component is.  We know
>> > how big each component is.  This patch does not change the fact that we
>> > calculate and store that.
> The patch you submitted blindly trusts the CPU, and I'm uneasy about that for 
> multiple reasons. We can and should do better than that, while still flexibly 
> making use of all CPU capabilities that are offered.

Yes, it blindly trusts the CPU.  This is precisely* what the *existing*
code has done since commit dc1e35c6e95 got merged in 2008.  Do you have
some specific concern with the compact format that makes you want to
stop blindly trusting the CPU after 7 years?

I know what you want now (I've coded up half of it already), but I've
not got the foggiest idea why other than pure paranoia.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/