From: Arjan van de Ven <arjan@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>,
Asit K Mallick <asit.k.mallick@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Brown, Len" <len.brown@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
the arch/x86 maintainers <x86@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Bae, Chang Seok" <chang.seok.bae@intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Revisiting XFD-based AMX and heterogenous systems
Date: Mon, 15 Nov 2021 12:11:28 -0800 [thread overview]
Message-ID: <8425e818-f6cc-ae52-ac6b-9cc80515c238@linux.intel.com> (raw)
In-Reply-To: <0f03a9e2-4611-4b5c-962f-93a7e1d2bde8@www.fastmail.com>
On 11/15/2021 11:59 AM, Andy Lutomirski wrote:
> [resend -- first try was HTML. oops.]
>
> Hi all-
>
> I just learned that current Alder Lake review samples are actually heterogenous, at least physically. The performance cores have AVX-512 and the efficiency cores don't have AVX-512. Since no OS supports actual runtime ISA heterogeneity, this feature seems to be hidden in that one must choose, per boot, whether one wants AVX-512 or efficiency cores, but the CPU is physically heterogenous.
>
> All the earlier discussions about Linux AMX architecture happened under the assumption that xfeature-heterogenous systems would never happen, and my grudging acceptance of the XFD model was predicated on that. But now we have obviously heterogenous hardware that is apparently actually shipping at least to reviewers, and I think we should revisit this before we merge AMX support.
>
Alderlake is not heterogenous.
This is not just an "OS can deal with it" thing... it's throughout everything from low lower power delivery through bios through ...
next prev parent reply other threads:[~2021-11-16 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 19:59 Andy Lutomirski
2021-11-15 20:11 ` Arjan van de Ven [this message]
2021-11-15 20:18 ` Andy Lutomirski
2021-11-23 14:24 ` Len Brown
2021-11-15 21:12 ` Thomas Gleixner
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=8425e818-f6cc-ae52-ac6b-9cc80515c238@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=asit.k.mallick@intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--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®