From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: "Yao, Yuan" <yuan.yao@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/fpu: Remove dynamic features from xcomp_bv for init_fpstate
Date: Thu, 13 Oct 2022 21:26:07 -0700 [thread overview]
Message-ID: <2b596039-578e-be9a-792d-5f706ca9c238@intel.com> (raw)
In-Reply-To: <BYAPR11MB3717D733EC448197D0321FF695249@BYAPR11MB3717.namprd11.prod.outlook.com>
On 10/13/2022 9:10 PM, Yao, Yuan wrote:
>
> Does init_fpstate saves the "init" state for all non-dynamic components in its buffer ?
For legacy states :)
* ... But doing so is a pointless exercise because most
* components have an all zeros init state except for the legacy
* ones (FP and SSE).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/kernel/fpu/xstate.c#n379
Thanks,
Chang
next prev parent reply other threads:[~2022-10-14 4:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 22:24 [PATCH] x86/fpu: Remove dynamic features from xcomp_bv for init_fpstate Dave Hansen
2022-10-11 22:47 ` Chang S. Bae
2022-10-13 1:33 ` Yao, Yuan
2022-10-13 1:47 ` Chang S. Bae
2022-10-13 3:35 ` Yao, Yuan
2022-10-13 16:23 ` Chang S. Bae
2022-10-13 17:21 ` Dave Hansen
2022-10-13 17:33 ` Chang S. Bae
2022-10-13 17:44 ` Dave Hansen
2022-10-14 3:53 ` Chang S. Bae
2022-10-14 4:10 ` Yao, Yuan
2022-10-14 4:26 ` Chang S. Bae [this message]
2022-10-14 4:03 ` Yao, Yuan
2022-10-13 18:04 ` Dave Hansen
2022-10-17 22:39 ` Chang S. Bae
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=2b596039-578e-be9a-792d-5f706ca9c238@intel.com \
--to=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuan.yao@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).