From: "Xu, Pengfei" <pengfei.xu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
"Su, Heng" <heng.su@intel.com>, "Du, Julie" <julie.du@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"Li, Philip" <philip.li@intel.com>,
"Xu, Pengfei" <pengfei.xu@intel.com>
Subject: Re: Tested x86 FPU fixes and found "Bad FPU state" issue
Date: Mon, 21 Jun 2021 11:50:33 +0000 [thread overview]
Message-ID: <72e37a644f474a3888ff96833213558d@intel.com> (raw)
In-Reply-To: <87pmwffruk.ffs@nanos.tec.linutronix.de>
Hi Thomas,
Thanks for your update!
And I tried new fpu branch with last commit:
b4c5dbb182058b2bd176fce77a4aea64494bf781
I verified this issue was fixed.
I will keep testing new FPU branch kernel.
Thanks!
BR.
On 2021-06-21 at 12:13:23 +0200, Thomas Gleixner wrote:
> Pengfei!
>
> On Mon, Jun 21 2021 at 01:31, Pengfei Xu wrote:
> > This "Bad FPU state" issue was found in 20210619 FPU branch kernel:
> > https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git
> > branch: origin/x86/fpu
> > last commit:
> > "
> > commit 2299e66e766a7cdca8aafc36b59ada8782d26233
> > ...
> > x86/fpu/signal: Let xrstor handle the features to init
> > "
>
> Thanks for testing and reporting!
>
> I found the issue and updated the branch. New head commit is
>
> b4c5dbb18205 ("x86/fpu/signal: Let xrstor handle the features to init")
>
> Thanks,
>
> tglx
prev parent reply other threads:[~2021-06-21 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e6f363f138e4d05b368f4428399466b@intel.com>
2021-06-21 10:13 ` Tested x86 FPU fixes and found "Bad FPU state" issue Thomas Gleixner
2021-06-21 11:50 ` Xu, Pengfei [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72e37a644f474a3888ff96833213558d@intel.com \
--to=pengfei.xu@intel.com \
--cc=dave.hansen@intel.com \
--cc=heng.su@intel.com \
--cc=julie.du@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=yu-cheng.yu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).