From: Peter Zijlstra <peterz@infradead.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
x86@kernel.org
Subject: Re: [regression/bisected] Add IBPB decreases performance in two times
Date: Mon, 14 Aug 2023 14:37:13 +0200 [thread overview]
Message-ID: <20230814123713.GI776869@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CABXGCsNSZD8GG1ZbpeNg54rjnsa9HQ3MumTgprLo8n5WE2VCoQ@mail.gmail.com>
On Mon, Aug 14, 2023 at 03:30:51AM +0500, Mikhail Gavrilov wrote:
> On Sun, Aug 13, 2023 at 7:19 PM Borislav Petkov <bp@alien8.de> wrote:
> > Nah, most people search the net and usually find the documentation, as
> > past experience shows. In this case, they will find:
> >
> > https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html
> >
> > It will be there next week but here's the source:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/hw-vuln/srso.rst
> >
> > --
> > Regards/Gruss,
> > Boris.
> >
> > https://people.kernel.org/tglx/notes-about-netiquette
>
> I am figure out why I noticed lage impact of safe RET on my system.
> safe-ret + KASAN = decrease performance for 50% in all scenarios
> I use KASAN on a daily basis to catch bugs.
> Is it possible for systems with KASAN to make a more optimal approach of SRSO?
Why do you care about speculation things on a dev box?
next prev parent reply other threads:[~2023-08-14 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 22:55 [regression/bisected] Add IBPB decreases performance in two times Mikhail Gavrilov
2023-08-13 8:24 ` Borislav Petkov
2023-08-13 9:17 ` Mikhail Gavrilov
2023-08-13 9:35 ` Borislav Petkov
[not found] ` <CABXGCsMrNz2SPYN=zLZTT7jU4axSi-XLm4bTm7K3NuWnc=yr9g@mail.gmail.com>
2023-08-13 11:14 ` Borislav Petkov
2023-08-13 11:38 ` Mikhail Gavrilov
2023-08-13 14:19 ` Borislav Petkov
2023-08-13 22:30 ` Mikhail Gavrilov
2023-08-14 12:37 ` Peter Zijlstra [this message]
2023-08-15 12:19 ` Mikhail Gavrilov
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=20230814123713.GI776869@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--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