[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9389b35-c1ef-4a53-9eb2-051df0aaf33d@intel.com>
Date: Fri, 7 Mar 2025 11:09:42 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Chao Gao <chao.gao@...el.com>, tglx@...utronix.de, x86@...nel.org,
seanjc@...gle.com, pbonzini@...hat.com, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: peterz@...radead.org, rick.p.edgecombe@...el.com,
weijiang.yang@...el.com, john.allen@....com, bp@...en8.de
Subject: Re: [PATCH v3 00/10] Introduce CET supervisor state support
On 3/7/25 08:41, Chao Gao wrote:
> case |IA32_XSS[12] | Space | RFBM[12] | Drop%
> -----+-------------+-------+----------+------
> 1 | 0 | None | 0 | 0.0%
> 2 | 1 | None | 0 | 0.2%
> 3 | 1 | 24B? | 1 | 0.2%
So, 0.2% is still, what, dozens of cycles? Are you sure that it really
takes the CPU dozens of cycles to skip over the feature during XSAVE?
If it really turns out to be this measurable, we should probably follow
up with the folks that implement XSAVE and see what's going on under the
covers.
On a separate note, I was bugging Thomas a bit on IRC. His memory was
that the AMX-era FPU rework only expected KVM to support user features.
You might want to dig through the history a bit and see if _that_ was
ever properly addressed because that would change the problem you're
trying to solve.
Powered by blists - more mailing lists