From: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>
To: John <therealgraysky@proton.me>
Cc: Borislav Petkov <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Unknown <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: add more x86-64 micro-architecture levels
Date: Thu, 19 Sep 2024 01:25:17 +0500 [thread overview]
Message-ID: <96f609c7-f185-49c8-a9d5-a26bfd093b09@gmail.com> (raw)
In-Reply-To: <JDkDAyklisK_zhy8Ecsw8Z6t4ALDO1Jzzza2DZjWefD5erI-tTPGD6GhevyIp1Ee1xoWg1ouqkMCOqcylaqwZg2YBO7h9USi0qzCIRotUBo=@proton.me>
On 9/19/24 00:02, John wrote:
> Yes, that is my git repo.
Oops, I didn't realize that.
Even better then! Could you please explain where the performance gains should come from, considering that the kernel force disables all SIMD extensions?
https://github.com/torvalds/linux/blob/4a39ac5b7d62679c07a3e3d12b0f6982377d8a7d/arch/x86/Makefile#L67-L80
I.e. if we won't have them anyway, what gives?
next prev parent reply other threads:[~2024-09-18 20:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 11:05 John
2024-09-15 11:40 ` Dave Hansen
2024-09-15 12:25 ` John
2024-09-15 12:58 ` Dave Hansen
2024-09-15 18:42 ` John
2024-09-17 18:22 ` John
2024-09-17 18:45 ` H. Peter Anvin
2024-09-15 12:49 ` Borislav Petkov
2024-09-15 12:53 ` Dave Hansen
2024-09-17 21:33 ` Hanabishi
2024-09-18 19:02 ` John
2024-09-18 20:25 ` Hanabishi [this message]
2024-09-18 21:14 ` John
2024-09-18 21:48 ` Hanabishi
2024-09-18 23:07 ` John
2024-09-16 5:14 ` WangYuli
2024-09-24 7:00 ` kernel test robot
2024-09-24 13:38 ` Dave Hansen
2024-09-24 17:40 ` John
2024-09-26 1:43 ` Oliver Sang
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=96f609c7-f185-49c8-a9d5-a26bfd093b09@gmail.com \
--to=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
--cc=bp@alien8.de \
--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=therealgraysky@proton.me \
--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®