From: Borislav Petkov <bp@alien8.de>
To: David Laight <David.Laight@aculab.com>
Cc: Breno Leitao <leitao@debian.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"pawan.kumar.gupta@linux.intel.com"
<pawan.kumar.gupta@linux.intel.com>,
"paul@paul-moore.com" <paul@paul-moore.com>,
"leit@meta.com" <leit@meta.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpu/bugs: Disable CPU mitigations at compilation time
Date: Mon, 12 Jun 2023 15:27:50 +0200 [thread overview]
Message-ID: <20230612132750.GIZIcdVmvWkQXu/85B@fat_crate.local> (raw)
In-Reply-To: <bdcc00582da6454ab7e5778ad108a1d7@AcuMS.aculab.com>
On Mon, Jun 12, 2023 at 12:16:19PM +0000, David Laight wrote:
> I do (and I compile without page table separation),
> but some of the run-time patched versions are not as 'good'
> as compiling the code out.
> It might just be some nops, but maybe it is worse.
"might", schmight, ... other statements without proof...
If you want me to take you seriously, explain in detail the problem.
Otherwise, I can keep on ignoring you.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-06-12 13:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:06 [PATCH] cpu/bugs: Disable CPU mitigations at compilation time Breno Leitao
2023-06-09 17:33 ` Borislav Petkov
2023-06-12 11:22 ` David Laight
2023-06-12 11:51 ` Borislav Petkov
2023-06-12 12:16 ` David Laight
2023-06-12 13:27 ` Borislav Petkov [this message]
2023-06-10 22:37 ` Thomas Gleixner
2023-06-12 12:54 ` Breno Leitao
2023-06-12 13:32 ` Borislav Petkov
2023-06-12 13:46 ` Breno Leitao
2023-06-12 13:53 ` Borislav Petkov
2023-06-12 14:16 ` Breno Leitao
2023-06-12 16:08 ` Borislav Petkov
2023-06-12 16:37 ` Breno Leitao
2023-06-12 17:05 ` Borislav Petkov
2023-06-13 16:02 ` Breno Leitao
2023-06-13 16:20 ` Borislav Petkov
2023-06-12 17:26 ` Thomas Gleixner
2023-06-12 18:06 ` Randy Dunlap
2023-06-12 18:13 ` Borislav Petkov
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=20230612132750.GIZIcdVmvWkQXu/85B@fat_crate.local \
--to=bp@alien8.de \
--cc=David.Laight@aculab.com \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=pawan.kumar.gupta@linux.intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).