Re: [tip:x86/urgent] x86/fpu: Set the xcomp_bv when we fake up a XSAVES area
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/urgent] x86/fpu: Set the xcomp_bv when we fake up a XSAVES area
- From: Kevin Hao <haokexin@xxxxxxxxx>
- Date: Tue, 24 Jan 2017 10:09:21 +0800
- Cc: Yu-cheng Yu <yu-cheng.yu@xxxxxxxxx>, fenghua.yu@xxxxxxxxx, dvlasenk@xxxxxxxxxx, peterz@xxxxxxxxxxxxx, oleg@xxxxxxxxxx, mingo@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, brgerst@xxxxxxxxx, luto@xxxxxxxxxx, bp@xxxxxxxxx, jpoimboe@xxxxxxxxxx, hpa@xxxxxxxxx, quentin.casasnovas@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, riel@xxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <1b4e8b6c-c143-1867-712c-8b2e336a6ce0@linux.intel.com>
- References: <f2fb890d-f8ff-69e2-acc7-b3c810d6cf02@linux.intel.com> <20170123165529.GA4996@test-lenovo> <2be814b7-9fd6-7955-b4e3-6ecb4ef76052@linux.intel.com> <20170123205725.GA3920@test-lenovo> <90b0fbee-273b-31c2-6fe9-228f00c0a205@linux.intel.com> <20170123211640.GA3976@test-lenovo> <20170124001447.GD15017@pek-khao-d1> <0d717394-eaf0-4d29-1aae-218ffcc8f06b@linux.intel.com> <20170124015012.GA9969@pek-khao-d1> <1b4e8b6c-c143-1867-712c-8b2e336a6ce0@linux.intel.com>
- User-agent: Mutt/1.7.1 (2016-10-04)
On Mon, Jan 23, 2017 at 06:01:10PM -0800, Dave Hansen wrote:
> On 01/23/2017 05:50 PM, Kevin Hao wrote:
> > According to the ISA manual, XSAVES also set the XCOMP_BV[62:0]. My code only
> > try to be compatible with what the cpu does when excuting XSAVES. The following
> > is quoted from 325462-sdm-vol-1-2abcd-3abcd.pdf.
> > The XSAVES instructions sets bit 63 of the XCOMP_BV field of the XSAVE header while writing RFBM[62:0] to
> > XCOMP_BV[62:0]. The XSAVES instruction does not write any part of the XSAVE header other than the XSTATE_BV
> > and XCOMP_BV fields.
>
> What purpose does it serve to make copyin_to_xsaves() set that bit,
We try to fake up a memory area which is supposed to be composed by XSAVES
instruction. My code is just trying to do what the XSAVES do.
> other than helping to hide bugs?
Why do you think it hide the bug? In contrast, I think my patch fixes what the
bug really is. The memory area we fake up is bug, we should fix it there.
Thanks,
Kevin
Attachment:
signature.asc
Description: PGP signature
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]