From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Dave Hansen" <dave.hansen@intel.com>, x86@kernel.org
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
chang.seok.bae@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 00/10] x86: Allocate AVX512 xstate ondemand
Date: Fri, 03 Dec 2021 11:42:10 +0000 [thread overview]
Message-ID: <e249390b-6f87-47f6-8676-fa727b2fa932@www.fastmail.com> (raw)
In-Reply-To: <d7be6ef4-f73e-923e-93b7-ef254bf347c0@intel.com>
在2021年12月3日十二月 上午12:58,Dave Hansen写道:
> On 12/2/21 4:45 PM, Jiaxun Yang wrote:
>> 在2021年12月3日十二月 上午12:40,Dave Hansen写道:
>>> On 12/2/21 4:36 PM, Jiaxun Yang wrote:
>>>> Also we are going to have heterogeneous processors that
>>>> only some cores support AVX512, it can be helpful when
>>>> dealing with such processors.
>>> Really? Which x86 vendor is doing that?
>> Clear lower two bits of MSR 0xAF on Alder Lake give me some suprise :-)
>
> I honestly don't know what you're talking about. Does poking that MSR
> allowing AVX512 instructions to be executed on cores where it was
> otherwise disabled? That's entertaining, but it's far from "supported"
> or even support*able* in Linux.
If it's improper I'll drop the statement in commit message :-)
Yep, I'm entertaining with kernel hackcing.
Thanks
--
- Jiaxun
next prev parent reply other threads:[~2021-12-03 11:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 0:36 Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 01/10] x86/fpu: Remove duplicated declaration of __fpu_state_size_dynamic Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 02/10] x86/fpu: Split fpu_xfd_enabled from fpu_state_size_dynamic Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 03/10] x86/fpu: Calculate xsave state addr on fly Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 04/10] x86/fpu: Remove xstate_comp_offsets cache Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 05/10] x86/fpu: Cache xstate_is_aligned Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 06/10] x86/fpu/xcr: Return all enabled xfeature if CPU doesn't support Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 07/10] x86/fpu: Rellocate fpstate on save_fpregs_to_fpstate Jiaxun Yang
2021-12-03 0:44 ` Dave Hansen
2021-12-03 11:39 ` Jiaxun Yang
2021-12-03 15:18 ` Dave Hansen
2021-12-03 15:51 ` Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 08/10] x86/fpu: Don't keep state_size in perm struct Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 09/10] x86/fpu: Split out XFEATURE_MASK_KERNEL_DYNAMIC Jiaxun Yang
2021-12-03 0:36 ` [RFC PATCH 10/10] x86/fpu: Mark AVX512 xfeatures as kernel dynamic Jiaxun Yang
2021-12-03 0:40 ` [RFC PATCH 00/10] x86: Allocate AVX512 xstate ondemand Dave Hansen
2021-12-03 0:45 ` Jiaxun Yang
2021-12-03 0:58 ` Dave Hansen
2021-12-03 9:20 ` David Laight
2021-12-03 11:42 ` Jiaxun Yang [this message]
2021-12-03 11:51 ` Borislav Petkov
2021-12-03 11:55 ` Jiaxun Yang
2021-12-04 11:55 ` Peter Zijlstra
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=e249390b-6f87-47f6-8676-fa727b2fa932@www.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®